/[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.3 Revision 1.4
1GLEP: 14 1GLEP: 14
2Title: security updates based on GLSA 2Title: security updates based on GLSA
3Version: $Revision: 1.3 $ 3Version: $Revision: 1.4 $
4Last-Modified: $Date: 2003/08/24 22:11:46 $ 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 10Post-History: 22-Aug-2003, 24-Aug-2003, 10-Nov-2003
11 11
12 12
13Abstract 13Abstract
14======== 14========
15 15
50----------- 50-----------
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 (update:
56Every GLSA has to be GPG signed by the responsible developer, who has to be 56a QT based editor for the GLSA format written by plasmaroo exists in the
57a member of the security herd. 57gentoo-projects repository). Every GLSA has to be GPG signed by the responsible
58developer, who has to be a member of the security herd.
58 59
59 60
60GLSA release process 61GLSA release process
61-------------------- 62--------------------
62 63
65be used to release a GLSA that will: 66be used to release a GLSA that will:
66 67
67- check the GLSA for correctness 68- check the GLSA for correctness
68- sign the GLSA with the developers GPG key 69- sign the GLSA with the developers GPG key
69- 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
70- 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)
71- put it on the rsync server 72- put it on the rsync server (via cvs commit)
72- notify the moderators on the forums to make an announcement 73- notify the moderators on the forums to make an announcement
73 74
74 75
75Portage changes 76Portage changes
76--------------- 77---------------
108 109
109Implementation 110Implementation
110============== 111==============
111 112
112A prototype implementation (including the update tool, a DTD and a sample 113A prototype implementation (including the update tool, a DTD and a sample
113XMLified 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
114on that implementation, though it can be changed or rewritten if necessary. 116on that implementation, though it can be changed or rewritten if necessary.
115According to portage developers there is also already some support for this in
116portage.
117 117
118 118
119Backwards compatibility 119Backwards compatibility
120======================= 120=======================
121 121

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

  ViewVC Help
Powered by ViewVC 1.1.20