savannah-hackers
[Top][All Lists]
Advanced

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

[savannah-help-public] [sr #109210] I can't connect to my repository via


From: Michael Pagan
Subject: [savannah-help-public] [sr #109210] I can't connect to my repository via ssh, but cvs can?
Date: Wed, 28 Dec 2016 23:12:29 +0000 (UTC)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0

Follow-up Comment #3, sr #109210 (project administration):

> First,
> On our servers I see there is one ssh public key configured for you. Please
> double-check on your computer that the fingerprint matches the following:
>     e8:[...]:72:b7 
> using
>     ssh-keygen -l -f ~/.ssh/id_rsa.pub
_I confirm:_ My ssh key fingerprint starts with `e8' and ends with
`72:b7' using the suggested command.

> Second,
> Read-only CVS connections to savannah do not use SSH at all (that is, using
> anonymous cvs in pserver mode listening on tcp port 2401).
> So I'm not sure what exactly is and isn't working.
I was not using anonymous checkout, I used the admin checkout.  The
following command and it's output indicates that the ssh server is
started when I checkout my repository (perhaps I'm interpreting it
wrong, but that's what it _looks_ like):

$ cvs -t -d:ext:address@hidden:/sources/genshiken co
genshiken |& grep ssh
 -> Starting server: ssh -l pegzmasta cvs.savannah.nongnu.org cvs server

> Third,
> <snip>
> Can you please try to connect with SSH to the following two hosts:
>
>     $ host vcs.savannah.gnu.org
>     vcs.savannah.gnu.org has address 208.118.235.72
>     $ ssh address@hidden

*Trying the first host, `vcs':*

$ host vcs.savannah.gnu.org
vcs.savannah.gnu.org has address 208.118.235.72

$ ssh address@hidden
Linux vcs.savannah.gnu.org 2.6.32-5-xen-686 #1 SMP Fri Feb 5 18:24:28 UTC 2016
i686

Interactive shell login is not possible for security reasons.
VCS commands are allowed.
You tried to execute: 
Sorry, you are not allowed to execute that command.
Connection to vcs.savannah.gnu.org closed.

> and
>
>     $ host vcs0.savannah.gnu.org
>     vcs0.savannah.gnu.org has address 208.118.235.201
>     $ ssh address@hidden
>  
> And tell us what are the results ?

*Trying the second host, `vcs0':*

$ host vcs0.savannah.gnu.org
vcs0.savannah.gnu.org has address 208.118.235.201

$ ssh address@hidden
The authenticity of host 'vcs0.savannah.gnu.org (208.118.235.201)' can't be
established.
ECDSA key fingerprint is 65:b8:1c:2f:82:7c:0e:39:e1:4a:63:f2:13:10:e8:9c.
Are you sure you want to continue connecting (yes/no)? yes
yes
Warning: Permanently added 'vcs0.savannah.gnu.org' (ECDSA) to the list of
known hosts.
Warning: the ECDSA host key for 'vcs0.savannah.gnu.org' differs from the key
for the IP address '208.118.235.201'
Offending key for IP in /home/pagan/.ssh/known_hosts:11
Are you sure you want to continue connecting (yes/no)? no
no
Host key verification failed.

*After receiving that error, I removed the "Offending key" with the
following command:*

$ sed -i '11d' /home/pagan/.ssh/known_hosts

*Afterwords, I tried again and received what I believe are the correct
results:*


$ host vcs0.savannah.gnu.org
vcs0.savannah.gnu.org has address 208.118.235.201

$ ssh address@hidden
Welcome to Trisquel GNU/Linux 7.0, Belenos (GNU/Linux 3.13.0-105-generic
x86_64)
   ___        ___               ___        ___       ___        ___       
___
  /\  \      /\  \      ___    /\  \      /\  \     /\__\      /\  \     
/\__\
  \ \  \    /  \  \    /\  \  /  \  \    /  \  \   / /  /     /  \  \    / / 
/
   \ \  \  / /\ \  \   \ \  \/ /\ \  \  / /\ \  \ / /  /     / /\ \  \  / / 
/
   /  \  \/  \ \ \  \  /  \__\ \ \ \  \/ /  \ \  \ /  /  ___/  \ \ \  \/ /  /
  / /\ \__\/\ \ \ \__\/ /\/__/\ \ \ \__\/__/ \ \__\__/  /\__\/\ \ \ \__\/__/
 / /  \/__/_|  \/ /  / /  /\ \ \ \ \/__/\  \ / /  /  \ / /  /\ \ \ \/__/\  \
/ /  /      | |  /  / /__/  \ \ \ \__\ \ \/\/ /  / \  / /  /\ \ \ \__\ \ \  \
\/__/       | |\/__/\ \__\   \ \/ /  /  \    /  / \ \/ /  /  \ \ \/__/  \ \ 
\
            | |  |   \/__/    \  /  /    \  /  /   \  /  /    \ \__\     \
\__\
             \|__|             \/__/      \/__/     \/__/      \/__/     
\/__/

Welcome to Trisquel GNU/Linux
Documentation: http://trisquel.info/wiki/

  The programs included with the Trisquel GNU/Linux system are free software.
  The exact distribution terms for each program are described in the
individual
  files in /usr/share/doc/*/copyright.

  Trisquel GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted
  by applicable law.


  The programs included with the Trisquel GNU/Linux system are free software.
  The exact distribution terms for each program are described in the
individual
  files in /usr/share/doc/*/copyright.

  Trisquel GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted
  by applicable law.

Last login: Wed Dec 28 17:39:08 2016 from ool-2f149472.dyn.optonline.net
You tried to execute: 
Sorry, you are not allowed to execute that command.
Connection to vcs0.savannah.gnu.org closed.


> If your SSH key is working, you should see the following message from both
> servers:
>
>      Interactive shell login is not possible for security reasons.
>      VCS commands are allowed.
>      Last login: Wed Dec 28 04:58:11 2016 from X.X.X.X
>      You tried to execute: 
>      Sorry, you are not allowed to execute that command.
>      Connection to vcs.savannah.gnu.org closed.

I received this message from both servers.

> If you SSH key is not working, then on 'vcs' you should see immediately
> the message "Permission denied (publickey).",

I did not experience this.

> but on 'vcs0' you will be asked for a password (which will never be
> accepted).

I experienced this; however, I corrected that error with sed; tried again,
and then I received the working message: "_Sorry, you are not allowed to
execute that command_."  I don't know what caused the initial error?

> <snip>
> Lastly,
> You've mentioned you have been using 'scp' to store files on
> 'download.savannah.gnu.org' and you've been using a password to login - can
> you confirm this is what you meant, and it has worked for you in the
> past?

My mistake, I think the server was just verifying my identity using GPG,
and what I entered was actually my "_GPG Password_."


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/support/?109210>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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