1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
|
<html>
<head>
<title>Debian testing security team</title>
</head>
<h1>Goals</h1>
<p>
The Debian testing security team is a group of debian developers
and users who are working to improve the state of security in
Debian's testing branch. Lack of security support for testing has
long been one of the key problems to using testing, and we aim to
eventually provide full security support for testing.
</p>
<h1>Activities</h1>
<p>
The team's first activity was to check all security holes since the
release of Debian 3.0, to ensure that all the holes are fixed in
sarge and to provide a baseline for future work.
</p>
<p>
Now the team is tracking new holes on an ongoing basis, making sure
maintainers are informed of them and that there are bugs in the
Debian BTS, writing patches and doing NMUs as necessary, and
tracking the fixed packages and working with the Debian Release
Managers to make sure fixes reach testing quickly. Thanks to this
work we now have
<a href="http://spohr.debian.org/~joeyh/testing-security.html">a
web page</a>, that tracks open security holes in testing.
</p>
<p>
The team is in the process of beginning full security support for
testing by providing security advisories and fixes built against
testing without the usual delays sometimes involved in getting a
security fix into testing. These will be announced on the
<a href="http://lists.alioth.debian.org/mailman/listinfo/secure-testing-announce">secure-testing-announce@lists.alioth.debian.org</a>
mailing list, and will be available in the following apt
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>
<p>
Currently we're limiting ourselves to tracking security holes that
have been the subject of a Debian Security Advisory, or are in the
<a href="http://www.cve.mitre.org/cve/index.html">CVE</a> database.
It's very helpful to us if bug reports and Debian changelog entries
include CVE numbers for security holes. If you don't have a CVE
number, we can help you get one.
</p>
<p>
The team maintains a database (actually some files) that contain
our notes about all CVEs, CANs, and DSAs. This database is available
<a href="http://svn.debian.org/wsvn/secure-testing">from subversion</a>,
and may be checked out from
<tt>svn://svn.debian.org/secure-testing/</tt>.
</p>
<h1>Uploads to the secure-testing repository</h1>
<p>
To upload a package to the secure-testing repository, any Debian
developer may follow this checklist:
<ol>
<li>Only upload changes that have already been made in
unstable and are blocked by reaching testing by some other
issues. This is both to keep things in sync once the
new version from unstable reaches testing, and to avoid
breaking secure-testing too badly with fixes that have not
been tested first in unstable.</li>
<li>Only make uploads for issues that the testing security
team plans to issue a DTSA announcement for. It is best to
contact the team first to avoid duplicate work.</li>
<li>Use a version number that is less than the version
number of the fix in unstable, but greater than the version
number of the fix in testing. For example, if the fix is in
a new upstream version 1.0-1 in unstable, upload version
1.0-0.1etch1 to secure-testing. If the fix is in version
1.5-10 in unstable, use version 1.5-9etch1 in
secure-testing.</li>
<li>Use "testing" as the distribution in the
changelog.</li>
<li>Build the package in a testing chroot using pbuilder
so that all the dependencies are ok. Be sure to build with
the -sa switch to include source, unless the source is
already in the secure-testing archive.
</li>
<li>Test the package.</li>
<li>Sign the package. Any Debian developer in the keyring
can do so.</li>
<li>Upload to <tt>secure-testing-master.debian.net</tt>.
Here is a dput.cf snippet for that upload queue:
<pre>
[secure-testing]
fqdn = secure-testing-master.debian.net
method = ftp
incoming = /pub/UploadQueue/
login = anonymous
</pre>
</li>
<li>Once your fix is accepted, a mail will be sent to
the <a href="http://lists.alioth.debian.org/mailman/listinfo/secure-testing-changes">secure-testing-changes</a>
list and, it will become available in this apt repository,
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>.
Once everything is ready, contact a team member to issue a
DSTA.
</li>
</ol>
<p>
To issue a DTSA, team members follow this checklist:
<ol>
<li>Commit an initial .adv template into SVN to prevent duplicate work and claim an advisory number
<li>Prepare the update and fill out the .adv template
<li>Make sure everything is ready.
<li>cd data/DTSA; ./dtsa -p ADVISORYNUMBER</li>
<li>svn add DTSA-n-1; svn commit</li>
<li>Edit data/DTSA/hints/yourname, and add a hint to make dtsasync
propigate the update from etch-proposed-updates to etch.
Commit the file and wait 15 minutes for the dtsasync run,
then check the <a href="logs/dtsasync">log file</a> and/or
upgrade a test machine.</li>
<li>cd data/DTSA; ./sndadvisory DTSA-n-1</li>
</ol>
</p>
<p>
Note that the above instructions are provisional until we get
everything set up.
</p>
<h1>Members and contacting the team</h1>
<p>
While some individual members may have sources of prior information
about security advisories (such as vendor-sec), the team as a whole
operates only on publically available information. Any Debian
developers with an interest in participating are welcome to join
the team, and we also welcome others who have the skills and desire
to help us.
</p>
<p>
The team can be contacted through its mailing list,
<a href="http://lists.alioth.debian.org/mailman/listinfo/secure-testing-team">secure-testing-team@lists.alioth.debian.org</a>.
There is a second mailing list,
<a href="http://lists.alioth.debian.org/mailman/listinfo/secure-testing-commits">secure-testing-commits@lists.alioth.debian.org</a>
that receives commit messages to our repository, new team members
are encouraged to join it.
The list
<a href="http://lists.alioth.debian.org/mailman/listinfo/secure-testing-changes">secure-testing-changes@lists.alioth.debian.org</a>
receives automatic annoucements of fixed packages uploaded to our
repository.
An <a href="http://alioth.debian.org/projects/secure-testing/">alioth
project page</a> is also available.
</p>
<hr>
$Id$
</html>
|
