From: | "Dave Page" <dpage(at)pgadmin(dot)org> |
---|---|
To: | "Andrej Podzimek" <andrej(at)podzimek(dot)org> |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: Bug: certificate expired |
Date: | 2008-10-08 07:30:30 |
Message-ID: | 937d27e10810080030m46d4968ake0ecce5b05ef704e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
On Tue, Oct 7, 2008 at 11:31 PM, Andrej Podzimek <andrej(at)podzimek(dot)org> wrote:
>> Hello,
>>
>> I have been using PgAdmin III with SSL for a couple of months. I set up
>> certificates for both the server and the client, valid until March 2009.
>> Everything worked fine.
>>
>> Now the bad news: PgAdmin refuses to connect since yesterday, with this
>> error message:
>>
>> Error connecting to the server: SSL error: sslv3 alert certificate
>> expired
>>
>> This is obviously a nonsense, as both certificates are valid and system
>> clocks on both computers show correct date and time. I even restarted the
>> PostgreSQL server, which did not help.
>>
>> Using PostgreSQL 8.3.3, compiled --with-openssl.
>>
>> Best regards,
>>
>> Andrej Podzimek
>
> Sorry for answeing my own message, but the bug is still there... This is a
> real showstopper. What could be wrong?
The message comes from OpenSSL/libpq - pgAdmin just displays it for
you. I have no idea why OpenSSL would think your certificate had
expired unless it had. Could it be the the issuing CA certificate has
expired?
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Andrej Podzimek | 2008-10-08 14:12:53 | Re: Bug: certificate expired |
Previous Message | Andrej Podzimek | 2008-10-07 22:31:44 | Re: Bug: certificate expired |