[Secure-testing-commits] r1722 - data/DTSA/hints doc
Joey Hess
joeyh at costa.debian.org
Mon Aug 29 20:40:32 UTC 2005
Author: joeyh
Date: 2005-08-29 20:40:32 +0000 (Mon, 29 Aug 2005)
New Revision: 1722
Modified:
data/DTSA/hints/joeyh
doc/announce.2
Log:
some misc updates
Modified: data/DTSA/hints/joeyh
===================================================================
--- data/DTSA/hints/joeyh 2005-08-29 20:38:38 UTC (rev 1721)
+++ data/DTSA/hints/joeyh 2005-08-29 20:40:32 UTC (rev 1722)
@@ -1,3 +1,5 @@
+#sync pcre3/6.3-0.1etch1
+
sync mozilla-firefox/1.0.4-2sarge2
sync mozilla/2:1.7.8-1sarge1
sync centericq/4.20.0-8etch1
Modified: doc/announce.2
===================================================================
--- doc/announce.2 2005-08-29 20:38:38 UTC (rev 1721)
+++ doc/announce.2 2005-08-29 20:40:32 UTC (rev 1722)
@@ -35,9 +35,17 @@
DTSA-1-1 kismet -
XXXXXX complete
-Currently, security updates are only built for the alpha, i386, ia64,
-mipsel, powerpc and sparc architectures.
+Note that while all of Debian's architectures are supported, we may release
+an advisory before fixed packages have built for all supported
+architectures. If so the missing builds will become available as they
+complete.
+We are not currently issueing advisories for security fixes that reach
+testing through normal propigation from unstable, but only for security
+fixes that are made available through our repository. So users of testing
+should continue to upgrade their systems on a regular basis to get such
+security fixes.
+
Note that this announcement does not mean that testing is suitable for
production use. Several security issues are present in unstable, and an
even larger number are present in testing. Our beginning of security
@@ -47,6 +55,10 @@
open, and users should use this information to make their own decisions
about whether testing is secure enough for them.
+Finally, we are still in the process of working out how best to serve users
+of testing and keep your systems secure, and we welcome comments and
+feedback about ways to do better.
+
For more information about the testing security team, see our web site.
<http://secure-testing.alioth.debian.org/>.
More information about the Secure-testing-commits
mailing list