From: | "Alejandro Gasca" <galejadror(at)gmail(dot)com> |
---|---|
To: | "Dave Page" <dpage(at)postgresql(dot)org> |
Cc: | "pgAdmin Support" <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: SSL problem in pgAdmin3 1.8.0 beta 5 |
Date: | 2007-09-28 16:14:13 |
Message-ID: | 20d60a6c0709280914h491291c8o12b599e8f91042c1@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
2007/9/28, Dave Page <dpage(at)postgresql(dot)org>:
>
> Alejandro Gasca wrote:
> > No. same problem..
> > I unzip the libpq.dll (8.3.0.7268) 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
> themselves.
>
> 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?
of course
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 :-(
>
> Regards Dave
>
>
Alejandro.
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel B. Thurman | 2007-09-28 17:24:00 | Re: |
Previous Message | Maciek Sakrejda | 2007-09-28 15:44:42 | Re: Feature request in pgadmin (tested on Beta 5) |