New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatibility with SSH-2.0-Sun_SSH_1.0.1 #2664
Comments
Replying to [comment:1 dkocher]:
Hi,
|
I've just checked. The problem exists for 3.0.3 as well. |
I've just checked. The problem exists for 3.0.3 as well. |
Hi. I've looked at this server-side, and I can't see whether it's Sun's SSH (likely) that's forcing the none connection first, but here's the difference between Cyberduck and /usr/bin/ssh. I can paste in full, but akismet said I was spamming. Cyberduck:
/usr/bin/ssh:
That's the essence of it, anyway. Basically, the first auth always fails, as it's for a connection method that will never work. Like I said, this is probably a config issue Solaris-side, or some other magic, but it'd be nice if Cyberduck could kludge it. |
Err, apologies for multi-comment spam, but I have this issue with "SSH-2.0-Sun_SSH_1.1" as well as the version string quoted by reporter. |
Looks like you are logging in using public key authentication with |
It connects and immediately disconnects from such servers.
Sun has a modified version of some older OpenSSH release.
the Sun ssh version in question is: SSH-2.0-Sun_SSH_1.0.1
I did not find any hints how to collect some more info for you. Please advise.
The text was updated successfully, but these errors were encountered: