in reply to Re^2: Usage of key authentication with Net::SSH::Any
in thread Usage of key authentication with Net::SSH::Any

(I'm the author of the previous message. Didn't see I wasn't logged yet)
  • Comment on Re^3: Usage of key authentication with Net::SSH::Any

Replies are listed 'Best First'.
Re^4: Usage of key authentication with Net::SSH::Any
by salva (Canon) on Dec 11, 2013 at 14:07 UTC
Re^4: Usage of key authentication with Net::SSH::Any
by grom (Initiate) on Dec 12, 2013 at 08:51 UTC
    Salva, that's what I used at "second" try. First used putty key format then converted them into OpenSSH format (see initial post)

    I can't respond to your answer, idk why
      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.

        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
        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?