[Cyberduck-trac] [Cyberduck] #2664: Incompatibility with SSH-2.0-Sun_SSH_1.0.1
Cyberduck
trac at trac.cyberduck.ch
Mon May 18 03:44:00 CEST 2009
#2664: Incompatibility with SSH-2.0-Sun_SSH_1.0.1
----------------------------------------+-----------------------------------
Reporter: zoltan.sebestyen@… | Owner: dkocher
Type: defect | Status: new
Priority: normal | Milestone:
Component: sftp | Version: 3.0.2
Severity: normal | Keywords:
----------------------------------------+-----------------------------------
Comment(by damian.bickhoff@…):
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:
{{{
debug1: userauth-request for user damian service ssh-connection method
none
debug1: attempt 0 initial attempt 0 failures 0 initial failures 0
Failed none for damian from 132.234.28.201 port 53955 ssh2
Connection closed by 132.234.28.201
}}}
/usr/bin/ssh:
{{{
debug1: userauth-request for user damian service ssh-connection method
none
debug1: attempt 0 initial attempt 0 failures 0 initial failures 0
Failed none for damian from 132.234.28.201 port 53956 ssh2
debug1: userauth-request for user damian service ssh-connection method
publickey
debug1: attempt 1 initial attempt 0 failures 1 initial failures 0
}}}
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.
--
Ticket URL: <http://trac.cyberduck.ch/ticket/2664#comment:6>
Cyberduck <http://cyberduck.ch>
FTP, SFTP, WebDAV, Cloud Files and Amazon S3 Browser for Mac OS X.
More information about the Cyberduck-trac
mailing list