Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

Ssh.com openssh compatibility problem

Subject: Ssh.com openssh compatibility problem
Date: Wed, 29 Jun 2005 12:05:49 -0400
We are currently running the ssh.com v 3.2 client on several of our systems.
We have no problem connecting to servers running openssh v3.5 or 3.7.
However we are not able to connect to a server running openssh 3.9.  I have
looked in the FAQ and in the mailing list archives since the release of 3.9
but have not seen anything about this.  Here is the output from using ssh
-v:

eos.nih.gov> ssh2 -V 
ssh2: SSH Secure Shell Tru64 UNIX 3.2.0 
eos.nih.gov> ssh2 -v afps@tla01.ufms.hhs.gov 
debug: SshAppCommon/sshappcommon.c:185: Allocating global SshRegex context. 
debug: SshConfig/sshconfig.c:2820: Metaconfig parsing stopped at line 3. 
debug: SshConfig/sshconfig.c:2728: Unable to open
/usr/users/kl2/.ssh2/ssh2_config 
debug: Connecting to tla01.ufms.hhs.gov, port 22... (SOCKS not used) 
debug: Ssh2/ssh2.c:2332: Entering event loop. 
debug: Ssh2Client/sshclient.c:1452: Creating transport protocol. 
debug: SshAuthMethodClient/sshauthmethodc.c:95: Added
"kerberos-tgt-2@ssh.com" to usable methods. 
debug: SshAuthMethodClient/sshauthmethodc.c:95: Added "kerberos-2@ssh.com"
to usable methods. 
debug: SshAuthMethodClient/sshauthmethodc.c:95: Added "publickey" to usable
methods. 
debug: SshAuthMethodClient/sshauthmethodc.c:95: Added "keyboard-interactive"
to usable methods. 
debug: SshAuthMethodClient/sshauthmethodc.c:95: Added "password" to usable
methods. 
debug: Ssh2Client/sshclient.c:1493: Creating userauth protocol. 
debug: client supports 5 auth methods:
'kerberos-tgt-2@ssh.com,kerberos-2@ssh.com,publickey,keyboard-interactive,pa
ssword' 
debug: SshUnixTcp/sshunixtcp.c:1227: using local hostname eos.nih.gov 
debug: Ssh2Common/sshcommon.c:541: local ip = 128.231.56.102, local port =
2764 
debug: Ssh2Common/sshcommon.c:543: remote ip = 158.72.182.201, remote port =
22 
debug: SshConnection/sshconn.c:1957: Wrapping... 
debug: SshReadLine/sshreadline.c:3388: Initializing ReadLine... 
debug: Remote version: SSH-2.0-OpenSSH_3.9p1+sftplogging-v1.2 
debug: OpenSSH: Major: 3 Minor: 9 Revision: 0 
debug: Ssh2Transport/trcommon.c:1530: All versions of OpenSSH handle kex
guesses incorrectly. 
debug: Ssh2Transport/trcommon.c:1154: Already disconnected. 
debug: Ssh2Common/sshcommon.c:180: DISCONNECT received: Connection closed. 
debug: SshReadLine/sshreadline.c:3454: Uninitializing ReadLine... 
warning: Authentication failed. 
debug: Ssh2/ssh2.c:184: locally_generated = TRUE 
Disconnected; connection lost (Connection closed.). 
debug: Ssh2Client/sshclient.c:1528: Destroying client. 
debug: SshConfig/sshconfig.c:2330: Freeing pki. (host_pki != NULL, user_pki
= NULL) 
debug: SshConnection/sshconn.c:2009: Destroying SshConn object. 
debug: Ssh2Client/sshclient.c:1596: Destroying client completed. 
debug: SshAuthMethodClient/sshauthmethodc.c:100: Destroying authentication
method array. 
debug: SshAppCommon/sshappcommon.c:198: Freeing global SshRegex context. 
debug: SshConfig/sshconfig.c:2330: Freeing pki. (host_pki = NULL, user_pki =
NULL) 

Note the line:

debug: Ssh2Transport/trcommon.c:1530: All versions of OpenSSH handle kex
guesses incorrectly.  

The connection closes without even prompting for a password.   Did something
change in openssh between 3.7 and 3.9 that might be the cause of this
problem.  Is there anything that can be done about it (do we need to upgrade
the version of ssh.com we are running?)?

Thanks for any help you can provide.

Robert P. Klein

<Prev in Thread] Current Thread [Next in Thread>