/[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.1 Revision 1.4
1GLEP: 14 1GLEP: 14
2Title: security updates based on GLSA 2Title: security updates based on GLSA
3Version: $Revision: 1.1 $ 3Version: $Revision: 1.4 $
4Last-Modified: $Date: 2003/08/22 15:00:55 $ 4Last-Modified: $Date: 2003/11/10 19:21:57 $
5Author: Marius Mauch <genone@genone.de>, 5Author: Marius Mauch <genone@genone.de>,
6Status: Draft 6Status: Accepted
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, 24-Aug-2003, 10-Nov-2003
10 11
11 12
12Abstract 13Abstract
13======== 14========
14 15
30=============== 31===============
31 32
32Update tool 33Update tool
33----------- 34-----------
34 35
35The 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
36the 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
37on user preferences: 38following actions, depending on user preferences:
38 39
39- 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
40 daemon restarts. 41 daemon restarts.
41- instruct the user how to fix the security hole. 42- instruct the user how to fix the security hole.
42- 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.
49----------- 50-----------
50 51
51The 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
52parsing and later extensions. See `implementation`_ for a sample DTD. The format 53parsing and later extensions. See `implementation`_ for a sample DTD. The format
53has 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
54tool 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 (update:
56a QT based editor for the GLSA format written by plasmaroo exists in the
57gentoo-projects repository). Every GLSA has to be GPG signed by the responsible
58developer, who has to be a member of the security herd.
55 59
56 60
57GLSA release process 61GLSA release process
58-------------------- 62--------------------
59 63
60Additional to sending the GLSA to the gentoo-announce mailing list it has to be 64Additional to sending the GLSA to the gentoo-announce mailing list it has to be
61stored on a HTTP/FTP server and in the portage tree. I'd suggest a script should 65stored on a HTTP/FTP server and in the portage tree. I'd suggest a script should
62be used to release a GLSA that will: 66be used to release a GLSA that will:
63 67
64- check the GLSA for correctness 68- check the GLSA for correctness
69- sign the GLSA with the developers GPG key
65- send a mail to gentoo-announce with the XML GLSA and a plaintext version attached 70- send a mail to gentoo-announce with the XML GLSA and a plaintext version attached
66- upload it to www.gentoo.org/glsa (or wherever they should be uploaded) 71- upload it to www.gentoo.org/security/en/glsa (via cvs commit)
67- put it on the rsync server 72- put it on the rsync server (via cvs commit)
68- notify the moderators on the forums to make an announcement 73- notify the moderators on the forums to make an announcement
69 74
70 75
71Portage changes 76Portage changes
72--------------- 77---------------
95Putting the GLSAs in the portage tree allows all users to check their systems 100Putting the GLSAs in the portage tree allows all users to check their systems
96for security updates without taking more actions and simplifies later integration 101for security updates without taking more actions and simplifies later integration
97of the update tool into portage. For security minded persons the GLSAs are 102of the update tool into portage. For security minded persons the GLSAs are
98available on a HTTP server to ease the load of the rsync servers. 103available on a HTTP server to ease the load of the rsync servers.
99 104
105To verify the signatures of the GLSAs the public keys of the developers should be
106available in the portage tree and on the HTTP server. The verification is necessary
107to prevent exploits by fake GLSAs.
108
100 109
101Implementation 110Implementation
102============== 111==============
103 112
104A prototype implementation (including the update tool, a DTD and a sample 113A prototype implementation (including the update tool, a DTD and a sample
105XMLified GLSA) exists at http://gentoo.devel-net.org/glsa/ . This GLEP is based 114XMLified GLSA) exists at http://gentoo.devel-net.org/glsa/ and in the
115gentoo-projects/gentoo-security/GLSA repository. This GLEP is based
106on that implementation, though it can be changed or rewritten if necessary. 116on that implementation, though it can be changed or rewritten if necessary.
107According to portage developers there is also already some support for this in
108portage.
109 117
110 118
111Backwards compatibility 119Backwards compatibility
112======================= 120=======================
113 121

Legend:
Removed from v.1.1  
changed lines
  Added in v.1.4

  ViewVC Help
Powered by ViewVC 1.1.20