[patch]: NM page update request (GPG) updated
Hi, here is updated patch ready to be applied.
(I tested my claim : germany.keyserver.net and pgp.ai.mit.edu does not
work. All listed wwwkeys.??.pgp.net works.)
Osamu
--
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +++++
Osamu Aoki <osamu@debian.org> Cupertino CA USA, GPG-key: A8061F32
.''`. Debian Reference: post-installation user's guide for non-developers
: :' : http://qref.sf.net and http://people.debian.org/~osamu
`. `' "Our Priorities are Our Users and Free Software" --- Social Contract
--- nm-step1.wml 2002-10-27 01:46:39.000000000 -0700
+++ nm-step1.wml.new 2002-10-27 10:06:56.000000000 -0800
@@ -29,10 +29,12 @@
fill out a web form and thereby verify the applicant's application (More
information about the Advocate system can be found in the
<A HREF="./nm-advocate">guidelines for advocates</A>).
-<LI>a way to <A HREF = "./nm-step2">identify</A> himself (preferably by
-having a GPG key signed by an existing Debian Developer or, alternatively,
-by sending in a photo of his drivers license or passport signed digitally
-with his GPG key).
+<LI>a way to <A HREF = "./nm-step2">identify</A> himself by
+having a GPG key signed by an existing Debian Developer.
+Only for people living in areas where one can not get his GPG key
+signed by an existing Debian Developer, sending in a photo of his
+drivers license or passport signed digitally with his GPG key may be
+accepted as the alternative method to identify himself.
<LI>enough experience in order to become an official Debian Developer
(the preferred way is to have a package
<A HREF ="./newmaint#Sponsor">sponsored</A> by a Debian developer; of course,
--- nm-step2.wml 2002-09-23 10:02:24.000000000 -0700
+++ nm-step2.wml.new 2002-10-27 10:22:38.000000000 -0800
@@ -45,13 +45,13 @@
</P>
<P>
-Please make sure that your GPG public key can be found on one of the
-<A HREF="http://wwwkeys.us.pgp.net/";>public key servers</A>. You can
-export your public key using:</P>
+Please make sure that your GPG public key can be found on at least
+one of the <A HREF="http://wwwkeys.us.pgp.net/";>public key servers</A>.
+You can export your public key using:</P>
<pre>
-gpg --send-key --keyserver germany.keyserver.net yourkeyid
+gpg --send-key --keyserver wwwkeys.$xx.pgp.net yourkeyid
</pre>
-
+Here, "$xx" can be any one of "us", "es", "de", "dk", "uk", or "ch".
<P>Note: ElGamal signatures generated by GPG <= 1.0.1 are
incompatible with later versions. Such signatures must be
@@ -60,6 +60,11 @@
ElGamal keys themselves do <em>not</em> need to be regenerated.
Only the signatures created by ElGamal keys.</P>
+<P>Note: It is a good idea to create <em>only one sub-key</em>. If
+you don't, keyservers on pgp.net are known to <em>corrupt</em> your key.
+Neither *.keyserver.net nor pgp.ai.mit.edu are usable recently.
+</P>
+
<P>
You should upgrade GPG to version >= 1.0.4, since the older
version has serious bugs which could lead to false signature
Reply to: