On Mon, Jul 9, 2012 at 10:34 AM, Magnus Hagander <mag...@hagander.net> wrote: > On Mon, Jul 9, 2012 at 11:15 AM, Dave Page <dp...@pgadmin.org> wrote: >> On Mon, Jul 9, 2012 at 10:10 AM, Akshay Joshi >> <akshay.jo...@enterprisedb.com> wrote: >>> >>> We are using following API for successful authentication using public key >>> >>> libssh2_userauth_publickey_fromfile(LIBSSH2_SESSION *session, const >>> char *username, const char *publickey, const char *privatekey, >>> const char *passphrase); >>> >>> So in this case we will require both public and private key. We can do >>> one thing here is only get the private key from user and assume public key >>> file (.pub) is at the same folder location. Thoughts? Comments? >> >> No, that won't work - it'll break as soon as I test it for example. >> >> You can just set that param to null. The man page says: >> >> publickey - Path name of the public key file. (e.g. >> /etc/ssh/hostkey.pub). If libssh2 is built against OpenSSL, this >> option can be set to NULL. > > What if it's not built against OpenSSL, though? For example, the one > on Ubuntu appears to be built against GnuTLS...
We've never supported anything other than OpenSSL. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers
