public inbox for [email protected]  

help / color / mirror / Atom feed

From: Stefan Kaltenbrunner <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: Magnus Hagander <[email protected]>
Cc: PostgreSQL www <[email protected]>
Subject: Re: Commitfest website certificate
Date: Wed, 18 Apr 2012 21:16:21 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<CABUevEy7oED1_bOk1nMjCvv6A1haoNpfvd8uLOvCQXSYgN+DDw@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On 04/18/2012 08:54 PM, Bruce Momjian wrote:
> On Wed, Apr 18, 2012 at 08:18:04PM +0200, Stefan Kaltenbrunner wrote:
>> On 04/18/2012 07:58 PM, Bruce Momjian wrote:
>>> On Wed, Apr 18, 2012 at 01:52:27PM -0400, Bruce Momjian wrote:
>>>>> Just to test a theory - do you get the same error if you connect to
>>>>> https://meldrar.postgresql.org?
>>>>
>>>> Yes.  Technical details are the same too:
>>>>
>>>>   Technical Details
>>>>           meldrar.postgresql.org uses an invalid security certificate.
>>>>
>>>>   The certificate is not trusted because no issuer chain was provided.
>>>>
>>>>   (Error code: sec_error_unknown_issuer)
>>>
>>> Here is someone having a similar error on Firefox 11:
>>>
>>> 	http://support.mozilla.org/en-US/questions/923163
>>
>> yeah if you are NOT getting the error on https://www.postgresql.org we
>> have identified the issue(it is affecting most of our ssl enabled sites
>> running lighttpd) as some sort of viral(...) copy&paste fail - will be
>> fixed soon...
> 
> I can confirm that is now fixed!  Thanks.

heh it was not actually fixed the moment you sent the mail, it "looked"
like it was fixed to you because your client probably cached the
intermediate certs the time you hit www.postgresql.org...


Stefan

view thread (12+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Commitfest website certificate
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox