- add support for DTSAs, with a new DTDA directory, a script to generate

  them, etc
- automatic db update with DTSA


git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@1660 e39458fd-73e7-0310-bf30-c45bca0a0e42

1 files changed, 5 insertions, 2 deletions

diff --git a/website/index.html b/website/index.html
index eb19fa66ef..f9a16ded50 100644
--- a/website/index.html
+++ b/website/index.html
@@ -42,7 +42,9 @@
 	repository:
 	<pre>
 	deb http://secure-testing.debian.net/debian-security-updates etch/security-updates main contrib non-free
+	deb-src http://secure-testing.debian.net/debian-security-updates etch/security-updates main contrib non-free
 	</pre>
+	The archive signing key used for this repository is <a href="ziyi-2005-7.asc">here</a>.
 	</p>
 	
 	<h1>Data sources</h1>
@@ -108,17 +110,18 @@
 		including builds for all other architectures:
 		<pre>
 		deb http://secure-testing.debian.net/debian-security-updates etch-proposed-updates/security-updates main contrib non-free
+		deb-src http://secure-testing.debian.net/debian-security-updates etch-proposed-updates/security-updates main contrib non-free
 		</pre>
 		Build logs can be found
 		<a href="http://experimental.debian.net/">here</a>.
 		</li>
 		<li>
 		Once everything is ready, contact a team member to create a DSTA annoucement
-		(procedure pending), contact a secure-testing-master admin
+		(using data/DTSA/mkadvisory), contact a secure-testing-master admin
 		to move the upload from etch-proposed-updates to
 		etch (using something like this, but the procedure is still being worked out:
 		madison -s etch-proposed-updates -f heidi -S $package | sudo -u katie heidi -a etch)
-		and send the DSTA to secure-testing-announce.
+		and send the signed DSTA to secure-testing-announce.
 		</li>
 	</ol>
 	</p>