Project

General

Profile

Feature #14728

Track security updates during the Tails code freeze

Added by anonym 3 months ago. Updated 26 days ago.

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
09/26/2017
Due date:
% Done:

0%

QA Check:
Feature Branch:
Type of work:
Research
Blueprint:
Starter:
Affected tool:

Description

This affects:

  1. packages we install from others dists than Debian stable, e.g. from Debian testing or Debian sid. A good example of the problem is the linux kernel which we install from sid; for instance, at the time of the 3.2 freeze we got linux 4.12.12-2, but in the middle of the freeze linux 4.12.13-1 was uploaded to sid, and it was not noticed until the final 3.2 was built so we missed out on several security updates.
  2. packages we override with our custom APT repo, see e.g. #14729 for one instance of this problem

Related issues

Related to Tails - Bug #14729: Fix gdk-pixbuf vulnerability (CVE-2017-2862) Resolved 09/26/2017

History

#1 Updated by intrigeri 2 months ago

  • Related to Bug #14729: Fix gdk-pixbuf vulnerability (CVE-2017-2862) added

#2 Updated by intrigeri 2 months ago

  • Subject changed from Improve tracking of security updates during the freeze to Track security updates during the Tails code freeze
  • Description updated (diff)

#3 Updated by anonym 2 months ago

The comment #14729#note-4 is relevant here. In particular, I believe the solution our security tracking woes is to automate it.

#4 Updated by intrigeri 2 months ago

A short-term, trivial fix would be to:

#5 Updated by anonym 26 days ago

  • Target version changed from Tails_3.3 to Tails_3.5

Also available in: Atom PDF