Re^4: Usage of key authentication with Net::SSH::Any

Replies are listed 'Best First'.
Re^5: Usage of key authentication with Net::SSH::Any by salva (Canon) on Dec 12, 2013 at 09:13 UTC
What I mean is that instead of bitvise, you use PuTTY key generator to convert the key from putty format to openssh one. IIRC, bitvise also uses its own key format that may be supported by OpenSSH but not by libssh2.	[reply]
Re^6: Usage of key authentication with Net::SSH::Any by grom (Initiate) on Dec 12, 2013 at 09:49 UTC
Yes, that's what I did. Here is the order of what I did: 1) Generate keys using PuttyKeygen 2) Putty worked, Perl failed 3) Converting keys in OpenSSH format using PuttyKeygen 4) Putty worked, Perl failed 5) Generate keys using Bitvise (choosing OpenSSH format) 5) Bitvise worked, Perl failed	[reply]
Re^7: Usage of key authentication with Net::SSH::Any by salva (Canon) on Dec 12, 2013 at 13:13 UTC
Try enabling Net::SSH::Any debugging. `$Net::SSH::Any::debug = -1;` [download] Also, try using Net::SSH2 directly in order to discard the case where it is a bug on Net::SSH::Any.	[reply] [d/l]
Re^6: Usage of key authentication with Net::SSH::Any by grom (Initiate) on Dec 12, 2013 at 10:39 UTC
Just an idea coming in my mind. When I connect with Putty (or bitvise), it asks to add the server fingerprint in the cache/registry. I chose "yes and save" in bitvise but Putty asked that too. So I guess this "cache"/"registry" may not be shared between different applications. Could it be related to my issue?	[reply]
Re^7: Usage of key authentication with Net::SSH::Any by salva (Canon) on Dec 12, 2013 at 12:04 UTC
No, unless you are using the development (git) versions of Net::SSH::Any, Net::SSH2 and libssh2. The stable version of Net::SSH2 does not validate the host key, which BTW is probably and unacceptable security issue.	[reply]