[Savannah-cvs] administration/content/gnu-content/faq User_Acc...

[Sylvain Beucler]

CVSROOT:        /web/administration
Module name:    administration
Changes by:     Sylvain Beucler <Beuc>  07/03/18 13:38:01

Modified files:
        content/gnu-content/faq: 
                                 
User_Account_-_How_do_I_configure_my_SSH_access.txt 

Log message:
        Moved SSH Access to http://savannah.gnu.org/maintenance/SshAccess

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/administration/content/gnu-content/faq/User_Account_-_How_do_I_configure_my_SSH_access.txt?cvsroot=administration&r1=1.6&r2=1.7

Patches:
Index: User_Account_-_How_do_I_configure_my_SSH_access.txt
===================================================================
RCS file: 
/web/administration/administration/content/gnu-content/faq/User_Account_-_How_do_I_configure_my_SSH_access.txt,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- User_Account_-_How_do_I_configure_my_SSH_access.txt 5 Apr 2006 00:42:55 
-0000       1.6
+++ User_Account_-_How_do_I_configure_my_SSH_access.txt 18 Mar 2007 13:38:01 
-0000      1.7
@@ -1,133 +1 @@
-<h3>Short version</h3>
-
-<p>You can simply setup your SSH key by typing in a terminal:
-<pre>ssh-keygen -t dsa</pre> Then copy <code>~/.ssh/id_dsa.pub</code>
-at http://savannah.gnu.org/my/admin/editsshkeys.php (once logged
-in).</p>
-
-
-<h3>Detailed version</h3>
-
-<p>Generally, if you can't access to your CVS trees or your download
-area, it means that your SSH access is not correctly configured. The
-<i>only</i> thing to do is to create a ssh-key and register it.</p>
-
-<p>Note that if you're not member of any project, no account will
-created on the system - you will have your web account, but not system
-access. A system account will be created after you become a member of
-at least one project.</p>
-
-<p>First, you need to create the ssh-key. In general, this is done by
-using <pre>ssh-keygen -t dsa</pre> It will ask you for a
-passphrase. Only this passphrase will be accepted for CVS or scp
-authentification, <b class="error">not the Savannah password</b>. The
-public key will be placed at <code>~/.ssh/id_dsa.pub</code>.</p>
-
-<p>You must register your public key in the Account Maintenance page
-(http://savannah.gnu.org/my/admin/editsshkeys.php). Make sure there are
-no line breaks except between keys - more information in the Account
-Maintenance page. After submitting, verify that the number of keys in
-your file is what you expected.</p>
-
-<p>You can publish several public keys, which is often needed when you
-connect to Savannah from different computers. You can delete them when
-you do not use that key pair anymore.</p>
-
-<p>Wait for the next cron job (in the worst case, 1 hour).
-
-<p>Try to download your CVS tree (take a look at your CVS project page
-- or read *How do I import my project into the CVS?*)</p>
-
-
-<h3>Troubleshootings</h3>
-
-<ul><li><p>If, when (for example) you try to use CVS, it asks you for
-a <i>password</i> and not a <i>passphrase</i>, then means that your
-key is not recognized. It could be a matter of time (cron job) or,
-generally, it means that your key is not a correct SSH2 DSA key (the
-key registration page contains a sample key for you to compare). If
-you think you have done everything correctly, use the support manager
-(https://savannah.gnu.org/support/?group=administration) or write to
address@hidden explaining your problem, providing
-copy/paste from the errors messages. It would also be good to provide
-the output from
-
-<pre>cvs -t 
-d:ext:<i>yourlogin</i>@cvs.savannah.gnu.org/cvsroot/<i>yourproject</i> co 
<i>yourproject</i></pre>
-
-and the output from:
-
-<pre>ssh -v <i>yourlogin</i>@cvs.savannah.gnu.org</pre>
-
-</p></li>
-
-
-<li><p>When you try to cvs, it will reports <code>the authenticity of
-host subversions.gnu.org cannot be established, RSA key fingerprint is
-80:5a:b0:0c:ec:93:66:29:49:7e:04:2b:fd:ba:2c:d5</code>.
-
-Why RSA here and not DSA? This is the RSA fingerprint of the Savannah
-site-wide server key. It is used to verify that the site you are
-connecting to is well GNU Savannah, and not a fake website. It is
-totally different from your SSH key.</p></li>
-
-
-<li><p><em>When trying to connect, I get <i>Protocol major versions
-differ: 1 vs. 2</i></em></p>
-
-<p>First, you should know that here, on Savannah, we use SSH version
-2. The error you got means that either:
-<ul><li>You are using an old implementation of SSH that does not support 
protocol version 2 - you need to upgrade.</li>
-<li>OpenSSH is configured, site-wide, to use protocol version 1 only. In this 
case, you need to edit <code>/etc/ssh/ssh_config</code>, and replace
-<pre>
-Protocol 1
-</pre>
-by
-<pre>
-Protocol 2,1
-</pre>
-<li>You configured SSH to use version 1 when connecting to Savannah. If you 
see something like:
-<pre>
-Protocol 1
-</pre>
-or
-<pre>
-Host cvs.savannah.gnu.org
-     Protocol 1
-</pre>
-then simply remove it (or see next question).
-</li></ul>
-
-
-<li><p><em>It is necessary to specify <code>Protocol 2</code> in the SSH
-configuration files?</em></p>
-
-<p>It is usually not needed to precise it in the SSH client
-configuration files (<code>~/.ssh/config</code> and
-<code>/etc/ssh/ssh_config</code>).
-
-<p>You can however add
-
-<pre>
-Host cvs.savannah.gnu.org
-     Protocol 2
-</pre>
-
-in that file when you think your SSH client will try to make a SSHv1
-connection by default. You can incidentally do that as well to avoid a
-man-in-the-middle attack that tries to move the connection from
-protocol 2 to protocol 1 during its establishment, since v1 has some
-flaws and is more easily crackable).</p></li>
-
-<li>
-<p><em>My key has several lines, how do I enter it?</em></p>
-
-
-<p>Note that we only support free implementations of SSH, such as
-http://www.openssh.org. If you public key is several-lines-long, and
-begins with <code>---- BEGIN SSH2 PUBLIC KEY ----</code>, then you are
-using a proprietary version that we do not support.</p></li>
-
-</ol>
-
-
-<p style="font-size: smaller">Updated $Date: 2006/04/05 00:42:55 $</p>
+FAQ moved here: http://savannah.gnu.org/maintenance/SshAccess