Commit 79eda9a5 authored by Moritz Muehlenhoff's avatar Moritz Muehlenhoff

remove outdated information

git-svn-id: svn+ssh:// e39458fd-73e7-0310-bf30-c45bca0a0e42
parent 9737e481
......@@ -35,133 +35,6 @@
<h2><a name="goals">Goals</a></h2>
The Debian testing security team is a group of Debian developers
and users who are working to keep Debian's testing branch in good
shape with respect to security. Since packages migrate to testing
from Debian's unstable branch, a secondary goal of the team is to
improve the state of security in unstable.
<h2><a name="tracker">Security Tracker</a></h2>
The team is tracking new security holes on an ongoing basis, making sure
maintainers are informed of them and filing bug reports in the
Debian BTS. The result of this work is availably in the
<a href="">Security Tracker web page</a>.
This tracker contains information about all branches of Debian and is also
used by the stable security team.
<h2><a name="testing-support">Security support for testing</a></h2>
<p>The team is providing security support for Debian's testing branch by</p>
<li>writing patches and doing NMUs to unstable as necessary</li>
<li>tracking the fixed packages and working with the Debian Release
Managers to make sure fixes reach testing quickly</li>
<li>if this process is too slow, providing fixed packages built against testing
in the <em>testing-security apt repository</em>:
deb testing/updates main contrib non-free
deb-src testing/updates main contrib non-free
However, the majority of security fixes reach testing by migration from
unstable. </li>
<p>Note that in order to take advantage of the security support for testing,
you must <em>update your system on a regular basis</em>.</p>
<h3><a name="limitations">Limitations</a></h3>
<p>For several reasons, the security support for testing cannot be expected to
be of the same quality as for Debian's stable branch:</p>
<li>Updates for testing-security usually receive less testing than updates
for stable-security.</li>
<li>Testing is changing all the time which increases the likelihood of problems
with the build infrastructure. Such problems can delay security updates in
<h3><a name="announce">Announcements</a></h3>
<p> Daily notifications about fixed security issues are sent to the
<a href=""></a>
mailing list.</p>
<h2><a name="contact">Contacting the team</a></h2>
<p>To contact the team, use</p>
<li> the
<a href="">team mailing list</a> at
<a href=""></a>
(Please note that this is a public list, and as such, you should not send details of undisclosed
vulnerabilities to this address.)</li>
<li>IRC: Our irc channel is #debian-security on the OFTC network.</li>
<p>For issues related to the Debian security tracker, use the</p>
<ul><li><a href="">security tracker mailing list</a> at
<a href=""></a>
<h2><a name="more">Helping the team</a></h2>
<li><a href="helping.html">Helping the testing security team</a></li>
<li><a href="uploading.html">Uploading to the testing-security repository</a></li>
<h2><a name="more">More information</a></h2>
<li><a href="">List of open
security issues in testing</a></li>
<li><a href="">Debian Security Analyzer</a> shows which
open issues affect your system</li>
<li><a href="">Subversion repository</a>
holding the data for the <a href="">Debian
security tracker</a>. It may be checked out from
<tt>svn://</tt>. There is also a
<a href="">mailing list</a>
for the commit messages.</li>
<li><a href="">Alioth
project page</a> with a list of team members.</li>
<li><a href="">Mitre's CVE database</a></li>
<h3><a name="int-doc">Internal information</a></h3>
<li><a href="">Introduction
to our processes</a></li>
<li><a href=";;exclude=tracked">Bugs
tagged security</a> that have not been added to the tracker, yet</li>
<li>Information about accepted uploads to testing-security is sent to <a
<a href="">
......@@ -172,3 +45,10 @@
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment