You could maybe start here:

http://github.com/jamis/net-ssh/tree/master/lib/net/ssh/ key_factory.rb

And search the code for places KeyFactory is used, to determine when/ where public keys are being used where private keys would do.

- Jamis

On Apr 14, 2008, at 8:02 AM, Paul Dowman wrote:

I'd be willing to take a crack at it if you can point me in the right
direction and if it's not fixed in v2.

Paul

On Sat, Apr 12, 2008 at 10:39 AM, Jamis Buck <[EMAIL PROTECTED]> wrote:
It's a quirk of Net::SSH that has never been patched. If anyone wants to take a look and fix it, that'd be great. The problem might already be fixed in Net::SSH v2 (due to be released in the near future), but I haven't had a
chance to verify.

- Jamis



On Apr 12, 2008, at 8:07 AM, Paul Dowman wrote:





Hi, there's something that's been confusing me for a long time. When
connecting using public/private key authentication the client
shouldn't need to have the public key available, but for some reason
Capistrano (Net:SSH?) seems to require it.

The openssh client can connect without having the public key file
available, e.g. "ssh -i privkeyfile hostname" (where privkeyfile is a
private key). But Capistrano complains if there isn't also a file
named "privkeyfile.pub" (containing the public key) in the same
directory.

Am I doing something wrong? Is there a way to change this so that the
public key isn't required?

Thanks,
Paul








--
http://pauldowman.com

--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---


Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to