Hmm. I don't know the details of SSH, but based on the text of the message and knowledge of PKI I can take a wild guess. Perhaps the Windows box does not trust the root cert that signed the public key, while the Linux box does trust the cert that signed the public key? That's what it sounds like to me... How else would you "verify" a public key other than checking the signature on that against trusted root certs?
HTH,
Fred Reimer, CCIE 23812 CISSP 107125
mailto:freimer_at_freimer.org
On May 11, 2010, at 5:52 AM, Bart Simpson wrote:
>> Just out of interest, is there any reason you pass things around as a QString?
> Yes there is, the class SshConnect is only a little part of a bigger Qt gui software.
> And somewhere i have to convert QString-->char or char-->QString so i decide to do it here.
>
>
>> -19 is LIBSSH2_ERROR_PUBLICKEY_UNVERIFIED and the error text should be
>> "Invalid signature for supplied public key, or bad username/public key
>> combination" not "Callback returned error" (I have no idea where this
>> second string came from).
> That is a good point, i think in my function "lastError()" is some mistake. But when i take
> the return value of "libssh2_userauth_publickey_fromfile" it is:
>
> -19 --> LIBSSH2_ERROR_PUBLICKEY_INVERIFIED
>
> But i do not understand the difference between linux and windows.
> I have exactly the same code and the same keyfile in both versions.
>
>
>
> Regards,
> Thomas
> _______________________________________________
> libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
>
_______________________________________________
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel