> On Wed, Sep 06, 2006 at 01:00:43PM -0400, Dennis Clarke wrote: > >> > which is the main reason the that from day one of its integration into >> > the Solaris 9 source base it identified itself as Sun_SSH. >> >> # cd /usr/share >> # find . -type f | xargs grep -i sun_ssh >> # > > [ other attempts to find sun_ssh snipped ] > > When Darren said "identified itself", he meant quite more actively than in > the filesystem: > > solaris% ssh -v localhost true |& grep -i sun > Sun_SSH_1.1, SSH protocols 1.5/2.0, OpenSSL 0x0090704f > debug1: Remote protocol version 2.0, remote software version Sun_SSH_1.1 > debug1: no match: Sun_SSH_1.1 > debug1: Local version string SSH-2.0-Sun_SSH_1.1 >
OKay .. I see that now : bash-3.1# /opt/csw/bin/ssh -2 -4 -e\^ -l dclarke -c aes256-cbc -v inotes OpenSSH_4.3p2, OpenSSL 0.9.8a 11 Oct 2005 debug1: Reading configuration data /opt/csw/etc/ssh_config debug1: Connecting to inotes [192.168.35.242] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/1 debug1: identity file /root/.ssh/id_rsa type -1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: Remote protocol version 2.0, remote software version Sun_SSH_1.1 debug1: no match: Sun_SSH_1.1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.3 debug1: Miscellaneous failure No credentials cache found debug1: Miscellaneous failure No credentials cache found debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received no matching cipher found: client aes256-cbc server aes128-ctr,aes128-cbc,arcfour,3des-cbc,blowfish-cbc bash-3.1# Now I need to go figure out what "debug1: Miscellaneous failure" means. Dennis _______________________________________________ opensolaris-discuss mailing list [email protected]
