summaryrefslogtreecommitdiffstats
path: root/doc/security-team.d.o/triage
diff options
context:
space:
mode:
Diffstat (limited to 'doc/security-team.d.o/triage')
-rw-r--r--doc/security-team.d.o/triage4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/security-team.d.o/triage b/doc/security-team.d.o/triage
index a45407efc4..828c919eca 100644
--- a/doc/security-team.d.o/triage
+++ b/doc/security-team.d.o/triage
@@ -4,10 +4,10 @@ Security updates affecting a released Debian suite can fall under three types:
These are getting announced via [debian-security-announce](https://www.debian.org/security/) and also redistributed via other sources (news feeds etc).
- Low severity updates can be included in [point releases](https://wiki.debian.org/DebianReleases/PointReleases), which are getting released every 2-3 months (any user using the [proposed-updates mechanism](https://www.debian.org/releases/proposed-updates) can also use them before they get released). This provides a good balance between fixing low impact issues before the next stable
- release, which can simply all be installed in one go when a point release happens.
+ release, which can simply be installed in one go when a point release happens.
- Some issues are simply not worth fixing in a stable release (for multiple reasons, e.g. because they are mostly a PR hype, or because they
- are mitigated in Debian via a different config or toolchain hardening).
+ are mitigated in Debian via a different config or toolchain hardening or because the impact is so marginal that it doesn't warrant an update).
Every incoming security issue gets triaged. Security issues which are being flagged for the second category are being displayed in the [Debian Package Tracker](https://tracker.debian.org), in fact you might have been redirected from the PTS to this page.

© 2014-2024 Faster IT GmbH | imprint | privacy policy