#5752 Unable to access proftp devel CVS repo

self-service
Chris Tsai
None
proftp
2013-11-05
2013-10-29
TJ Saunders
No

After yesterday's CVS maintenance, I am unable to access (checkout or commit) the proftp devel CVS repository. It is as if the devel CVS server cannot find my username/account,

I was planning on doing a proftpd release sometime this week, but am now unable to do so due to the lack of developer access to my project's CVS repos.

What went wrong to cause this?

Discussion

  • TJ Saunders
    TJ Saunders
    2013-10-30

    Some additional information: attempting to access the developer CVS repo for 'proftp' using password authentication, not just publickey authentication, also fails for user 'castaglia' -- using the same password with which I successfully logged into the website, in order to update this ticket.

     
  • Chris Tsai
    Chris Tsai
    2013-10-30

    • status: unread --> pending
    • assigned_to: Chris Tsai
     
  • Chris Tsai
    Chris Tsai
    2013-10-30

    What's the exact error message you're seeing? Also, what happens if you try to ssh directly to the CVS host (preferably with verbose output)?

    eg.

    $ ssh -v castaglia@proftp.cvs.sourceforge.net
    

    Thanks,
    Chris Tsai, SourceForge.net Support

     
  • TJ Saunders
    TJ Saunders
    2013-10-30

    When attempting to commit to the repo, I don't get an error message, per se. Instead, I am prompted for the passphrase for my SSH key 3 times; using the tried-and-true passphrase fails. I am then prompted for my username/password -- and using my (recently changed) password (same one used to log into this website) fails. The SSH connection terms there with "Too many authentication failures".

    Specifically:

    $ cvs commit doc/contrib/mod_tls_shmcache.html
    Password:
    Password:
    Password:
    castaglia@proftp.cvs.sourceforge.net's password:
    Received disconnect from 216.34.181.112: 2: Too many authentication failures for castaglia
    cvs [commit aborted]: end of file from server (consult above messages if any)

    And the requested output:

    $ ssh -v castaglia@proftp.cvs.sourceforge.net
    OpenSSH_5.1p1 Debian-5ubuntu1, OpenSSL 0.9.8g 19 Oct 2007
    debug1: Reading configuration data /home/tj/.ssh/config
    debug1: Reading configuration data /etc/ssh/ssh_config
    debug1: Applying options for
    debug1: Connecting to proftp.cvs.sourceforge.net [216.34.181.112] port 22.
    debug1: Connection established.
    debug1: identity file /home/tj/.ssh/identity type 0
    debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-1024
    debug1: Checking blacklist file /etc/ssh/blacklist.RSA-1024
    debug1: identity file /home/tj/.ssh/id_rsa type 1
    debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-1024
    debug1: Checking blacklist file /etc/ssh/blacklist.RSA-1024
    debug1: identity file /home/tj/.ssh/id_dsa type 2
    debug1: Checking blacklist file /usr/share/ssh/blacklist.DSA-1024
    debug1: Checking blacklist file /etc/ssh/blacklist.DSA-1024
    debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3
    debug1: match: OpenSSH_5.3 pat OpenSSH

    debug1: Enabling compatibility mode for protocol 2.0
    debug1: Local version string SSH-2.0-OpenSSH_5.1p1 Debian-5ubuntu1
    debug1: SSH2_MSG_KEXINIT sent
    debug1: SSH2_MSG_KEXINIT received
    debug1: kex: server->client aes128-cbc hmac-md5 none
    debug1: kex: client->server aes128-cbc hmac-md5 none
    debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
    debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
    debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
    debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
    debug1: Host 'proftp.cvs.sourceforge.net' is known and matches the RSA host key.
    debug1: Found key in /home/tj/.ssh/known_hosts:305
    debug1: ssh_rsa_verify: signature correct
    debug1: SSH2_MSG_NEWKEYS sent
    debug1: expecting SSH2_MSG_NEWKEYS
    debug1: SSH2_MSG_NEWKEYS received
    debug1: SSH2_MSG_SERVICE_REQUEST sent
    debug1: SSH2_MSG_SERVICE_ACCEPT received
    debug1: Authentications that can continue: publickey,password,keyboard-interactive
    debug1: Next authentication method: publickey
    debug1: Offering public key: /home/tj/.ssh/id_rsa
    debug1: Authentications that can continue: publickey,password,keyboard-interactive
    debug1: Offering public key: /home/tj/.ssh/id_dsa
    debug1: Authentications that can continue: publickey,password,keyboard-interactive
    debug1: Next authentication method: keyboard-interactive
    Password:
    debug1: Authentications that can continue: publickey,password,keyboard-interactive
    Password:
    debug1: Authentications that can continue: publickey,password,keyboard-interactive
    Password:
    debug1: Authentications that can continue: publickey,password,keyboard-interactive
    debug1: Next authentication method: password
    castaglia@proftp.cvs.sourceforge.net's password:
    Received disconnect from 216.34.181.112: 2: Too many authentication failures for castaglia

     
  • Chris Tsai
    Chris Tsai
    2013-11-01

    Hmm, I wonder if there was a password sync issue related to the outage, please try resetting your password again to try to get it to re-sync.

    Also, I'm curious whether or not you can still log into other SSH based services, like the Shell service or SFTP

    Regards,
    Chris Tsai, SourceForge.net Support

     

    Related

    Documentation: File Management

  • TJ Saunders
    TJ Saunders
    2013-11-05

    I had to reset my password, after the outage, as I'd forgotten it -- the reset/new password is what I use to log into the website to file/update this ticket.

    I just tried to ssh into web.sourceforge.net -- it prompted me for password authentication (indicating that it does not know about my previous SSH key) -- and the password authentication (using the password used for this website) fails.

    I'll try manually re-pasting/adding my SSH public key, to see if that fixes things.

     
  • TJ Saunders
    TJ Saunders
    2013-11-05

    Looks like re-adding my SSH public key worked. According to my accounts page earlier, I had 0 SSH public key associated with my accounts, which was clearly wrong.

    I'd still really like to know how/why SF lost my SSH public key, which had been working without issue for years. The only issue between the working and non-working access was the developer CVS maint window -- the fact that this would somehow lead to my SSH public key being lost is more than a little disheartening and frightening.

     
  • Chris Tsai
    Chris Tsai
    2013-11-05

    • status: pending --> self-service
     
  • Chris Tsai
    Chris Tsai
    2013-11-05

    I'm not sure that those are necessarily linked (ie., while there may be correlation, there isn't necessarily a causative relationship). But in any case, I'm glad to hear this is working for you now.

    Regards,
    Chris Tsai, SourceForge.net Support

     
  • TJ Saunders
    TJ Saunders
    2013-11-05

    Even if the two events are not related (which is likely), I'd still like to know how SF lost my SSH public key. If it happened once, it'll happen again unless the root cause is understood.