[Cyberduck-trac] [Cyberduck] #398: Cannot connect with SSH public key authentication ("Can't read key due to internal IO problems")

[Cyberduck]

#398: Cannot connect with SSH public key authentication ("Can't read key due to
internal IO problems")
--------------------------------+-------------------------------------------
 Reporter:  bshalsey at paxoo.com  |        Owner:  dkocher
     Type:  defect              |       Status:  new    
 Priority:  low                 |    Milestone:         
Component:  sftp                |      Version:  2.5.5  
 Severity:  minor               |   Resolution:         
 Keywords:                      |  
--------------------------------+-------------------------------------------
Comment (by bshalsey (at) paxoo):

 That exception does occur when an incorrect password is entered. However,
 my particular problem is a little more complicated.

 When I try to use my original key (I'll call it ''tonks-1'' from now on),
 it doesn't even ask for my password, even though I entered one when I
 generated the key.

 The problem ''might'' be the cause, as I speculated earlier, of SSH Agent
 instead. The original key I used, ''tonks-1'', which causes this problem
 was generated inside SSH Agent instead of using the CLI '''ssh-keygen'''
 utility, which also perhaps explains why the Proc-Type and DEK-Info
 headers show up inside the key.

 Since Cyberduck seems to work well with other keys and you have other more
 important defects and enhancements to work on (I'm really looking forward
 to that key forwarding enhancement in #75!), I'd say this is a very minor
 issue and would, in fact, be inclined to assign the problem to SSH Agent.

-- 
Ticket URL: <http://trac.cyberduck.ch/ticket/398>
Cyberduck <http://cyberduck.ch>
FTP and SFTP Browser for Mac OS X.