Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 6 Jan 2002 17:23:04 -0700
From:      dgkerr@juno.com
To:        freebsd-questions@FreeBSD.ORG
Subject:   Fw: Re: FreeBSD Ver 4.4 and open SSH
Message-ID:  <20020106.172304.1444.1.dgkerr@juno.com>

next in thread | raw e-mail | index | archive | help
Hi Chris,

Yes I do have OpenSSh-2.3.0 FreeBSD localsations 20010713.

I have tried using Putty and Secure Shell SSH with the same results.  I
have the log from unsuccessful attempts.  I have generated keys in the
FreeBSD box and moved them to the windows box, and I have generated keys
with both Putty and Secure Shell SSH and moved them to the FreeBSD Box
with the same results.  This is an unsuccessful attempt from Secure
Shell, but it is nearly identical to the output from Putty.

I am using Protocol 2

Jan 6 09:55:52 gk2 sshd[181]: Connection from 192.168.202.1 port 1051
Jan 6 09:55:52 gk2 sshd[181]: Connection from 192.168.202.1 port 1051
Jan 6 09:55:52 gk2 sshd[181]: debug1: Client protocol version 1.99;
client software version 3.0.0 SSH Secure Shell for Windows
Jan 6 09:55:52 gk2 sshd[181]: debug1: no match: 3.0.0 SSH Secure Shell
for Windows
Jan 6 09:55:52 gk2 sshd[181]: Enabling compatibility mode for protocol
2.0
Jan 6 09:55:52 gk2 sshd[181]: debug1: Local version string
SSH-2.0-OpenSSH_2.3.0 FreeBSD localisations 20010713
Jan 6 09:55:52 gk2 sshd[181]: debug1: send KEXINIT
Jan 6 09:55:52 gk2 sshd[181]: debug1: done
Jan 6 09:55:52 gk2 sshd[181]: debug1: wait KEXINIT
Jan 6 09:55:52 gk2 sshd[181]: debug1: got kexinit:
diffie-hellman-group1-sha1
Jan 6 09:55:52 gk2 sshd[181]: debug1: got kexinit:
ssh-rsa,ssh-dss,x509v3-sign-dss,x509v3-sign-rsa
Jan 6 09:55:52 gk2 sshd[181]: debug1: got kexinit:
aes128-cbc,3des-cbc,blowfish-cbc,twofish-cbc,arcfour
Jan 6 09:55:52 gk2 sshd[181]: debug1: got kexinit:
aes128-cbc,3des-cbc,blowfish-cbc,twofish-cbc,arcfour
Jan 6 09:55:52 gk2 sshd[181]: debug1: got kexinit: hmac-md5,hmac-sha1
Jan 6 09:55:52 gk2 sshd[181]: debug1: got kexinit: hmac-md5,hmac-sha1
Jan 6 09:55:52 gk2 sshd[181]: debug1: got kexinit: none
Jan 6 09:55:52 gk2 sshd[181]: debug1: got kexinit: none
Jan 6 09:55:52 gk2 sshd[181]: debug1: got kexinit: 
Jan 6 09:55:52 gk2 sshd[181]: debug1: got kexinit: 
Jan 6 09:55:52 gk2 sshd[181]: debug1: first kex follow: 0 
Jan 6 09:55:52 gk2 sshd[181]: debug1: reserved: 0 
Jan 6 09:55:52 gk2 sshd[181]: debug1: done
Jan 6 09:55:52 gk2 sshd[181]: debug1: kex: client->server aes128-cbc
hmac-md5 none
Jan 6 09:55:52 gk2 sshd[181]: debug1: kex: server->client aes128-cbc
hmac-md5 none
Jan 6 09:55:52 gk2 sshd[181]: debug1: Wait SSH2_MSG_KEXDH_INIT.
Jan 6 09:55:52 gk2 sshd[181]: debug1: bits set: 496/1024
Jan 6 09:55:52 gk2 sshd[181]: debug1: bits set: 522/1024
Jan 6 09:55:52 gk2 sshd[181]: debug1: sig size 20 20
Jan 6 09:55:52 gk2 sshd[181]: debug1: send SSH2_MSG_NEWKEYS.
Jan 6 09:55:52 gk2 sshd[181]: debug1: done: send SSH2_MSG_NEWKEYS.
Jan 6 09:55:52 gk2 sshd[181]: debug1: Wait SSH2_MSG_NEWKEYS.
Jan 6 09:55:52 gk2 sshd[181]: debug1: GOT SSH2_MSG_NEWKEYS.
Jan 6 09:55:52 gk2 sshd[181]: debug1: done: KEX2.
Jan 6 09:55:57 gk2 sshd[181]: Could not reverse map address
192.168.202.1.
Jan 6 09:55:57 gk2 sshd[181]: debug1: userauth-request for user george
service ssh-connection method none
Jan 6 09:55:57 gk2 sshd[181]: debug1: attempt #1
Jan 6 09:55:57 gk2 sshd[181]: debug1: Starting up PAM with username
"george"
Jan 6 09:55:57 gk2 sshd[181]: Failed none for george from 192.168.202.1
port 1051 ssh2
Jan 6 09:55:57 gk2 sshd[181]: debug1: userauth-request for user george
service ssh-connection method publickey
Jan 6 09:55:57 gk2 sshd[181]: debug1: attempt #2
Jan 6 09:55:57 gk2 sshd[181]: bad pkalg ssh-rsa
Jan 6 09:55:57 gk2 sshd[181]: Failed publickey for george from
192.168.202.1 port 1051 ssh2
Jan 6 09:55:57 gk2 sshd[181]: debug1: userauth-request for user george
service ssh-connection method none
Jan 6 09:55:57 gk2 sshd[181]: debug1: attempt #3
Jan 6 09:55:57 gk2 sshd[181]: Failed none for george from 192.168.202.1
port 1051 ssh2
Jan 6 09:55:57 gk2 sshd[181]: Received disconnect: 14: No further
authentication methods available.
Jan 6 09:55:57 gk2 sshd[181]: debug1: Calling cleanup 0x8058bd8(0x0)
Jan 6 09:55:57 gk2 sshd[181]: debug1: Calling cleanup 0x805f3f8(0x0)

