Status of pam-1@ssh.com authentication in OpenSSH?

From: Eduardo Duenez (e_duenez_at_hotmail.com)
Date: 12/21/03

  • Next message: Neil W Rickert: "Re: Status of pam-1@ssh.com authentication in OpenSSH?"
    Date: Sun, 21 Dec 2003 11:23:06 -0500
    
    

    Hi.

    Like many others, I have run into the problem that OpenSSH doesn't seem
    to implement the pam-1@ssh.com authentication method. I did some
    Googling and found older messages from other users with the exact same
    problem as me. Succintly:

    *My (technology illiterate) employer implements a Pine mail service
    through SSH allowing *only* pam-1@ssh.com as the authentication method.

    *I use OpenSSH (3.7.1p2) under Linux and get a refused connection (no
    password prompt at all).

    Any good news? (Verbose output follows.)

    Thanks,
    Eduardo

    ~> ssh -v eduenez1@pine.jhu.edu
    OpenSSH_3.7.1p2, SSH protocols 1.5/2.0, OpenSSL 0.9.7b 10 Apr 2003
    debug1: Reading configuration data /etc/ssh/ssh_config
    debug1: Applying options for *
    debug1: Connecting to pine.jhu.edu [128.220.2.18] port 22.
    debug1: Connection established.
    debug1: read PEM private key done: type DSA
    debug1: read PEM private key done: type RSA
    debug1: identity file /home/eduardo/.ssh/identity type -1
    debug1: identity file /home/eduardo/.ssh/id_rsa type -1
    debug1: identity file /home/eduardo/.ssh/id_dsa type -1
    debug1: Remote protocol version 2.0, remote software version 3.1.0 SSH
    Secure Shell (non-commercial)
    debug1: no match: 3.1.0 SSH Secure Shell (non-commercial)
    debug1: Enabling compatibility mode for protocol 2.0
    debug1: Local version string SSH-2.0-OpenSSH_3.7.1p2
    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: sending SSH2_MSG_KEXDH_INIT
    debug1: expecting SSH2_MSG_KEXDH_REPLY
    debug1: Host 'pine.jhu.edu' is known and matches the DSA host key.
    debug1: Found key in /home/eduardo/.ssh/known_hosts:2
    debug1: ssh_dss_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: pam-1@ssh.com
    debug1: No more authentication methods to try.
    Permission denied (pam-1@ssh.com).
    debug1: Calling cleanup 0x80645d0(0x0)


  • Next message: Neil W Rickert: "Re: Status of pam-1@ssh.com authentication in OpenSSH?"

    Relevant Pages

    • Re: queer dns access problem
      ... I was not quite right when I said that ssh works. ... debug1: Next authentication method: publickey ... not recording any traffic coming from the broken server when it tries to ...
      (RedHat)
    • cannot connect
      ... openssh 3.5p1-2. ... Now I cannot connect anymore to a host I used to connect ... OpenSSH_3.5p1, SSH protocols 1.5/2.0, OpenSSL 0x0090607f ... debug1: Rhosts Authentication disabled, ...
      (SSH)
    • Re: ssh gives "Permission denied, please try again"
      ... That just shows the server starting up, when you logged in via ssh to ... would have included the reason why it refused your login. ... debug1: Next authentication method: publickey ... debug1: Authentications that can continue: publickey,password ...
      (uk.comp.os.linux)
    • Re: ssh gives "Permission denied, please try again"
      ... That just shows the server starting up, when you logged in via ssh to ... would have included the reason why it refused your login. ... debug1: Next authentication method: publickey ... debug1: Authentications that can continue: publickey,password ...
      (uk.comp.os.linux)
    • error:key_read, hostname failed
      ... and I have openssh 3.4.1 on the server. ... Can you think of any reason why ssh would work and sftp/scp wouldn't? ... debug1: Rhosts Authentication disabled, ... Host ''hostname' is known and matches the RSA1 host key. ...
      (comp.security.ssh)