Skip site navigation (1) Skip section navigation (2)

Re: SSH Tunneling implementation

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: SSH Tunneling implementation
Date: 2012-07-09 10:23:47
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgadmin-hackers
On Mon, Jul 9, 2012 at 12:15 PM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> On Mon, Jul 9, 2012 at 10:51 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> On Mon, Jul 9, 2012 at 11:48 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>>> We've never supported anything other than OpenSSL.
>> For the direct linking. But the question here is what *libssh2* is
>> built against, not what pgadmin is linked against.
>> If you require the entire system to be built against openssl, then the
>> feature won't work on Debian. Or Ubuntu. Or RedHat. Or Fedora. Or
>> SuSE. Or any derived distros. Because they all made the decision to
>> move away from openssl for any packages that support other things
>> (though annoyingly enough, debian/ubuntu went towards gnutls and the
>> redhat style distros went towards libnss - but that's a different
>> story).
> Hmm, good point. In that case Akshay will need to figure out how to
> deal with this some other way.

Or at least verify that it's not just a docu snafu - it might mean
"any external SSL library" or something like that.

 Magnus Hagander

In response to


pgadmin-hackers by date

Next:From: Akshay JoshiDate: 2012-07-09 13:38:44
Subject: Re: SSH Tunneling implementation
Previous:From: Dave PageDate: 2012-07-09 10:15:30
Subject: Re: SSH Tunneling implementation

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group