savannah-hackers
[Top][All Lists]
Advanced

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

[Savannah-hackers] Unable to access CVS for GOMP


From: Scott Robert Ladd
Subject: [Savannah-hackers] Unable to access CVS for GOMP
Date: Fri, 23 May 2003 09:14:03 -0400
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030430 Debian/1.3-5

I've been having terrible troubles trying to access the gomp CVS repository on Savannah.


Here's the result I get when trying to checkout the project:

  $ cvs -z3 -d address@hidden:/cvsroot/gomp co libgomp
  address@hidden's password:

No password works. I've successfully used remote CVS before, although not in the context of GNU. I've searched the web high and low, seeking any answer to this vexing problem.

In response to common questions:

Yes, I've registered my public key with savannah via the web interface. I've double-checked the registered key against the one on my machine, and they are identical.

Yes, I have tried connecting with and without my router in the middle.

My ~/.ssh/config file is set per instructions, as in:

    # also tried: Host savannah.gnu.org
    Host *gnu.org
        Protocol 1

My /etc/ssh/ssh_config is nothing but comments:

#       $OpenBSD: ssh_config,v 1.16 2002/07/03 14:21:05 markus Exp $
# This is the ssh client system-wide configuration file.  See
# ssh_config(5) for more information.  This file provides defaults for
# users, and the values can be changed in per-user configuration files
# or on the command line.
# Configuration data is parsed as follows:
#  1. command line options
#  2. user-specific file
#  3. system-wide file
# Any configuration value is only changed the first time it is set.
# Thus, host-specific definitions should be at the beginning of the
# configuration file, and defaults at the end.
# Site-wide defaults for various options
# Host *
#   ForwardAgent no
#   ForwardX11 no
#   RhostsAuthentication no
#   RhostsRSAAuthentication no
#   RSAAuthentication yes
#   PasswordAuthentication yes
#   HostbasedAuthentication no
#   BatchMode no
#   CheckHostIP yes
#   StrictHostKeyChecking ask
#   IdentityFile ~/.ssh/identity
#   IdentityFile ~/.ssh/id_rsa
#   IdentityFile ~/.ssh/id_dsa
#   Port 22
#   Protocol 2,1
#   Cipher 3des
# Ciphers aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc
#   EscapeChar ~

Now, if I try something I found via Google:

  address@hidden:~/projects/gnu$ ssh -v -1 sv.gnu.org
OpenSSH_3.6.1p2 Debian 1:3.6.1p2-1, SSH protocols 1.5/2.0, OpenSSL 0x0090702f
  debug1: Reading configuration data /home/scott/.ssh/config
  debug1: Applying options for *
  debug1: Applying options for *gnu.org
  debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Rhosts Authentication disabled, originating port will not be trusted.
  debug1: Connecting to sv.gnu.org [199.232.41.3] port 22.
  debug1: Connection established.
  debug1: identity file /home/scott/.ssh/identity type 0
debug1: Remote protocol version 1.99, remote software version OpenSSH_3.4p1 Debian 1:3.4p1-0.0woody1
  debug1: match: OpenSSH_3.4p1 Debian 1:3.4p1-0.0woody1 pat OpenSSH*
  debug1: Local version string SSH-1.5-OpenSSH_3.6.1p2 Debian   1:3.6.1p2-1
  debug1: Waiting for server public key.
  debug1: Received server public key (768 bits) and host key (1024   bits).
  debug1: Host 'sv.gnu.org' is known and matches the RSA1 host key.
  debug1: Found key in /home/scott/.ssh/known_hosts:7
  debug1: Encryption type: 3des
  debug1: Sent encrypted session key.
  debug1: Installing crc compensation attack detector.
  debug1: Received encrypted confirmation.
  debug1: RSA authentication using agent refused.
  debug1: Trying RSA authentication with key '/home/scott/.ssh/identity'
  debug1: Server refused our key.
  debug1: Doing challenge response authentication.
  debug1: No challenge.
  debug1: Doing password authentication.
  address@hidden's password:

I believe this indicates where the problem lies; the server is refusing my key, so it regresses to password authentication. I do not have a shell login, so I can't verify that my ~/.ssh/authorized_keys file is set correctly at Savannah.

Frankly, I'm at a loss. I can retrieve files via anonymous access, but (as yet) have no way of write-accessing the repository.

Any ideas would be appreciated.

..Scott

--
Scott Robert Ladd
Coyote Gulch Productions (http://www.coyotegulch.com)
Professional programming for science and engineering;
Interesting and unusual bits of very free code.





reply via email to

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