/[gentoo]/xml/htdocs/proj/en/glep/glep-0014.txt
Gentoo

Diff of /xml/htdocs/proj/en/glep/glep-0014.txt

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.2 Revision 1.3
1GLEP: 14 1GLEP: 14
2Title: security updates based on GLSA 2Title: security updates based on GLSA
3Version: $Revision: 1.2 $ 3Version: $Revision: 1.3 $
4Last-Modified: $Date: 2003/08/22 15:11:16 $ 4Last-Modified: $Date: 2003/08/24 22:11:46 $
5Author: Marius Mauch <genone@genone.de>, 5Author: Marius Mauch <genone@genone.de>,
6Status: Draft 6Status: Draft
7Type: Standards Track 7Type: Standards Track
8Content-Type: text/x-rst 8Content-Type: text/x-rst
9Created: 18 Aug 2003 9Created: 18 Aug 2003
10Post-History: 22-Aug-2003 10Post-History: 22-Aug-2003, 24-Aug-2003
11 11
12 12
13Abstract 13Abstract
14======== 14========
15 15
31=============== 31===============
32 32
33Update tool 33Update tool
34----------- 34-----------
35 35
36The coding part of this GLEP is a update tool that reads a GLSA, checks if 36The coding part of this GLEP is a update tool that reads a GLSA, verifies its
37the system is affected by it and executes one of the following actions, depending 37GPG signature, checks if the system is affected by it and executes one of the
38on user preferences: 38following actions, depending on user preferences:
39 39
40- run all steps necessary to fix the security hole, including package updates and 40- run all steps necessary to fix the security hole, including package updates and
41 daemon restarts. 41 daemon restarts.
42- instruct the user how to fix the security hole. 42- instruct the user how to fix the security hole.
43- print the GLSA so the user can get more information if desired. 43- print the GLSA so the user can get more information if desired.
51 51
52The GLSA format needs to be specified, I suggest using XML for that to simplify 52The GLSA format needs to be specified, I suggest using XML for that to simplify
53parsing and later extensions. See `implementation`_ for a sample DTD. The format 53parsing and later extensions. See `implementation`_ for a sample DTD. The format
54has to be compatible with the update tool of course. If necessary a converter 54has to be compatible with the update tool of course. If necessary a converter
55tool or an editor could be written for people not comfortable with XML. 55tool or an editor could be written for people not comfortable with XML.
56Every GLSA has to be GPG signed by the responsible developer, who has to be
57a member of the security herd.
56 58
57 59
58GLSA release process 60GLSA release process
59-------------------- 61--------------------
60 62
61Additional to sending the GLSA to the gentoo-announce mailing list it has to be 63Additional to sending the GLSA to the gentoo-announce mailing list it has to be
62stored on a HTTP/FTP server and in the portage tree. I'd suggest a script should 64stored on a HTTP/FTP server and in the portage tree. I'd suggest a script should
63be used to release a GLSA that will: 65be used to release a GLSA that will:
64 66
65- check the GLSA for correctness 67- check the GLSA for correctness
68- sign the GLSA with the developers GPG key
66- send a mail to gentoo-announce with the XML GLSA and a plaintext version attached 69- send a mail to gentoo-announce with the XML GLSA and a plaintext version attached
67- upload it to www.gentoo.org/glsa (or wherever they should be uploaded) 70- upload it to www.gentoo.org/glsa (or wherever they should be uploaded)
68- put it on the rsync server 71- put it on the rsync server
69- notify the moderators on the forums to make an announcement 72- notify the moderators on the forums to make an announcement
70 73
96Putting the GLSAs in the portage tree allows all users to check their systems 99Putting the GLSAs in the portage tree allows all users to check their systems
97for security updates without taking more actions and simplifies later integration 100for security updates without taking more actions and simplifies later integration
98of the update tool into portage. For security minded persons the GLSAs are 101of the update tool into portage. For security minded persons the GLSAs are
99available on a HTTP server to ease the load of the rsync servers. 102available on a HTTP server to ease the load of the rsync servers.
100 103
104To verify the signatures of the GLSAs the public keys of the developers should be
105available in the portage tree and on the HTTP server. The verification is necessary
106to prevent exploits by fake GLSAs.
107
101 108
102Implementation 109Implementation
103============== 110==============
104 111
105A prototype implementation (including the update tool, a DTD and a sample 112A prototype implementation (including the update tool, a DTD and a sample

Legend:
Removed from v.1.2  
changed lines
  Added in v.1.3

  ViewVC Help
Powered by ViewVC 1.1.20