Openssh 3.1 and Openssh 3.4 authentication

From: F. Romero (fromero@csudh.edu)
Date: 12/22/02 

Date: Sat, 21 Dec 2002 21:51:01 -0800
To: secureshell@securityfocus.com
From: "F. Romero" <fromero@csudh.edu>

I have MacOSX box with openssh 3.4 trying to connect with automatic
authentication to a Linux box with openssh 3.1. I have made the key
and put it to its correct location, when I set the verbose option, I
get:

OpenSSH_3.4p1, SSH protocols 1.5/2.0, OpenSSL 0x0090605f
debug1: Reading configuration data /etc/ssh_config
debug1: Rhosts Authentication disabled, originating port will not be trusted.
debug1: ssh_connect: needpriv 0
debug1: Connecting to tardis.csudh.edu [155.135.21.52] port 22.
debug1: Connection established.
debug1: identity file /Users/paco/.ssh/identity type -1
debug1: identity file /Users/paco/.ssh/id_rsa type -1
debug1: identity file /Users/paco/.ssh/id_dsa type 2
debug1: Remote protocol version 1.99, remote software version OpenSSH_3.1p1
debug1: match: OpenSSH_3.1p1 pat OpenSSH_2.*,OpenSSH_3.0*,OpenSSH_3.1*
Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.4p1
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 sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: dh_gen_key: priv key bits set: 145/256
debug1: bits set: 1603/3191
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'tardis.csudh.edu' is known and matches the RSA host key.
debug1: Found key in /Users/paco/.ssh/known_hosts:2
debug1: bits set: 1561/3191
debug1: ssh_rsa_verify: signature correct
debug1: kex_derive_keys
debug1: newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: waiting for SSH2_MSG_NEWKEYS
debug1: newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: done: ssh_kex2.
debug1: send SSH2_MSG_SERVICE_REQUEST
debug1: service_accept: ssh-userauth
debug1: got SSH2_MSG_SERVICE_ACCEPT
debug1: authentications that can continue:
publickey,password,keyboard-interactive
debug1: next auth method to try is publickey
debug1: try privkey: /Users/paco/.ssh/identity
debug1: try privkey: /Users/paco/.ssh/id_rsa
debug1: try pubkey: /Users/paco/.ssh/id_dsa
debug1: authentications that can continue:
publickey,password,keyboard-interactive
debug1: next auth method to try is keyboard-interactive
debug1: authentications that can continue:
publickey,password,keyboard-interactive
debug1: next auth method to try is password 

-- 
fromero@csudh.edu
Computer Technical Support, Math/Science Coordinator
http://www.csudh.edu/class/

Relevant Pages

  • Re: IBM openssh seems to hang
    ... openssh, and it went away when I upgraded the machines that were back-level. ... > Could it be that we're using two different ssh packages on the two boxes? ... > debug1: Rhosts Authentication disabled, originating port will not be trusted. ... next auth method to try is publickey ...
    (comp.unix.aix)
  • help with ssh
    ... debug1: Authentications that can continue: publickey,gssapi-with-mic,password ... debug2: we sent a gssapi-with-mic packet, ...
    (RedHat)
  • OpenSSH on Solaris 9: Puzzling problems
    ... I have an odd problem with OpenSSH 3.6.1p1 on Solaris 9. ... debug1: read PEM private key done: type RSA ... debug1: private host key: #1 type 1 RSA ... debug1: Authentications that can continue: publickey,password ...
    (SSH)
  • Re: SFTP/SCP connection prob
    ... debug1: Authentications that can continue: publickey,password,keyboard- ... debug2: we sent a publickey packet, ... which only supports SFTP/SCP protocal from server C ...
    (comp.security.unix)
  • No password prompt with openssh
    ... This distribution is mainly based on Debian woody binaries. ... debug1: send SSH2_MSG_SERVICE_REQUEST ... debug1: authentications that can continue: ... next auth method to try is keyboard-interactive ...
    (comp.security.ssh)