[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 anonymous):

 Not sure what would be causing the problem, then. Here's how I narrowed it
 down:

 1. Generate new keypair with ''ssh-keygen -t rsa'' and saved it as
 ~/.ssh/id_rsa[.pub]
 2. scp id_rsa.pub remote_host:/.ssh/authorized_keys
 3. (In Cyberduck) Changed bookmark to use public key authorization and
 selected id_rsa as private key.
 4. Connected to remote_host successfully, browsed, then disconnected.
 5. cat id_rsa did '''not''' show Proc-Type and DEK-Info.
 6. Open SSH Agent and activate id_rsa key.
 7. cat id_rsa '''did''' show Proc-Type and DEK-Info encapsulated headers.
 8. Attempted step 4 again, connecting to remote_host via Cyberduck;
 received the same "internal IO problem" message.
 8a. This problem occurs whether SSH Agent is running or not.

 Repeating the process above, but setting mode to a-w before activating the
 public key in SSH Agent will allow Cyberduck and SSH Agent to play nicely
 together. It's quite possible (probable, perhaps) that the problem
 actually lies with SSH Agent, but since it does handle forwarding
 correctly for other apps (including command-line ssh), who knows?

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