Author: micah
Date: 2006-03-14 16:52:56 +0000 (Tue, 14 Mar 2006)
New Revision: 3615
Modified:
doc/narrative_introduction
Log:
Re-re-clarified DSA cross references
Modified: doc/narrative_introduction
===================================================================
--- doc/narrative_introduction 2006-03-14 16:46:53 UTC (rev 3614)
+++ doc/narrative_introduction 2006-03-14 16:52:56 UTC (rev 3615)
@@ -308,15 +308,9 @@
that tracks, when a fix has reached testing relative to the time when
it hit stable.
-Once an entry has been added to DSA/list, a cross-reference should be
-added to CVE/list, an example based on the above DSA follows:
-
-CVE-2005-2475 (Race condition in Unzip 5.52 allows local users to modify
permissions ...)
- {DSA-903-1}
- - unzip 5.52-4 (bug #321927; low)
-
-It is unnecessary to add [sarge] or [woody] entries to CVE/list when
-there is a DSA cross-reference. However, they should be added if there
+There is no need to add anything to CVE/list for a DSA, the DSA
+cross-reference will be added automatically by the cron job. However,
+you do need to add [sarge] or [woody] entries to CVE/list when there
is a 'no-dsa' or 'not-affected' condition.
The bin/dsa2list script can be used to generate a template for a new
_______________________________________________
Secure-testing-commits mailing list
Secure-testing-commits@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/secure-testing-commits
