Re: SSH not passing my key!!

From: Bill Unruh (unruh_at_string.physics.ubc.ca)
Date: 02/27/05

  • Next message: Russ Allbery: "Re: Six Kerberos/OS X/SSH observations and questions" 
    Date: 27 Feb 2005 15:59:20 GMT

    "Affan" <affanahmed@gmail.com> writes:

    >Hello,
    >I had capability to ssh into the cs551 account of the machined
    >aludra.usc.edu (I am the TA!). I am not exactly sure what changed, but
    >I am no longer able to access the account, even thought the prof.
    >having access to tha account has verified that my public key is in the
    >authorized_keys of the account. So I tried the verbose output and it
    >seems that in the final lines of the verbose output by ssh below(before
    >it asks me for the cs551 accoutn pwd .. which i dont have) It *tries*
    >(no what does that mean) two keys that arent in my .ssh account at all.

    How does it know they aren't in your account at all without trying them?
    It is not compiled in. It goes through the possible keys in order until it
    finds one that you have and that works.

    >Then if offers the id_dsa key (I would have thought that it would offer
    >the id_dsa.pub key?) which i do have (and whose pub key is in the

    It is trying the id_dsa signature. It encrypts with your private key id_dsa
    and then the other side decrypts with your public key to see if it really
    is you.

    >aco***!!!) but it still seems to fail and ask for password!!! Any
    >suggestion/tips on what might be wrong?

    Wrong key has been put into authorized_keys. Are you sure yours works? put
    your own key into your own authorized hosts and try ssh to yourself.
    See if that works. If not, your file has become corrupted. Then give your
    prof your current id_dsa.pub key and have him reinstall it.

    Are othr people able to log on? If not it may be a configuration change on
    his end.

    >OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003
    >debug1: Reading configuration data /etc/ssh/ssh_config
    >debug1: Applying options for *
    >debug1: Connecting to aludra.usc.edu [128.125.19.184] port 22.
    >debug1: Connection established.
    >debug1: identity file /nfs/guest/asyed/.ssh/identity type -1
    >debug1: identity file /nfs/guest/asyed/.ssh/id_rsa type -1
    >debug1: identity file /nfs/guest/asyed/.ssh/id_dsa type 2
    >debug1: Remote protocol version 1.99, remote software version
    >OpenSSH_3.8p1
    >debug1: match: OpenSSH_3.8p1 pat OpenSSH*
    >debug1: Enabling compatibility mode for protocol 2.0
    >debug1: Local version string SSH-2.0-OpenSSH_3.9p1
    >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 'aludra.usc.edu' is known and matches the RSA host key.
    >debug1: Found key in /nfs/guest/asyed/.ssh/known_hosts:10
    >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,gssapi-with-mic,password
    >debug1: Next authentication method: publickey
    >debug1: Trying private key: /nfs/guest/asyed/.ssh/identity
    >debug1: Trying private key: /nfs/guest/asyed/.ssh/id_rsa
    >debug1: Offering public key: /nfs/guest/asyed/.ssh/id_dsa
    >debug1: Authentications that can continue:
    >publickey,gssapi-with-mic,password
    >debug1: Next authentication method: password
    >cs551@aludra.usc.edu's password:

    >Thanks
    >Affan

  • Next message: Russ Allbery: "Re: Six Kerberos/OS X/SSH observations and questions"