Thanks for your help.
George
On Sun, 06 Jan 2002 15:48:57 -0600 Christopher Schulte
<schulte+freebsd@nospam.schulte.org> writes:
> At 12:39 PM 1/6/2002 -0700, dgkerr@juno.com wrote:
> >I just installed FreeBSD 4.4 stable.  I have not been able to get 
> SSH to
> >allow a log in.  After much time I discovered that I still have
> >OpenSSH_2.3.0.  This is the same version I got with FreeBSD 4.3 
> Release.
> 
> No,
> 
> 4.3 came with OpenSSH_2.3.0 green@FreeBSD.org 20010321
> 
> 4.4 came with OpenSSH_2.3.0 FreeBSD localisations 20010713
> 
> Note the '20010321' versus '20010713'.  They are different versions 
> of 
> OpenSSH 2.3.0, each patched by the FreeBSD team when problems 
> arose.
> 
> >I thought that after the Security advisory, SSH had been upgraded 
> to a
> >newer version.
> 
> Which security advisory are you referring to?  Recent UseLogin 
> patch?
> 
> That has been fixed in -STABLE as of December 3, 2001:
> 
> OpenSSH_2.3.0 FreeBSD localisations 20011202
> 
> >Do I have to do something different to get an updated version of 
> OpenSSH
> >that will work with FreeBSD?
> 
> You probably already have the most recent FreeBSD shipped version of 
> OpenSSH.
> 
> Reply ( back to this list ) with more specific details of why you 
> are 
> unable to login via ssh.
> 
> >Thanks,
> >George
> 
> 
> --chris
> 
> 


George Kerr
Web-Pilot
www.milehirc.com
dgkerr@juno.com
web-pilot@attbi.com

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020106.172304.1444.1.dgkerr>