www-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

www/software README.accounts.html


From: Ineiev
Subject: www/software README.accounts.html
Date: Tue, 23 Nov 2021 02:25:31 -0500 (EST)

CVSROOT:        /web/www
Module name:    www
Changes by:     Ineiev <ineiev> 21/11/23 02:25:31

Modified files:
        software       : README.accounts.html 

Log message:
        Update to boilerplate 1.96; add GPG-related instructions, RT #1780595.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/software/README.accounts.html?cvsroot=www&r1=1.26&r2=1.27

Patches:
Index: README.accounts.html
===================================================================
RCS file: /web/www/www/software/README.accounts.html,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -b -r1.26 -r1.27
--- README.accounts.html        12 May 2021 01:55:15 -0000      1.26
+++ README.accounts.html        23 Nov 2021 07:25:28 -0000      1.27
@@ -1,5 +1,6 @@
 <!--#include virtual="/server/header.html" -->
-<!-- Parent-Version: 1.79 -->
+<!-- Parent-Version: 1.96 -->
+<!-- This page is derived from /server/standards/boilerplate.html -->
 <title>Accounts on GNU machines
 - GNU Project - Free Software Foundation</title>
 <!--#include virtual="/server/gnun/initial-translations-list.html" -->
@@ -12,55 +13,49 @@
 also kept (only) on that host.</p>
 
 <p>The GNU Project also runs a hosting site, <a
-href="http://savannah.gnu.org/";>savannah.gnu.org</a>.  All GNU packages
+href="//savannah.gnu.org/">savannah.gnu.org</a>.  All GNU packages
 are welcome and encouraged to use it, and non-GNU packages are welcome
-too.  Creating accounts on savannah is done through its web
-interface.  Please note, Savannah and Fencepost accounts are not linked.
+too.  Creating accounts on Savannah is done through its web
+interface.  Please note, Savannah and fencepost accounts are not linked.
 You will need to contact accounts@gnu.org if you have lost access
 to your account.</p>
 
