On Wed, Apr 18, 2012 at 09:16:21PM +0200, Stefan Kaltenbrunner wrote:
> 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...
Oh, good point.
-- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB
http://enterprisedb.com
+ It's impossible for everything to be true. +
