1 [[!meta title="Security"]]
5 [[!inline pages="security/* and !security/audits and !security/audits.* and !security/audits/* and currentlang()"
6 actions=no archive=yes feedonly=yes show=10]]
8 Since Tails is based on Debian, it takes advantage of all the work done by the
9 Debian security team. As quoted from <http://security.debian.org/>:
11 > Debian takes security very seriously. We handle all security
12 problems brought to our attention and ensure that they are corrected within a
13 reasonable timeframe. Many advisories are coordinated with other free software
14 vendors and are published the same day a vulnerability is made public and we
15 also have a Security Audit team that reviews the archive looking for new or
16 unfixed security bugs.
18 > Experience has shown that "security through obscurity" does
19 not work. Public disclosure allows for more rapid and better solutions to
20 security problems. In that vein, this page addresses Debian's status with
21 respect to various known security holes, which could potentially affect
26 [[!inline pages="security/* and ! tagged(security/probable)
27 and ! tagged(security/fixed) and currentlang() and created_after(security/Numerous_security_holes_in_1.0.1)"
28 actions=no archive=yes feeds=no show=0]]
32 Until an [[!tails_ticket 5769 desc="audit"]] of the bundled network
33 applications is done, information leakages at the protocol level
34 should be considered as − at the very least − possible.
36 [[!inline pages="security/* and tagged(security/probable) and currentlang()"
37 actions=no archive=yes feeds=no show=0]]
41 **WARNING**: some of these holes may only be fixed in [[Git|contribute/git]].
42 Please carefully read the "Affected versions" sections bellow.
44 [[!inline pages="security/* and tagged(security/fixed) and currentlang()"
45 actions=no archive=yes feeds=no show=0]]
49 Audits of Tails that we are aware of are collected in [[security/audits]].