On Tue, Jul 10, 2012 at 4:22 PM, Dave Page
<dpage@pgadmin.org> wrote:
On Tue, Jul 10, 2012 at 11:39 AM, Magnus Hagander <
magnus@hagander.net> wrote:
> Can we identify which version of libssh is required, and have a
> configure check for it? AFAICT they are all on 1.2 until the *next*
> release - so is it really something that breaks on just a minor
> version? If so, we really need a configure check for it.
>
> I think it's ok to say that we can't build with that feature on 10.04
> (assuming we can find a configure test for it). less sure about
> something that's less than a year old such as 11.10.
mailing lists to see if there's another API that you've missed, or if
they can explain why it's necessary to provide the public key and
private one.
I have posted the problem on libssh2 mailing list and below is the response that I received from Daniel Stenberg
"Any other SSL library" would be another crypto library to be strict, as we don't use SSL... That only other crypto library
we support in libssh2 is gcrypt. It just happens that nobody has written the necessary code in libssh2 to allow this
operation with that backend. Feel free to step forward and help us remove this annoying difference in functionality
depending on backend crypto lib!
So... something to think about in parallel with that; if we cannot
deal with this cleanly using libssh2, should we go back to the
original plan that Akshay and I discussed privately, which was to have
pgAdmin spawn ssh (or putty on Windows) processes to provide the
tunnels?
--
Akshay Joshi
Senior Software Engineer
EnterpriseDB Corporation
The Enterprise PostgreSQL Company
Phone: +91 20-3058-9522
Mobile: +91 976-788-8246