Alejandro Gasca wrote:
> No. same problem..
> I unzip the libpq.dll (18.104.22.16868) and replace the other.
> OpenSSL: FATAL.
> OPENSSL_Uplink(00DF4010,05): no OPENSSL_Applink.
Hmm, OK on further investigation it looks like the applink code must be
in the exe, not the dll. This is *really* annoying because it means that
anyone writing a libpq based application now also needs the OpenSSL
headers of the exact version used in libpq :-(. For me thats not an
issue of course, but I doubt many others build Postgres and their app
Anyway, I've committed a fix for pgAdmin which seems to work using the
certificates you sent me. I'll send you a .exe to test if you like?
One other annoying side effect is that a debug build of pgAdmin *must*
now use a debug build of libpq, otherwise it'll outright crash when
connecting to an SSL server with a client certificate :-(
In response to
pgadmin-support by date
|Next:||From: Dave Page||Date: 2007-09-28 11:00:16|
|Subject: Re: Bug in pgadmin table properties (tested on
|Previous:||From: Kieran McCusker||Date: 2007-09-28 08:56:43|
|Subject: Feature request in pgadmin (tested on Beta 5)|