-<p>(Additional <a href="devel.html">resources for GNU developers</a> are
+<p>(Additional <a href="/software/devel.html">resources for GNU developers</a> 
are
 available, besides these accounts.)</p>
 
-<h3>If you have a Savannah account, with ssh key uploaded</h3>
+<h3>If you don't have a Savannah account</h3>
+
+<p>You need to create a Savannah account and upload your SSH public keys
+to Savannah.  To create your account, do the following:</p>
 
-<p>If you have an account on savannah.gnu.org and <b>have registered an
-RSA public key for ssh there</b>, you can request an account on
-fencepost by sending email to <a
-href="mailto:accounts@gnu.org";>&lt;accounts@gnu.org&gt;</a> with the
-following information:</p>
 <ul>
-<li>Your full name.</li>
-<li>Primary use(s) of your fencepost account (e.g., &ldquo;maintainer of
-    GNU Foobar&rdquo;).</li>
-<li>Requested username for fencepost account.</li>
-<li>An email address that does not deliver via FSF or GNU.</li>
-<li>Phone numbers and time of day where we can contact you to
-    confirm fingerprints.</li>
-<li>Your postal mailing address.</li>
-<li>The RSA public key you registered for ssh on savannah.</li>
-</ul>
+<li>Visit <a href="https://savannah.gnu.org/";>https://savannah.gnu.org</a>
+(your browser will need to support https).</li>
 
-<p>Your ssh public key from Savannah will be used for access to
-fencepost.  Your <a href="devel.html">fencepost account can be used</a>
-for email, development and testing related to your work on GNU.</p>
+<li>Follow the &ldquo;New User&rdquo; link, and follow the directions.</li>
 
+<li>Aside: to manage your web pages, source code, and/or ftp area (these
+are all independent), you can register a project using the
+&ldquo;Register New Project&rdquo; link.</li>
 
-<h3>If you have a Savannah account, but no ssh key uploaded</h3>
+</ul>
+
+
+<h3>If you have a Savannah account, but no SSH key uploaded</h3>
 
-<p>After logging in to your savannah account, to upload your <a
-href="http://www.openssh.org/";>OpenSSH</a> public key, do the
+<p>To upload your <a
+href="https://www.openssh.org/";>OpenSSH</a> public key, do the
 following:</p>
 
 <ul>
-<li>On each machine from which you'll want to connect to savannah,
-run <code>ssh-keygen</code> to generate an ssh RSA keypair.  The
+<li>On each machine from which you'll want to connect to Savannah,
+run <code>ssh-keygen</code> to generate an SSH RSA keypair.  The
 resulting public key will be left in <code>~/.ssh/id_rsa.pub</code>,
 which contains one very long line of ASCII text.  (<a
-href="http://meyering.net/nuke-your-DSA-keys/";>Do not use DSA
+href="https://meyering.net/nuke-your-DSA-keys/";>Do not use DSA
 keys</a>.)</li>
 
-<li>Login to <a href="http://savannah.gnu.org/";>savannah</a> in a web
+<li>Log in to <a href="https://savannah.gnu.org/";>Savannah</a> in a web
 browser.</li>
 
 <li>Click the &ldquo;My Account Conf&rdquo; item in the left-hand
@@ -69,45 +64,70 @@
 <li>On the resulting page, click &ldquo;Register an SSH Public
 Key&rdquo; (under &ldquo;Authentication Setup&rdquo;).</li>
 
-<li>Paste your ssh RSA public key(s) in the &ldquo;Authorized
+<li>Paste your SSH RSA public keys in the &ldquo;Authorized
 keys&rdquo; text field.  Make sure there are no line breaks within a
 key.  Then click the &ldquo;Update&rdquo; button.</li>
 
-<li>This will bring you back to the &ldquo;Account Configuration&rdquo;
+<li>This will bring you back to the &ldquo;My Account Configuration&rdquo;
 page.  Verify that the number of &ldquo;SSH Public Keys
 registered&rdquo; is the same number that you actually uploaded.  If it
 is higher, then some extra line breaks snuck in, so you need to try
 again.</li>
 
-<li>Once you've registered on and uploaded your ssh key(s) to savannah,
-email <a href="mailto:accounts@gnu.org";>&lt;accounts@gnu.org&gt;</a>
-with the info listed in the above section and they (the FSF sysadmins)
-will give you access.</li>
-
 </ul>
 
-<p>(By the way, you'll also need to have an ssh key uploaded in order to
+<p>(By the way, you'll also need to have an SSH key uploaded in order to
 make commits to repositories.)</p>
 
 
-<h3>If you don't have a Savannah account</h3>
-
-<p>You need to create a Savannah account and upload your ssh public key
-to Savannah.  To create your account, do the following:</p>
+<h3>If you have a Savannah account, but no GPG key uploaded</h3>
 
 <ul>
-<li>Visit <a href="http://savannah.gnu.org/";>http://savannah.gnu.org</a>
-(your browser will need to support https).</li>
+<li>If you have no GPG key, run <code>gpg --gen-key</code> in order
+to generate a key.</li>
 
-<li>Follow the &ldquo;New User&rdquo; link, and follow the directions.</li>
+<li>Export your public key to a text file: <code>gpg -a --export
+<var>[your-key-fingerprint]</var> &lt; key.asc</code>.  Key fingerprint
+is a 40-digit hexadecimal number, you can see it when you run
+<code>gpg --list-secret-keys</code>.</li>
 
-<li>Aside: to manage your web pages, source code, and/or ftp area (these
-are all independent), you can register a project using the
-&ldquo;Register New Project&rdquo; link.</li>
+<li>Log in to your account and visit &ldquo;My Account Conf&rdquo; &rarr;
+&ldquo;Edit GPG Key.&rdquo;</li>
+
+<li>Paste your key and check it with the &ldquo;Test GPG keys&rdquo;
+button.</li>
 
+<li>If everything looks good, register your key with the &ldquo;Update&rdquo;
+button.</li>
+
+</ul>
+
+
+<h3>If you have a Savannah account, with GPG and SSH keys uploaded</h3>
+
+<p>If you have an account on savannah.gnu.org and have registered
+SSH and GPG public keys, you can request an account on
+fencepost by sending email to <a
+href="mailto:accounts@gnu.org";>&lt;accounts@gnu.org&gt;</a> with the
+following information:</p>
+<ul>
+<li>Your full name.</li>
+<li>Primary uses of your fencepost account (e.g., &ldquo;maintainer of
+    GNU Foobar&rdquo;).</li>
+<li>Requested username for fencepost account.</li>
+<li>An email address that does not deliver via FSF or GNU.</li>
+<li>Phone numbers and time of day where we can contact you to
+    confirm fingerprints.</li>
+<li>Your postal mailing address.</li>
+<li>The SSH and GPG public keys you registered on Savannah.</li>
 </ul>
 
-<p>Then follow the instructions in the previous two sections.</p>
+<p>Sign your message before sending with a command like
+<code>gpg --clear-sign message.txt</code>.</p>
+
+<p>Your SSH public key from Savannah will be used for access to
+fencepost.  Your <a href="/software/devel.html">fencepost account can be 
used</a>
+for email, development and testing related to your work on GNU.</p>
 
 
 <h3>First login on fencepost.gnu.org</h3>
@@ -143,12 +163,12 @@
 
 <p>If you have questions about or problems with using fencepost once you
 have an account, additional user support is available on the <a
-href="http://lists.gnu.org/mailman/listinfo/fencepost-users";>fencepost-users</a>
+href="https://lists.gnu.org/mailman/listinfo/fencepost-users";>fencepost-users</a>
 mailing list.  Feel free to subscribe.</p>
 
 </div><!-- for id="content", starts in the include above -->
 <!--#include virtual="/server/footer.html" -->
-<div id="footer">
+<div id="footer" role="contentinfo">
 <div class="unprintable">
 
 <p>Please send general FSF &amp; GNU inquiries to
@@ -166,13 +186,13 @@
         to <a href="mailto:web-translators@gnu.org";>
         &lt;web-translators@gnu.org&gt;</a>.</p>
 
-        <p>For information on coordinating and submitting translations of
+        <p>For information on coordinating and contributing translations of
         our web pages, see <a
         href="/server/standards/README.translations.html">Translations
         README</a>. -->
 Please see the <a
 href="/server/standards/README.translations.html">Translations
-README</a> for information on coordinating and submitting translations
+README</a> for information on coordinating and contributing translations
 of this article.</p>
 </div>
 
@@ -203,10 +223,10 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2021/05/12 01:55:15 $
+$Date: 2021/11/23 07:25:28 $
 <!-- timestamp end -->
 </p>
 </div>
-</div>
+</div><!-- for class="inner", starts in the banner include -->
 </body>
 </html>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]