[Secure-testing-commits] r1656 - doc

[Joey Hess]

Author: joeyh
Date: 2005-08-26 15:09:54 +0000 (Fri, 26 Aug 2005)
New Revision: 1656

Added:
   doc/announce.2
Log:
draft announcement


Added: doc/announce.2
===================================================================
--- doc/announce.2	2005-08-26 14:43:08 UTC (rev 1655)
+++ doc/announce.2	2005-08-26 15:09:54 UTC (rev 1656)
@@ -0,0 +1,39 @@
+DRAFT. Slashdot on penalty of death. DRAFT
+
+
+Subject: announcing the beginning of security support for testing
+
+The Debian testing security team is pleased to announce the beginning of
+full security support for Debian's testing distribution. We have spent the
+past year building the team, tracking and fixing security holes, and
+creating our infrastructure, and now the final piece is in place, and 
+we are able to offer security updates and advisories for testing.
+
+We invite Debian users who are currently running testing, or who would like
+to switch to testing, to subscribe to the secure-testing-announce mailing 
+list, which will be used to announce security updates.
+<http://lists.alioth.debian.org/mailman/listinfo/secure-testing-announce>
+
+We also invite you to add the following line to your apt sources.list file,
+and run "apt-get update && apt-get upgrade" to make the security updates
+available:
+
+deb http://secure-testing.debian.net/debian-security-updates etch/security-updates main contrib non-free
+
+Note that some initial advisories have already been posted to the list
+and are already available in the repository. These include:
+
+DTSA-1-1 kismet -
+XXXXXX complete
+
+Note that this announcement does not mean that testing is free of security
+issues. Several security issues are present in unstable, and an even larger
+quantity are present in testing. Our beginning of security support only
+means that we are now able to begin making security fixes available for
+testing nearly as quickly as for unstable. The testing security team makes
+statistics about what security holes are still open available on our
+website, and users should use this information to make their own decision
+about whether testing is secure enough for production use.
+
+For more information about the testing security team, see our web site.
+<http://secure-testing.alioth.debian.org/>.