www-commits
[Top][All Lists]
Advanced

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

www/software README.accounts.html


From: Karl Berry
Subject: www/software README.accounts.html
Date: Sat, 24 Apr 2010 22:26:30 +0000

CVSROOT:        /web/www
Module name:    www
Changes by:     Karl Berry <karl>       10/04/24 22:26:30

Modified files:
        software       : README.accounts.html 

Log message:
        split no account/no ssh key

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

Patches:
Index: README.accounts.html
===================================================================
RCS file: /web/www/www/software/README.accounts.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- README.accounts.html        18 Apr 2010 17:53:28 -0000      1.7
+++ README.accounts.html        24 Apr 2010 22:26:26 -0000      1.8
@@ -1,4 +1,4 @@
-<!-- Parent-Version: $Revision: 1.7 $ -->
+<!-- Parent-Version: $Revision: 1.8 $ -->
 
 <!-- This is the template document for GNU web pages.  We use
      server side includes (#include) for common elements, for
@@ -37,9 +37,9 @@
 <h2>Accounts on GNU machines</h2>
 
 <p>The GNU Project has a general login server named
-<tt>fencepost.gnu.org</tt> which project members can use for their
-email, development and testing.  Some <a href="/prep/maintain/">files
-for GNU maintainers</a> are also kept there.</p>
+<tt>fencepost.gnu.org</tt> which project members can use.  Some <a
+href="/prep/maintain/">files for GNU maintainers</a> are also kept
+there.</p>
 
 <p>The GNU Project also runs a hosting site, <a
 href="http://savannah.gnu.org/";>savannah.gnu.org</a>.  All GNU packages
@@ -48,72 +48,80 @@
 interface.</p>
 
 
-<h3>If you already have a Savannah account</h3>
+<h3>If you have a Savannah account, with ssh key uploaded</h3>
 
-<p>If you already have an account on savannah.gnu.org and have also
-<b>registered an SSH public key there</b>, you can request a shell
-account on fencepost by sending email to <a
+<p>If you already have an account on savannah.gnu.org and <b>have also
+registered an ssh public key there</b>, you can request an account on
+fencepost by sending email to <a
 href="mailto:address@hidden";>&lt;address@hidden&gt;</a> with your
-Savannah user name.  Your SSH public key from Savannah will be used for
-access to fencepost.  Otherwise, keep reading.</p>
+Savannah user name.  Your ssh public key from Savannah will be used for
+access to fencepost.</p>
 
+<p>Your <a href="devel.html">fencepost account can be used</a> for
+email, development and testing related to your work on GNU.</p>
 
-<h3>If you don't yet have a Savannah account</h3>
 
-<p>You need to create a Savannah account and upload your SSH public key
-to Savannah.<p>
+<h3>If you have a Savannah account, but no ssh key uploaded</h3>
 
-<ol>
-<li>To create your account, please do the following:
-
-<ul>
-<li>Visit <a href="http://savannah.gnu.org/";>http://savannah.gnu.org</a>
-(your browser will need to support https).
-
-<li>Follow the &ldquo;New User&rdquo; link, and follow the directions.
-
-<li>Aside: to manage your web pages, source code, and/or ftp area,
-you can register a project using the &ldquo;Register New
-Project&rdquo; link.
-
-</ul>
-
-<li>To then upload your <a href="http://www.openssh.org/";>OpenSSH</a>
-public key, do the following:
+<p>After logging in to your savannah account, to upload your <a
+href="http://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
+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.  (By the way, you
 <a href="http://meyering.net/nuke-your-DSA-keys/";>should not use DSA
-keys</a>.)
+keys</a>.)</li>
 
 <li>Login to <a href="http://savannah.gnu.org/";>savannah</a> in your
-browser.
+browser.</li>
 
 <li>Click the &ldquo;My Account Conf&rdquo; item in the left-hand
-navigation bar.
+navigation bar.</li>
 
 <li>On the resulting page, click &ldquo;Register an SSH Public
-Key&rdquo; (under Authentication Setup).
+Key&rdquo; (under Authentication Setup).</li>
 
 <li>Paste your OpenSSH public key(s) 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.
+key.  Then click the &ldquo;Update&rdquo; button.</li>
 
 <li>This will bring you back to the Account Configuration 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 should try again.
+line breaks snuck in, so you should try again.</li>
 
 <li>Once you've registered on and uploaded your ssh key(s) to savannah,
 email <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>
 with your savannah user name and they (the FSF sysadmins) will give you
-access to fencepost via those keys.</p>
+access to fencepost via those keys.</li>
+
+</ul>
+
+<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 yet 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>
+
+<ul>
+<li>Visit <a href="http://savannah.gnu.org/";>http://savannah.gnu.org</a>
+(your browser will need to support https).</li>
+
+<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,
+you can register a project using the &ldquo;Register New
+Project&rdquo; link.</li>
 
 </ul>
-</ol>
+
+<p>Then follow the instructions in the previous two sections.</p>
 
 
 <h3>Problems?</h3>
@@ -154,7 +162,7 @@
 
 <p>Updated:
 <!-- timestamp start -->
-$Date: 2010/04/18 17:53:28 $
+$Date: 2010/04/24 22:26:26 $
 <!-- timestamp end -->
 </p>
 </div>




reply via email to

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