1 |
keytoaster 10/09/02 12:25:33 |
2 |
|
3 |
Added: powers.xml |
4 |
Log: |
5 |
Fetched from falco's old .html file. I rewrote the XML and added a 'not up-to-date' warning to the top. |
6 |
|
7 |
Revision Changes Path |
8 |
1.1 xml/htdocs/proj/en/security/powers.xml |
9 |
|
10 |
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/security/powers.xml?rev=1.1&view=markup |
11 |
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/security/powers.xml?rev=1.1&content-type=text/plain |
12 |
|
13 |
Index: powers.xml |
14 |
=================================================================== |
15 |
<?xml version="1.0" encoding="UTF-8"?> |
16 |
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/security/powers.xml,v 1.1 2010/09/02 12:25:33 keytoaster Exp $ --> |
17 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
18 |
|
19 |
<guide> |
20 |
|
21 |
<title>Power list</title> |
22 |
<author title="Author"> |
23 |
<!-- <mail link="koon@g.o">Thierry Carrez</mail> --> |
24 |
<mail>Thierry Carrez</mail> |
25 |
</author> |
26 |
<author title="Editor"> |
27 |
<mail link="keytoaster"/> |
28 |
</author> |
29 |
|
30 |
<abstract> |
31 |
This document lists the permissions people get during the recruiment process |
32 |
for Gentoo Security. |
33 |
</abstract> |
34 |
|
35 |
<license/> |
36 |
|
37 |
<version>0.1</version> |
38 |
<date>2005-01-28</date> |
39 |
|
40 |
<chapter> |
41 |
<title>Powers</title> |
42 |
<section> |
43 |
<body> |
44 |
|
45 |
<warn> |
46 |
This document has not been updated for years and does not reflect the current |
47 |
status of Gentoo Security. |
48 |
</warn> |
49 |
|
50 |
</body> |
51 |
</section> |
52 |
<section> |
53 |
<title>GLSAMaker account</title> |
54 |
<body> |
55 |
|
56 |
<p> |
57 |
Access to the GLSAMaker tool. This power can be granted by security team |
58 |
members, by editing on toucan the /var/www/dev.gentoo.org/glsamaker/.htpasswd |
59 |
file and adding the result of <c>/usr/sbin/htpasswd2 -nm user_to_add</c>. |
60 |
</p> |
61 |
|
62 |
</body> |
63 |
</section> |
64 |
<section> |
65 |
<title>glsa-commits@g.o alias</title> |
66 |
<body> |
67 |
|
68 |
<p> |
69 |
Your email address should be added to the glsa-commits@g.o alias, which |
70 |
receives GLSA draft requests and diffs. This can be granted by security leads or |
71 |
infra people. |
72 |
</p> |
73 |
|
74 |
</body> |
75 |
</section> |
76 |
<section> |
77 |
<title>Channel Op</title> |
78 |
<body> |
79 |
|
80 |
<p> |
81 |
Channel operator rights on #gentoo-security. This power can be granted by |
82 |
klieber. |
83 |
</p> |
84 |
|
85 |
</body> |
86 |
</section> |
87 |
<section> |
88 |
<title>Gentoo developer status</title> |
89 |
<body> |
90 |
|
91 |
<p> |
92 |
Gentoo developer status, which should provide a @gentoo.org email address, a |
93 |
listing on the <uri link="/proj/en/devrel/roll-call/userinfo.xml">roll-call |
94 |
developer list</uri> and editbugs rights for your Bugzilla account. This needs |
95 |
devrel approval and infra powers. |
96 |
</p> |
97 |
|
98 |
</body> |
99 |
</section> |
100 |
<section> |
101 |
<title>Gentoo developer account</title> |
102 |
<body> |
103 |
|
104 |
<p> |
105 |
This gives a Gentoo developer account on dev.gentoo.org, which is needed for CVS |
106 |
access. This needs developer status and infra powers. |
107 |
</p> |
108 |
|
109 |
</body> |
110 |
</section> |
111 |
<section> |
112 |
<title>Security project team listing membership</title> |
113 |
<body> |
114 |
|
115 |
<p> |
116 |
You should get added to the Security project team roster. This can be granted by |
117 |
security developers, by editing the project page contents. |
118 |
</p> |
119 |
|
120 |
</body> |
121 |
</section> |
122 |
<section> |
123 |
<title>Bugzilla Gentoo Security group membership</title> |
124 |
<body> |
125 |
|
126 |
<p> |
127 |
You should be added as a member of the Gentoo Security BugZilla group. This |
128 |
allows you to see security-restricted bugs. This can be granted by koon or infra |
129 |
people. |
130 |
</p> |
131 |
|
132 |
</body> |
133 |
</section> |
134 |
<section> |
135 |
<title>security@g.o alias</title> |
136 |
<body> |
137 |
|
138 |
<p> |
139 |
Your developer email address should be added to the security@g.o alias. |
140 |
This can be granted by security leads or infra people. |
141 |
</p> |
142 |
|
143 |
</body> |
144 |
</section> |
145 |
<section> |
146 |
<title>security-audit@g.o alias</title> |
147 |
<body> |
148 |
|
149 |
<p> |
150 |
Your developer email address is added to the security-audit@g.o alias. |
151 |
This can be granted by security leads or infra people. |
152 |
</p> |
153 |
|
154 |
</body> |
155 |
</section> |
156 |
<section> |
157 |
<title>kern-sec@g.o alias</title> |
158 |
<body> |
159 |
|
160 |
<p> |
161 |
Your developer email address is added to the kern-sec@g.o alias. This can |
162 |
be granted by security leads or infra people. |
163 |
</p> |
164 |
|
165 |
</body> |
166 |
</section> |
167 |
<section> |
168 |
<title>gentoo-announce posting rights</title> |
169 |
<body> |
170 |
|
171 |
<p> |
172 |
Your email account should be cleared to post to the gentoo-announce |
173 |
mailing-list. This can be granted by infra people. |
174 |
</p> |
175 |
|
176 |
</body> |
177 |
</section> |
178 |
<section> |
179 |
<title>cvssecurity commit rights</title> |
180 |
<body> |
181 |
|
182 |
<p> |
183 |
You should get commit rights to security documents (GLSA, security pages, |
184 |
security project pages). This can be granted by infra people. |
185 |
</p> |
186 |
|
187 |
</body> |
188 |
</section> |
189 |
<section> |
190 |
<title>www_glsamaker group</title> |
191 |
<body> |
192 |
|
193 |
<p> |
194 |
Your username should appear in dev.gentoo.org www_glsamaker group. This allows |
195 |
you to act on glsamaker directories directly (for cleanup or direct drafts |
196 |
editing). This can be granted by infra people. |
197 |
</p> |
198 |
|
199 |
</body> |
200 |
</section> |
201 |
<section> |
202 |
<title>Vendor-sec clearance</title> |
203 |
<body> |
204 |
|
205 |
<p> |
206 |
You receive vendor-sec mails. This can be granted by klieber. |
207 |
</p> |
208 |
|
209 |
</body> |
210 |
</section> |
211 |
</chapter> |
212 |
<chapter> |
213 |
<title>Who gets what</title> |
214 |
<section> |
215 |
<body> |
216 |
|
217 |
<table> |
218 |
<tr> |
219 |
<th></th> |
220 |
<ti>Scout</ti> |
221 |
<ti>Apprentice</ti> |
222 |
<ti>On probation</ti> |
223 |
<ti>Team member</ti> |
224 |
<ti>Senior member</ti> |
225 |
<ti>Subproject leads</ti> |
226 |
<ti>Audit member</ti> |
227 |
<ti>Kernel member</ti> |
228 |
</tr> |
229 |
<tr> |
230 |
<ti>GLSAMaker</ti> |
231 |
<ti></ti> |
232 |
<ti>x</ti> |
233 |
<ti>x</ti> |
234 |
<ti>x</ti> |
235 |
<ti>x</ti> |
236 |
<ti>o</ti> |
237 |
<ti></ti> |
238 |
<ti></ti> |
239 |
</tr> |
240 |
<tr> |
241 |
<ti>glsa-commits alias</ti> |
242 |
<ti></ti> |
243 |
<ti>o</ti> |
244 |
<ti>x</ti> |
245 |
<ti>x</ti> |
246 |
<ti>x</ti> |
247 |
<ti>o</ti> |
248 |
<ti></ti> |
249 |
<ti></ti> |
250 |
</tr> <tr> |
251 |
<ti>Channel Op</ti> |
252 |
<ti></ti> |
253 |
<ti></ti> |
254 |
<ti>x</ti> |
255 |
<ti>x</ti> |
256 |
<ti>x</ti> |
257 |
<ti>x</ti> |
258 |
<ti>x</ti> |
259 |
<ti></ti> |
260 |
</tr> <tr> |
261 |
<ti>Developer status</ti> |
262 |
<ti></ti> |
263 |
<ti></ti> |
264 |
<ti>x</ti> |
265 |
<ti>x</ti> |
266 |
<ti>x</ti> |
267 |
<ti>x</ti> |
268 |
<ti>x</ti> |
269 |
<ti>x</ti> |
270 |
</tr> <tr> |
271 |
<ti>Developer account</ti> |
272 |
<ti></ti> |
273 |
<ti></ti> |
274 |
<ti>x</ti> |
275 |
<ti>x</ti> |
276 |
<ti>x</ti> |
277 |
<ti>x</ti> |
278 |
<ti></ti> |
279 |
<ti>x</ti> |
280 |
</tr> <tr> |
281 |
<ti>Security team listing</ti> |
282 |
<ti></ti> |
283 |
<ti></ti> |
284 |
<ti>x</ti> |
285 |
<ti>x</ti> |
286 |
<ti>x</ti> |
287 |
<ti>x</ti> |
288 |
<ti>x</ti> |
289 |
<ti>x</ti> |
290 |
</tr> <tr> |
291 |
<ti>Bugzilla Security group</ti> |
292 |
<ti></ti> |
293 |
<ti></ti> |
294 |
<ti>x</ti> |
295 |
<ti>x</ti> |
296 |
<ti>x</ti> |
297 |
<ti>x</ti> |
298 |
<ti></ti> |
299 |
<ti></ti> |
300 |
</tr> <tr> |
301 |
<ti>security alias</ti> |
302 |
<ti></ti> |
303 |
<ti></ti> |
304 |
<ti>x</ti> |
305 |
<ti>x</ti> |
306 |
<ti>x</ti> |
307 |
<ti>x</ti> |
308 |
<ti></ti> |
309 |
<ti></ti> |
310 |
</tr> <tr> |
311 |
<ti>security-audit alias</ti> |
312 |
<ti></ti> |
313 |
<ti></ti> |
314 |
<ti></ti> |
315 |
<ti>o</ti> |
316 |
<ti>x</ti> |
317 |
<ti>o</ti> |
318 |
<ti>x</ti> |
319 |
<ti></ti> |
320 |
</tr> |
321 |
<tr> |
322 |
<ti>kern-sec alias</ti> |
323 |
<ti></ti> |
324 |
<ti></ti> |
325 |
<ti></ti> |
326 |
<ti>o</ti> |
327 |
<ti>x</ti> |
328 |
<ti>o</ti> |
329 |
<ti></ti> |
330 |
<ti>x</ti> |
331 |
</tr><tr> |
332 |
<ti>gentoo_announce access</ti> |
333 |
<ti></ti> |
334 |
<ti></ti> |
335 |
<ti></ti> |
336 |
<ti>x</ti> |
337 |
<ti>x</ti> |
338 |
<ti></ti> |
339 |
<ti></ti> |
340 |
<ti></ti> |
341 |
</tr><tr> |
342 |
<ti>cvssecurity commit</ti> |
343 |
<ti></ti> |
344 |
<ti></ti> |
345 |
<ti></ti> |
346 |
<ti>x</ti> |
347 |
<ti>x</ti> |
348 |
<ti></ti> |
349 |
<ti></ti> |
350 |
<ti></ti> |
351 |
</tr><tr> |
352 |
<ti>www_glsamaker group</ti> |
353 |
<ti></ti> |
354 |
<ti></ti> |
355 |
<ti></ti> |
356 |
<ti>x</ti> |
357 |
<ti>x</ti> |
358 |
<ti></ti> |
359 |
<ti></ti> |
360 |
<ti></ti> |
361 |
</tr><tr> |
362 |
<ti>vendorsec clearance</ti> |
363 |
<ti></ti> |
364 |
<ti></ti> |
365 |
<ti></ti> |
366 |
<ti></ti> |
367 |
<ti>x</ti> |
368 |
<ti></ti> |
369 |
<ti></ti> |
370 |
<ti></ti> |
371 |
</tr> |
372 |
</table> |
373 |
|
374 |
<p> |
375 |
x: must have |
376 |
</p> |
377 |
|
378 |
<p> |
379 |
o: on-demand |
380 |
</p> |
381 |
|
382 |
</body> |
383 |
</section> |
384 |
</chapter> |
385 |
</guide> |