Re: SSH Tunneling implementation

On Thu, Jul 12, 2012 at 5:21 PM, Dave Page <dpage(at)pgadmin(dot)org> wrote:

> On Thu, Jul 12, 2012 at 12:04 PM, Akshay Joshi
> <akshay(dot)joshi(at)enterprisedb(dot)com> wrote:
> > Hi All
> >
> > I have tried a lot to figure out libssh2 is compiled with which crypto
> > library, but unable to find it. Can someone guide/help me or do we
> continue
> > with the public key option on UI?
>
> The libssh2 guys couldn't tell you how?
>

I'll post this on mailing list, but I have found one solution to the
problem is checking the function "*libssh2_md5*" using AC_CHECK_LIB as
below
AC_CHECK_LIB(ssh2, libssh2_md5, [IS_LIBSSH2_OPENSSL_CRYPTO=yes],
[IS_LIBSSH2_OPENSSL_CRYPTO=no])

I have analyze libssh2 source code and found "libssh2_md5" is
implemented only for openssl version not for the gcrypt. I have tested it
with both
the version of libssh2.so.

Thoughts? Comments?

>
> > I'll continue to find some solution.
> >
> >
> > On Tue, Jul 10, 2012 at 6:06 PM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> >>
> >> On Tue, Jul 10, 2012 at 1:32 PM, Akshay Joshi
> >> <akshay(dot)joshi(at)enterprisedb(dot)com> wrote:
> >> >
> >> >
> >> > On Tue, Jul 10, 2012 at 4:22 PM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> >> >>
> >> >> On Tue, Jul 10, 2012 at 11:39 AM, Magnus Hagander <
> magnus(at)hagander(dot)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.
> >> >>
> >> >> Yeah, that seems reasonable. I'd also suggest pinging the libssh2
> >> >> 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!
> >>
> >> OK, so can you please try to find out what Ubuntu/Debian and Redhat do
> >> please?
> >>
> >> --
> >> Dave Page
> >> Blog: http://pgsnake.blogspot.com
> >> Twitter: @pgsnake
> >>
> >> EnterpriseDB UK: http://www.enterprisedb.com
> >> The Enterprise PostgreSQL Company
> >
> >
> >
> >
> > --
> > Akshay Joshi
> > Senior Software Engineer
> > EnterpriseDB Corporation
> > The Enterprise PostgreSQL Company
> > Phone: +91 20-3058-9522
> > Mobile: +91 976-788-8246
> >
>
>
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>

--
*Akshay Joshi
Senior Software Engineer
EnterpriseDB Corporation
The Enterprise PostgreSQL Company
Phone: +91 20-3058-9522
Mobile: +91 976-788-8246*