From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Dave Page <dpage(at)postgresql(dot)org> |
Cc: | Alejandro Gasca <galejadror(at)gmail(dot)com>, pgAdmin Support <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: SSL problem in pgAdmin3 1.8.0 beta 5 |
Date: | 2007-09-26 15:44:47 |
Message-ID: | 20070926154447.GF21744@svr2.hagander.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
On Wed, Sep 26, 2007 at 04:40:53PM +0100, Dave Page wrote:
> Dave Page wrote:
> > [CCing Magnus as this could be a problem - pgAdmin 1.8 fails to connect
> > to an SSL server with a 'real' certificate]
> >
> > Alejandro Gasca wrote:
> >> Well, i download the postgresql-8.2.4-1-binaries-no-installer.zip.
> >> the psql packed there connects without problem.
> >
> > Well the main difference between those builds is that pgAdmin 1.8 uses a
> > version of libpq.dll compiled with MSVC++ rather than mingw, and ships
> > with OpenSSL 0.9.8.5 instead of 0.9.8.1 - which is a touch worrying.
>
> OK, on further research it sounds like this might be problem:
>
> http://www.openssl.org/support/faq.html#PROG2
>
> To recap, the error reported was:
>
> OPENSSL_Uplink(00914010,05): no OPENSSL_Applink.
>
> The patch below adds the applink code to libpq. Alejandro; may I send
> you an updated libpq.dll to test?
>
> Magnus; assuming this works, we should add it to the server as well I
> guess - src/backend/libpq/be-secure.c seem reasonable?
Yes. But we probably need an openssl version check as well, no? Won't it
break on older openssl libs otherwise?
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2007-09-26 15:47:19 | Re: SSL problem in pgAdmin3 1.8.0 beta 5 |
Previous Message | Dave Page | 2007-09-26 15:40:53 | Re: SSL problem in pgAdmin3 1.8.0 beta 5 |