| 1 | <?xml version="1.0" encoding="utf-8" ?> |
1 | <?xml version="1.0" encoding="utf-8" ?> |
| 2 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
2 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
| 3 | <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> |
3 | <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> |
| 4 | <!-- |
4 | |
| 5 | This HTML is auto-generated. DO NOT EDIT THIS FILE! If you are writing a new |
|
|
| 6 | PEP, see http://www.python.org/peps/pep-0001.html for instructions and links |
|
|
| 7 | to templates. DO NOT USE THIS HTML FILE AS YOUR TEMPLATE! |
|
|
| 8 | --> |
|
|
| 9 | <head> |
5 | <head> |
| 10 | <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> |
6 | <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> |
| 11 | <meta name="generator" content="Docutils 0.3.0: http://docutils.sourceforge.net/" /> |
7 | <meta name="generator" content="Docutils 0.4: http://docutils.sourceforge.net/" /> |
| 12 | <title>GLEP 12 -- Gentoo.org Finger Daemon</title> |
8 | <title>GLEP 12 -- Gentoo.org Finger Daemon</title> |
| 13 | <link rel="stylesheet" href="tools/glep.css" type="text/css" /> |
9 | <link rel="stylesheet" href="tools/glep.css" type="text/css" /> |
| 14 | </head> |
10 | </head> |
| 15 | <body bgcolor="white"> |
11 | <body bgcolor="white"> |
| 16 | <table class="navigation" cellpadding="0" cellspacing="0" |
12 | <table class="navigation" cellpadding="0" cellspacing="0" |
| … | |
… | |
| 22 | <td class="textlinks" align="left"> |
18 | <td class="textlinks" align="left"> |
| 23 | [<b><a href="http://www.gentoo.org/">Gentoo Linux Home</a></b>] |
19 | [<b><a href="http://www.gentoo.org/">Gentoo Linux Home</a></b>] |
| 24 | [<b><a href="http://www.gentoo.org/proj/en/glep">GLEP Index</a></b>] |
20 | [<b><a href="http://www.gentoo.org/proj/en/glep">GLEP Index</a></b>] |
| 25 | [<b><a href="http://www.gentoo.org/proj/en/glep/glep-0012.txt">GLEP Source</a></b>] |
21 | [<b><a href="http://www.gentoo.org/proj/en/glep/glep-0012.txt">GLEP Source</a></b>] |
| 26 | </td></tr></table> |
22 | </td></tr></table> |
| 27 | <div class="document"> |
|
|
| 28 | <table class="rfc2822 field-list" frame="void" rules="none"> |
23 | <table class="rfc2822 docutils field-list" frame="void" rules="none"> |
| 29 | <col class="field-name" /> |
24 | <col class="field-name" /> |
| 30 | <col class="field-body" /> |
25 | <col class="field-body" /> |
| 31 | <tbody valign="top"> |
26 | <tbody valign="top"> |
| 32 | <tr class="field"><th class="field-name">GLEP:</th><td class="field-body">12</td> |
27 | <tr class="field"><th class="field-name">GLEP:</th><td class="field-body">12</td> |
| 33 | </tr> |
28 | </tr> |
| 34 | <tr class="field"><th class="field-name">Title:</th><td class="field-body">Gentoo.org Finger Daemon</td> |
29 | <tr class="field"><th class="field-name">Title:</th><td class="field-body">Gentoo.org Finger Daemon</td> |
| 35 | </tr> |
30 | </tr> |
| 36 | <tr class="field"><th class="field-name">Version:</th><td class="field-body">1.1</td> |
31 | <tr class="field"><th class="field-name">Version:</th><td class="field-body">1.2</td> |
| 37 | </tr> |
32 | </tr> |
| 38 | <tr class="field"><th class="field-name">Last-Modified:</th><td class="field-body"><a class="reference" href="http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/proj/en/glep/glep-0012.txt?cvsroot=gentoo">2003/08/11 14:32:44</a></td> |
33 | <tr class="field"><th class="field-name">Last-Modified:</th><td class="field-body"><a class="reference" href="http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/proj/en/glep/glep-0012.txt?cvsroot=gentoo">2004/01/31 21:56:55</a></td> |
| 39 | </tr> |
34 | </tr> |
| 40 | <tr class="field"><th class="field-name">Author:</th><td class="field-body">Tavis Ormandy <taviso at gentoo.org></td> |
35 | <tr class="field"><th class="field-name">Author:</th><td class="field-body">Tavis Ormandy <taviso at gentoo.org></td> |
| 41 | </tr> |
36 | </tr> |
| 42 | <tr class="field"><th class="field-name">Status:</th><td class="field-body">Draft</td> |
37 | <tr class="field"><th class="field-name">Status:</th><td class="field-body">Rejected</td> |
| 43 | </tr> |
38 | </tr> |
| 44 | <tr class="field"><th class="field-name">Type:</th><td class="field-body">Standards Track</td> |
39 | <tr class="field"><th class="field-name">Type:</th><td class="field-body">Standards Track</td> |
| 45 | </tr> |
40 | </tr> |
| 46 | <tr class="field"><th class="field-name">Created:</th><td class="field-body">10-Aug-2003</td> |
41 | <tr class="field"><th class="field-name">Created:</th><td class="field-body">10-Aug-2003</td> |
| 47 | </tr> |
42 | </tr> |
| 48 | <tr class="field"><th class="field-name">Post-History:</th><td class="field-body">11-Aug-2003</td> |
43 | <tr class="field"><th class="field-name">Post-History:</th><td class="field-body">11-Aug-2003</td> |
| 49 | </tr> |
44 | </tr> |
| 50 | </tbody> |
45 | </tbody> |
| 51 | </table> |
46 | </table> |
| 52 | <hr /> |
47 | <hr /> |
| 53 | <div class="contents topic" id="contents"> |
48 | <div class="contents topic"> |
| 54 | <p class="topic-title"><a name="contents">Contents</a></p> |
49 | <p class="topic-title first"><a id="contents" name="contents">Contents</a></p> |
| 55 | <ul class="simple"> |
50 | <ul class="simple"> |
|
|
51 | <li><a class="reference" href="#reason-for-rejection" id="id21" name="id21">Reason for rejection</a></li> |
| 56 | <li><a class="reference" href="#abstract" id="id21" name="id21">Abstract</a></li> |
52 | <li><a class="reference" href="#abstract" id="id22" name="id22">Abstract</a></li> |
| 57 | <li><a class="reference" href="#motivation" id="id22" name="id22">Motivation</a></li> |
53 | <li><a class="reference" href="#motivation" id="id23" name="id23">Motivation</a></li> |
| 58 | <li><a class="reference" href="#rationale" id="id23" name="id23">Rationale</a></li> |
54 | <li><a class="reference" href="#rationale" id="id24" name="id24">Rationale</a></li> |
| 59 | <li><a class="reference" href="#implementation-and-security" id="id24" name="id24">Implementation and Security</a></li> |
55 | <li><a class="reference" href="#implementation-and-security" id="id25" name="id25">Implementation and Security</a></li> |
| 60 | <li><a class="reference" href="#example-query" id="id25" name="id25">Example Query</a></li> |
56 | <li><a class="reference" href="#example-query" id="id26" name="id26">Example Query</a></li> |
| 61 | <li><a class="reference" href="#references" id="id26" name="id26">References</a></li> |
57 | <li><a class="reference" href="#references" id="id27" name="id27">References</a></li> |
| 62 | <li><a class="reference" href="#copyright" id="id27" name="id27">Copyright</a></li> |
58 | <li><a class="reference" href="#copyright" id="id28" name="id28">Copyright</a></li> |
| 63 | </ul> |
59 | </ul> |
| 64 | </div> |
60 | </div> |
| 65 | <div class="section" id="abstract"> |
61 | <div class="section"> |
|
|
62 | <h1><a class="toc-backref" href="#id21" id="reason-for-rejection" name="reason-for-rejection">Reason for rejection</a></h1> |
|
|
63 | <p>Information about Gentoo development is already significantly fragmented. |
|
|
64 | Although this GLEP has its merits, the fact that it is a separate source |
|
|
65 | of information, rather than simply another conduit to existing sources |
|
|
66 | of information, poses more problems than it solves. Were this GLEP to |
|
|
67 | be resubmitted/modified so that finger was nothing more than an interface |
|
|
68 | into existing sources of information, it would probably be accepted.</p> |
|
|
69 | </div> |
|
|
70 | <div class="section"> |
| 66 | <h1><a class="toc-backref" href="#id21" name="abstract">Abstract</a></h1> |
71 | <h1><a class="toc-backref" href="#id22" id="abstract" name="abstract">Abstract</a></h1> |
| 67 | <p>The finger protocol is documented in rfc742 <a class="footnote-reference" href="#id11" id="id1" name="id1">[1]</a> and rfc1196 <a class="footnote-reference" href="#id12" id="id2" name="id2">[2]</a>, a simple |
72 | <p>The finger protocol is documented in rfc742 <a class="footnote-reference" href="#id11" id="id1" name="id1">[1]</a> and rfc1196 <a class="footnote-reference" href="#id12" id="id2" name="id2">[2]</a>, a simple |
| 68 | protocol that returns a human readable report about a particular user |
73 | protocol that returns a human readable report about a particular user |
| 69 | of the system. Typically, the information returned will be details such as |
74 | of the system. Typically, the information returned will be details such as |
| 70 | full name, location, etc. These details are entirely optional and are obtained |
75 | full name, location, etc. These details are entirely optional and are obtained |
| 71 | from the system passwd file, which of course can be edited or removed with the |
76 | from the system passwd file, which of course can be edited or removed with the |
| … | |
… | |
| 81 | </blockquote> |
86 | </blockquote> |
| 82 | <p>The finger protocol is mature, secure and widely used in the UNIX community. |
87 | <p>The finger protocol is mature, secure and widely used in the UNIX community. |
| 83 | There are clients available for all major operating systems, and web-based |
88 | There are clients available for all major operating systems, and web-based |
| 84 | clients for those that dont.</p> |
89 | clients for those that dont.</p> |
| 85 | </div> |
90 | </div> |
| 86 | <div class="section" id="motivation"> |
91 | <div class="section"> |
| 87 | <h1><a class="toc-backref" href="#id22" name="motivation">Motivation</a></h1> |
92 | <h1><a class="toc-backref" href="#id23" id="motivation" name="motivation">Motivation</a></h1> |
| 88 | <p>Gentoo developers are already aware of the importance of User Relations <a class="footnote-reference" href="#id19" id="id5" name="id5">[9]</a> .</p> |
93 | <p>Gentoo developers are already aware of the importance of User Relations <a class="footnote-reference" href="#id19" id="id5" name="id5">[9]</a> .</p> |
| 89 | <p>It is essential to keep the community up to date with current goals, status |
94 | <p>It is essential to keep the community up to date with current goals, status |
| 90 | updates, and information from the development team. Currently it is suggested |
95 | updates, and information from the development team. Currently it is suggested |
| 91 | users track mailing lists, monitor the Gentoo bugzilla, developer IRC |
96 | users track mailing lists, monitor the Gentoo bugzilla, developer IRC |
| 92 | channels and cvs commits.</p> |
97 | channels and cvs commits.</p> |
| 93 | <p>While the resources to track developer progress and activity are made |
98 | <p>While the resources to track developer progress and activity are made |
| 94 | available to users, they are not in a form usable to many people. Keeping |
99 | available to users, they are not in a form usable to many people. Keeping |
| … | |
… | |
| 101 | lists even more cluttered with status updates is not desirable.</p> |
106 | lists even more cluttered with status updates is not desirable.</p> |
| 102 | <p>A method that would allow individual developers to keep a log of their |
107 | <p>A method that would allow individual developers to keep a log of their |
| 103 | activities and plans that were instantly accesible to anyone who was |
108 | activities and plans that were instantly accesible to anyone who was |
| 104 | interested would be desirable, I propose running a finger daemon on |
109 | interested would be desirable, I propose running a finger daemon on |
| 105 | gentoo.org, or dev.gentoo.org and forwarding requests there from gentoo.org.</p> |
110 | gentoo.org, or dev.gentoo.org and forwarding requests there from gentoo.org.</p> |
| 106 | <p>Running a developer finger daemon would improve inter developer communication, |
111 | <p>Running a developer finger daemon would improve inter developer communication, |
| 107 | user communication and relations, and reduce workload on developers who have to |
112 | user communication and relations, and reduce workload on developers who have to |
| 108 | respond to queries from users on project status updates.</p> |
113 | respond to queries from users on project status updates.</p> |
| 109 | <p>In the future, it is foreseen that portage will require a cryptographically |
114 | <p>In the future, it is foreseen that portage will require a cryptographically |
| 110 | secure means of verifying ebuilds aquired from an rsync mirror are identical |
115 | secure means of verifying ebuilds aquired from an rsync mirror are identical |
| 111 | to those checked into the portage tree by a developer <a class="footnote-reference" href="#id20" id="id6" name="id6">[10]</a> . Making developer keys |
116 | to those checked into the portage tree by a developer <a class="footnote-reference" href="#id20" id="id6" name="id6">[10]</a> . Making developer keys |
| 112 | available to users for manually checking the integrity of files, or patches |
117 | available to users for manually checking the integrity of files, or patches |
| 113 | sent to them is important. It has long been known that encouraging the |
118 | sent to them is important. It has long been known that encouraging the |
| 114 | use of gpg among developers is desirable <a class="footnote-reference" href="#id15" id="id7" name="id7">[5]</a> .</p> |
119 | use of gpg among developers is desirable <a class="footnote-reference" href="#id15" id="id7" name="id7">[5]</a> .</p> |
| 115 | <p>Should a security vulnerability of a serious nature ever be reported, |
120 | <p>Should a security vulnerability of a serious nature ever be reported, |
| 116 | standard procedure <a class="footnote-reference" href="#id16" id="id8" name="id8">[6]</a> is to inform vendors before releasing the information |
121 | standard procedure <a class="footnote-reference" href="#id16" id="id8" name="id8">[6]</a> is to inform vendors before releasing the information |
| 117 | to full disclosure security discussion lists. Making the relevant maintainer's |
122 | to full disclosure security discussion lists. Making the relevant maintainer's |
| 118 | key easily obtainable will allow reporters to encrypt their reports.</p> |
123 | key easily obtainable will allow reporters to encrypt their reports.</p> |
| 119 | </div> |
124 | </div> |
| 120 | <div class="section" id="rationale"> |
125 | <div class="section"> |
| 121 | <h1><a class="toc-backref" href="#id23" name="rationale">Rationale</a></h1> |
126 | <h1><a class="toc-backref" href="#id24" id="rationale" name="rationale">Rationale</a></h1> |
| 122 | <p>Providing a finger daemon will allow users to instantly access information on |
127 | <p>Providing a finger daemon will allow users to instantly access information on |
| 123 | developers, and all details of that developers current projects that they decide |
128 | developers, and all details of that developers current projects that they decide |
| 124 | to share.</p> |
129 | to share.</p> |
| 125 | <p>GPG keys for all developers will be instantly availble, and the output of the |
130 | <p>GPG keys for all developers will be instantly availble, and the output of the |
| 126 | finger <a class="reference" href="mailto:devname@gentoo.org">devname@gentoo.org</a> command can be piped into gpg --import to instantly |
131 | finger <a class="reference" href="mailto:devname@gentoo.org">devname@gentoo.org</a> command can be piped into gpg --import to instantly |
| 127 | add it to the users keyring.</p> |
132 | add it to the users keyring.</p> |
| 128 | <p>The following projects use finger for user-developer communications,:</p> |
133 | <p>The following projects use finger for user-developer communications,:</p> |
| 129 | <pre class="literal-block"> |
134 | <pre class="literal-block"> |
| 130 | Latest kernel releases, and developer information. |
135 | Latest kernel releases, and developer information. |
| 131 | $ finger @kernel.org |
136 | $ finger @kernel.org |
| … | |
… | |
| 133 | Developers and organisers are encouraged to keep .plans about their |
138 | Developers and organisers are encouraged to keep .plans about their |
| 134 | activity. |
139 | activity. |
| 135 | $ finger nugget@distributed.net |
140 | $ finger nugget@distributed.net |
| 136 | |
141 | |
| 137 | Latest NASA news, and information from engineers. |
142 | Latest NASA news, and information from engineers. |
| 138 | $ finger nasanews@space.mit.edu |
143 | $ finger nasanews@space.mit.edu |
| 139 | |
144 | |
| 140 | Slackware developers. |
145 | Slackware developers. |
| 141 | $ finger volkerdi@slackware.com |
146 | $ finger volkerdi@slackware.com |
| 142 | |
147 | |
| 143 | FreeBSD developers. |
148 | FreeBSD developers. |
| 144 | $ finger nakai@freebsd.org |
149 | $ finger nakai@freebsd.org |
| 145 | </pre> |
150 | </pre> |
| 146 | </div> |
151 | </div> |
| 147 | <div class="section" id="implementation-and-security"> |
152 | <div class="section"> |
| 148 | <h1><a class="toc-backref" href="#id24" name="implementation-and-security">Implementation and Security</a></h1> |
153 | <h1><a class="toc-backref" href="#id25" id="implementation-and-security" name="implementation-and-security">Implementation and Security</a></h1> |
| 149 | <p>Some admins are concerned about the security of running a finger daemon on their |
154 | <p>Some admins are concerned about the security of running a finger daemon on their |
| 150 | machines, the class of security issues involved with the finger protocol are |
155 | machines, the class of security issues involved with the finger protocol are |
| 151 | commonly referred to as "information leaks" <a class="footnote-reference" href="#id17" id="id9" name="id9">[7]</a>.</p> |
156 | commonly referred to as "information leaks" <a class="footnote-reference" href="#id17" id="id9" name="id9">[7]</a>.</p> |
| 152 | <p>This means an attacker may be able to use a finger daemon to identify valid |
157 | <p>This means an attacker may be able to use a finger daemon to identify valid |
| 153 | accounts on their target, which they would then try to obtain access to.</p> |
158 | accounts on their target, which they would then try to obtain access to.</p> |
| 154 | <p>This scenario does not apply to this implementation, as the gentoo developer |
159 | <p>This scenario does not apply to this implementation, as the gentoo developer |
| 155 | names are already well publicised. <a class="footnote-reference" href="#id18" id="id10" name="id10">[8]</a></p> |
160 | names are already well publicised. <a class="footnote-reference" href="#id18" id="id10" name="id10">[8]</a></p> |
| 156 | <p>No security issues have ever been reported with the fingerd available in gentoo |
161 | <p>No security issues have ever been reported with the fingerd available in gentoo |
| 157 | portage. Finger is used worldwide by universities, unix systems, and development |
162 | portage. Finger is used worldwide by universities, unix systems, and development |
| 158 | projects.</p> |
163 | projects.</p> |
| 159 | <p>Adding dummy users, will be trivial and allow projects such as gentoo-docs, |
164 | <p>Adding dummy users, will be trivial and allow projects such as gentoo-docs, |
| 160 | gentoo-alpha, gentoo-ppc, etc to maintain .plans and .projects. This will allow |
165 | gentoo-alpha, gentoo-ppc, etc to maintain .plans and .projects. This will allow |
| 161 | the projects to maintain more technical details or status updates not suitable |
166 | the projects to maintain more technical details or status updates not suitable |
| 162 | for their project webpages.</p> |
167 | for their project webpages.</p> |
| 163 | <p>Adding data to a plan is a lot simpler than updating webpages.</p> |
168 | <p>Adding data to a plan is a lot simpler than updating webpages.</p> |
| 164 | </div> |
169 | </div> |
| 165 | <div class="section" id="example-query"> |
170 | <div class="section"> |
| 166 | <h1><a class="toc-backref" href="#id25" name="example-query">Example Query</a></h1> |
171 | <h1><a class="toc-backref" href="#id26" id="example-query" name="example-query">Example Query</a></h1> |
| 167 | <p>Should a user want information about the author, this might be the output of |
172 | <p>Should a user want information about the author, this might be the output of |
| 168 | a finger query:</p> |
173 | a finger query:</p> |
| 169 | <pre class="literal-block"> |
174 | <pre class="literal-block"> |
| 170 | $ finger taviso@gentoo.org |
175 | $ finger taviso@gentoo.org |
| 171 | Login: taviso Name: Tavis Ormandy |
176 | Login: taviso Name: Tavis Ormandy |
| 172 | Directory: /home/taviso Shell: /bin/bash |
177 | Directory: /home/taviso Shell: /bin/bash |
| 173 | Last login: dd-mmm-yyyy |
178 | Last login: dd-mmm-yyyy |
| 174 | Mail last read dd-mmm-yyy |
179 | Mail last read dd-mmm-yyy |
| 175 | Project: |
180 | Project: |
| 176 | |
181 | |
| 177 | Currently working on implementing XXX, and porting XXX to XXX. |
182 | Currently working on implementing XXX, and porting XXX to XXX. |
| 178 | |
183 | |
| 179 | Plan: |
184 | Plan: |
| 180 | |
185 | |
| 181 | dd-mmm-yyyy |
186 | dd-mmm-yyyy |
| 182 | |
187 | |
| 183 | Investigating bug #12345, testing patch provided in #12236 |
188 | Investigating bug #12345, testing patch provided in #12236 |
| 184 | |
189 | |
| 185 | Write documentation for new features in XXX. |
190 | Write documentation for new features in XXX. |
| 186 | |
191 | |
| 187 | dd-mmm-yyyy |
192 | dd-mmm-yyyy |
| 188 | |
193 | |
| 189 | Contact acmesoft regarding license for xxx in portage. |
194 | Contact acmesoft regarding license for xxx in portage. |
| 190 | |
195 | |
| 191 | PGP Key: |
196 | PGP Key: |
| 192 | |
197 | |
| 193 | -----BEGIN PGP PUBLIC KEY BLOCK----- |
198 | -----BEGIN PGP PUBLIC KEY BLOCK----- |
| 194 | Version: GnuPG v1.2.1 (Linux) |
199 | Version: GnuPG v1.2.1 (Linux) |
| 195 | (...) |
200 | (...) |
| 196 | -----END PGP PUBLIC KEY BLOCK----- |
201 | -----END PGP PUBLIC KEY BLOCK----- |
| 197 | </pre> |
202 | </pre> |
| 198 | </div> |
203 | </div> |
| 199 | <div class="section" id="references"> |
204 | <div class="section"> |
| 200 | <h1><a class="toc-backref" href="#id26" name="references">References</a></h1> |
205 | <h1><a class="toc-backref" href="#id27" id="references" name="references">References</a></h1> |
| 201 | <table class="footnote" frame="void" id="id11" rules="none"> |
206 | <table class="docutils footnote" frame="void" id="id11" rules="none"> |
| 202 | <colgroup><col class="label" /><col /></colgroup> |
207 | <colgroup><col class="label" /><col /></colgroup> |
| 203 | <tbody valign="top"> |
208 | <tbody valign="top"> |
| 204 | <tr><td class="label"><a class="fn-backref" href="#id1" name="id11">[1]</a></td><td><a class="reference" href="http://www.ietf.org/rfc/rfc0742.txt">http://www.ietf.org/rfc/rfc0742.txt</a></td></tr> |
209 | <tr><td class="label"><a class="fn-backref" href="#id1" name="id11">[1]</a></td><td><a class="reference" href="http://www.ietf.org/rfc/rfc0742.txt">http://www.ietf.org/rfc/rfc0742.txt</a></td></tr> |
| 205 | </tbody> |
210 | </tbody> |
| 206 | </table> |
211 | </table> |
| 207 | <table class="footnote" frame="void" id="id12" rules="none"> |
212 | <table class="docutils footnote" frame="void" id="id12" rules="none"> |
| 208 | <colgroup><col class="label" /><col /></colgroup> |
213 | <colgroup><col class="label" /><col /></colgroup> |
| 209 | <tbody valign="top"> |
214 | <tbody valign="top"> |
| 210 | <tr><td class="label"><a class="fn-backref" href="#id2" name="id12">[2]</a></td><td><a class="reference" href="http://www.ietf.org/rfc/rfc1196.txt">http://www.ietf.org/rfc/rfc1196.txt</a></td></tr> |
215 | <tr><td class="label"><a class="fn-backref" href="#id2" name="id12">[2]</a></td><td><a class="reference" href="http://www.ietf.org/rfc/rfc1196.txt">http://www.ietf.org/rfc/rfc1196.txt</a></td></tr> |
| 211 | </tbody> |
216 | </tbody> |
| 212 | </table> |
217 | </table> |
| 213 | <table class="footnote" frame="void" id="id13" rules="none"> |
218 | <table class="docutils footnote" frame="void" id="id13" rules="none"> |
| 214 | <colgroup><col class="label" /><col /></colgroup> |
219 | <colgroup><col class="label" /><col /></colgroup> |
| 215 | <tbody valign="top"> |
220 | <tbody valign="top"> |
| 216 | <tr><td class="label"><a class="fn-backref" href="#id3" name="id13">[3]</a></td><td><a class="reference" href="http://www.gentoo.org/dyn/pkgs/sys-apps/shadow.xml">http://www.gentoo.org/dyn/pkgs/sys-apps/shadow.xml</a></td></tr> |
221 | <tr><td class="label"><a class="fn-backref" href="#id3" name="id13">[3]</a></td><td><a class="reference" href="http://www.gentoo.org/dyn/pkgs/sys-apps/shadow.xml">http://www.gentoo.org/dyn/pkgs/sys-apps/shadow.xml</a></td></tr> |
| 217 | </tbody> |
222 | </tbody> |
| 218 | </table> |
223 | </table> |
| 219 | <table class="footnote" frame="void" id="id14" rules="none"> |
224 | <table class="docutils footnote" frame="void" id="id14" rules="none"> |
| 220 | <colgroup><col class="label" /><col /></colgroup> |
225 | <colgroup><col class="label" /><col /></colgroup> |
| 221 | <tbody valign="top"> |
226 | <tbody valign="top"> |
| 222 | <tr><td class="label"><a class="fn-backref" href="#id4" name="id14">[4]</a></td><td><a class="reference" href="http://www.gnupg.org">http://www.gnupg.org</a></td></tr> |
227 | <tr><td class="label"><a class="fn-backref" href="#id4" name="id14">[4]</a></td><td><a class="reference" href="http://www.gnupg.org">http://www.gnupg.org</a></td></tr> |
| 223 | </tbody> |
228 | </tbody> |
| 224 | </table> |
229 | </table> |
| 225 | <table class="footnote" frame="void" id="id15" rules="none"> |
230 | <table class="docutils footnote" frame="void" id="id15" rules="none"> |
| 226 | <colgroup><col class="label" /><col /></colgroup> |
231 | <colgroup><col class="label" /><col /></colgroup> |
| 227 | <tbody valign="top"> |
232 | <tbody valign="top"> |
| 228 | <tr><td class="label"><a class="fn-backref" href="#id7" name="id15">[5]</a></td><td><<a class="reference" href="mailto:20030629040521.4316b135.seemant@gentoo.org">20030629040521.4316b135.seemant@gentoo.org</a>></td></tr> |
233 | <tr><td class="label"><a class="fn-backref" href="#id7" name="id15">[5]</a></td><td><<a class="reference" href="mailto:20030629040521.4316b135.seemant@gentoo.org">20030629040521.4316b135.seemant@gentoo.org</a>></td></tr> |
| 229 | </tbody> |
234 | </tbody> |
| 230 | </table> |
235 | </table> |
| 231 | <table class="footnote" frame="void" id="id16" rules="none"> |
236 | <table class="docutils footnote" frame="void" id="id16" rules="none"> |
| 232 | <colgroup><col class="label" /><col /></colgroup> |
237 | <colgroup><col class="label" /><col /></colgroup> |
| 233 | <tbody valign="top"> |
238 | <tbody valign="top"> |
| 234 | <tr><td class="label"><a class="fn-backref" href="#id8" name="id16">[6]</a></td><td><a class="reference" href="http://www.oisafety.org/process.html">http://www.oisafety.org/process.html</a></td></tr> |
239 | <tr><td class="label"><a class="fn-backref" href="#id8" name="id16">[6]</a></td><td><a class="reference" href="http://www.oisafety.org/process.html">http://www.oisafety.org/process.html</a></td></tr> |
| 235 | </tbody> |
240 | </tbody> |
| 236 | </table> |
241 | </table> |
| 237 | <table class="footnote" frame="void" id="id17" rules="none"> |
242 | <table class="docutils footnote" frame="void" id="id17" rules="none"> |
| 238 | <colgroup><col class="label" /><col /></colgroup> |
243 | <colgroup><col class="label" /><col /></colgroup> |
| 239 | <tbody valign="top"> |
244 | <tbody valign="top"> |
| 240 | <tr><td class="label"><a class="fn-backref" href="#id9" name="id17">[7]</a></td><td><a class="reference" href="http://search.linuxsecurity.com/cgi-bin/htsearch?words=information%20leak">http://search.linuxsecurity.com/cgi-bin/htsearch?words=information%20leak</a></td></tr> |
245 | <tr><td class="label"><a class="fn-backref" href="#id9" name="id17">[7]</a></td><td><a class="reference" href="http://search.linuxsecurity.com/cgi-bin/htsearch?words=information%20leak">http://search.linuxsecurity.com/cgi-bin/htsearch?words=information%20leak</a></td></tr> |
| 241 | </tbody> |
246 | </tbody> |
| 242 | </table> |
247 | </table> |
| 243 | <table class="footnote" frame="void" id="id18" rules="none"> |
248 | <table class="docutils footnote" frame="void" id="id18" rules="none"> |
| 244 | <colgroup><col class="label" /><col /></colgroup> |
249 | <colgroup><col class="label" /><col /></colgroup> |
| 245 | <tbody valign="top"> |
250 | <tbody valign="top"> |
| 246 | <tr><td class="label"><a class="fn-backref" href="#id10" name="id18">[8]</a></td><td><a class="reference" href="http://www.gentoo.org/main/en/devlist.xml">http://www.gentoo.org/main/en/devlist.xml</a></td></tr> |
251 | <tr><td class="label"><a class="fn-backref" href="#id10" name="id18">[8]</a></td><td><a class="reference" href="http://www.gentoo.org/main/en/devlist.xml">http://www.gentoo.org/main/en/devlist.xml</a></td></tr> |
| 247 | </tbody> |
252 | </tbody> |
| 248 | </table> |
253 | </table> |
| 249 | <table class="footnote" frame="void" id="id19" rules="none"> |
254 | <table class="docutils footnote" frame="void" id="id19" rules="none"> |
| 250 | <colgroup><col class="label" /><col /></colgroup> |
255 | <colgroup><col class="label" /><col /></colgroup> |
| 251 | <tbody valign="top"> |
256 | <tbody valign="top"> |
| 252 | <tr><td class="label"><a class="fn-backref" href="#id5" name="id19">[9]</a></td><td><a class="reference" href="http://www.gentoo.org/proj/en/devrel/user-relations.xml">http://www.gentoo.org/proj/en/devrel/user-relations.xml</a></td></tr> |
257 | <tr><td class="label"><a class="fn-backref" href="#id5" name="id19">[9]</a></td><td><a class="reference" href="http://www.gentoo.org/proj/en/devrel/user-relations.xml">http://www.gentoo.org/proj/en/devrel/user-relations.xml</a></td></tr> |
| 253 | </tbody> |
258 | </tbody> |
| 254 | </table> |
259 | </table> |
| 255 | <table class="footnote" frame="void" id="id20" rules="none"> |
260 | <table class="docutils footnote" frame="void" id="id20" rules="none"> |
| 256 | <colgroup><col class="label" /><col /></colgroup> |
261 | <colgroup><col class="label" /><col /></colgroup> |
| 257 | <tbody valign="top"> |
262 | <tbody valign="top"> |
| 258 | <tr><td class="label"><a class="fn-backref" href="#id6" name="id20">[10]</a></td><td><a class="reference" href="http://www.gentoo.org/news/en/gwn/20030407-newsletter.xml">http://www.gentoo.org/news/en/gwn/20030407-newsletter.xml</a></td></tr> |
263 | <tr><td class="label"><a class="fn-backref" href="#id6" name="id20">[10]</a></td><td><a class="reference" href="http://www.gentoo.org/news/en/gwn/20030407-newsletter.xml">http://www.gentoo.org/news/en/gwn/20030407-newsletter.xml</a></td></tr> |
| 259 | </tbody> |
264 | </tbody> |
| 260 | </table> |
265 | </table> |
| 261 | </div> |
266 | </div> |
| 262 | <div class="section" id="copyright"> |
267 | <div class="section"> |
| 263 | <h1><a class="toc-backref" href="#id27" name="copyright">Copyright</a></h1> |
268 | <h1><a class="toc-backref" href="#id28" id="copyright" name="copyright">Copyright</a></h1> |
| 264 | <p>This document is released under the Open Publications License.</p> |
269 | <p>This document is released under the Open Publications License.</p> |
| 265 | </div> |
270 | </div> |
| 266 | </div> |
|
|
| 267 | |
271 | |
| 268 | <hr class="footer"/> |
272 | </div> |
| 269 | <div class="footer"> |
273 | <div class="footer"> |
|
|
274 | <hr class="footer" /> |
| 270 | <a class="reference" href="glep-0012.txt">View document source</a>. |
275 | <a class="reference" href="glep-0012.txt">View document source</a>. |
| 271 | Generated on: 2003-08-11 14:32 UTC. |
276 | Generated on: 2007-10-13 13:39 UTC. |
| 272 | Generated by <a class="reference" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. |
277 | Generated by <a class="reference" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. |
|
|
278 | |
| 273 | </div> |
279 | </div> |
| 274 | </body> |
280 | </body> |
| 275 | </html> |
281 | </html> |
| 276 | |
282 | |