> Experience has shown that "security through obscurity" does
not work. Public disclosure allows for more rapid and better solutions to
security problems. In that vein, this page addresses Debian's status with
respect to various known security holes, which could potentially affect
respect to various known security vulnerabilities, which could potentially affect
Debian.
# Current holes
# Current security vulnerabilities
[[!inline pages="page(security/*) and ! tagged(security/probable)
and !security/audits and !security/audits.* and !security/audits/*
and ! tagged(security/fixed) and currentlang() and created_after(security/Numerous_security_holes_in_1.2)"
actions=no archive=yes feeds=no show=0 sort="-meta(date) age -path"]]
# Probable holes
# Probable security vulnerabilities
Until an [[!tails_ticket 5769 desc="audit"]] of the bundled network
applications is done, information leakages at the protocol level
...
...
@@ -38,12 +38,12 @@ should be considered as − at the very least − possible.
[[!inline pages="page(security/*) and tagged(security/probable) and currentlang()"
actions=no archive=yes feeds=no show=0 sort="-meta(date) age -path"]]
# Fixed holes
# Fixed security vulnerabilities
**WARNING**: some of these holes may only be fixed in [[Git|contribute/git]].
**WARNING**: some of these vulnerabilities may only be fixed in [[Git|contribute/git]].
Please carefully read the "Affected versions" sections below.
[[!inline pages="page(security/*) and tagged(security/fixed) and (currentlang() or security/Numerous_security_holes_in_*)"
[[!inline pages="page(security/*) and tagged(security/fixed) and (currentlang() or security/Numerous_security_holes_in_* or security/Known_security_vulnerabilities_in_*)"
actions=no archive=yes feeds=no show=0 sort="-meta(date) age -path"]]