Learn how to a build a cloud-first strategyRegister Now


difference between ssh and openssh

Posted on 2007-07-24
Medium Priority
Last Modified: 2013-12-02
difference between ssh and openssh.  I have one EFT server that will accept SSH.
I have another EFT server that won't accept SSH, but will accept openSSH.
The servers are globascape but they are different versions.  The newer version will not accept SSH.
Thank you
Question by:rvaede
  • 2
LVL 13

Accepted Solution

dhoffman_98 earned 450 total points
ID: 19558637
I don't think it's a matter of SSH compared to openSSH. More likely the problem you are having is which version of SSH are being accepted. By that, I mean the version of the protocol. If you are using version 1 of the protocol on one machine, and running SSH tries to only connect on version 2, then you won't be able to connect. On the other hand perhaps openSSH automatically tries version 2, and then falls back to version 1 if version 2 fails.

You'll need to check the servers for what versions of the protocol they will accept.
LVL 48

Assisted Solution

Tintin earned 300 total points
ID: 19559523
Show us the output of

ssh - v eftserver1

ssh -v eftserver2

Using the SSH client.  It's probably more due to ssh server configuration, particularly around permissions.

Author Comment

ID: 19560687

I only have this one for now:

Connecting to xxxx.com...
Sun_SSH_1.1, SSH protocols 1.5/2.0, OpenSSL 0x0090704f
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Rhosts Authentication disabled, originating port will not be trusted.
debug1: ssh_connect: needpriv 0
debug1: Connecting to xxxx.com [xxx.xxx.161.220] port 22.
debug1: Connection established.
debug1: identity file /home/xxxxxx/.ssh/id_rsa type -1
debug1: identity file /home/xxxx/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version 1.36 sshlib: GlobalScape
debug1: no match: 1.36 sshlib: GlobalScape
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-Sun_SSH_1.1
debug1: Failed to acquire GSS-API credentials for any mechanisms (No credentials were supplied, or the credentials were unavailable or inaccessible
Unknown code 0
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: Peer sent proposed langtags, ctos:
debug1: Peer sent proposed langtags, stoc:
debug1: We proposed langtags, ctos: i-default
debug1: We proposed langtags, stoc: i-default
debug1: dh_gen_key: priv key bits set: 135/256
debug1: bits set: 512/1024
debug1: sending SSH2_MSG_KEXDH_INIT
debug1: expecting SSH2_MSG_KEXDH_REPLY
debug1: Host 'vault.advisory.com' is known and matches the DSA host key.
debug1: Found key in /home/xxxxx/.ssh/known_hosts:3
debug1: bits set: 507/1024
debug1: ssh_dss_verify: signature correct
debug1: newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: done: ssh_kex2.
Welcome to Advisory Board Compass Solution Services
This is a private network, which may be accessed and used only
for official The Advisory Board Company and their members only.
Unauthorized access or use of this computer system
may subject violators to criminal, civil, and/or administrative
action. Any information on this computer system may be intercepted,
recorded, read, copied, and disclosed by and to authorized personnel
for official purposes, including criminal investigations.
Access or use of this computer system by any person whether
authorized or unauthorized, constitutes consent to these terms.
debug1: Authentications that can continue: password,publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /home/xxxxxx/.ssh/id_rsa
debug1: Trying private key: /home/xxxxxx/.ssh/id_dsa
debug1: Next authentication method: password
5025moffitt@vault.advisory.com's password:
debug1: Authentication succeeded (password)
debug1: fd 5 setting O_NONBLOCK
debug1: channel 0: new [client-session]
debug1: send channel open 0
debug1: Entering interactive session.
debug1: ssh_session2_setup: id 0
debug1: Sending subsystem: sftp
debug1: channel request 0: subsystem
debug1: channel 0: open confirm rwindow 16384 rmax 16384


LVL 48

Expert Comment

ID: 19560786
Really need to see the debug output from when your login fails with the SSH client.

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Have you ever stumbled upon a software that is so great that you just love? It happened to me. Love at first sight. Filezilla Server.   Ok its not the most advanced ftp server I've came across. But its a fairly simple piece of software to get the …
Hello to you all, I hear of many people congratulate AWS (Amazon Web Services) on how easy it is to spin up and create new EC2 (Elastic Compute Cloud) instances, but then fail and struggle to connect to them using simple tools such as SSH (Secure…
Michael from AdRem Software outlines event notifications and Automatic Corrective Actions in network monitoring. Automatic Corrective Actions are scripts, which can automatically run upon discovery of a certain undesirable condition in your network.…
In this video, Percona Solutions Engineer Barrett Chambers discusses some of the basic syntax differences between MySQL and MongoDB. To learn more check out our webinar on MongoDB administration for MySQL DBA: https://www.percona.com/resources/we…
Suggested Courses
Course of the Month21 days, 2 hours left to enroll

810 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question