Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

hex (3272)

hex
  (email not shown publicly)
http://downlode.org/

Perl, RDF and wiki hacker, London, UK. This is my former Perl blog; I now write at Earle's Notebook [downlode.org].

Journal of hex (3272)

Saturday March 29, 2008
11:05 PM

Oh joy! Firefox 3 is too secure for PAUSE.

[ #36006 ]

Secure Connection Failed

pause.perl.org uses an invalid security certificate.

The certificate is not trusted because it is self signed.

(Error code: sec_error_ca_cert_invalid)

Luckily it - I'm using FF 3.0b4 - has a very nice new mechanism that lets you add an exception for specific servers, but really I don't think we should be seeing this in the first place... could our lovely PAUSE people please fix this?

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • The problem is that the certificate is self-signed. FF3 just has a different dialogue for approving such a cert, but all browser will prompt you about it.
    • No, I'm not paying for it :-) Sorry if this post came across as ungrateful.

      Hmm. Well, I'm really no expert in the field of authentication, encryption and so on. I was just taken aback a little by the wording of the error message, mainly the word "invalid".

      It would be a nice gesture if some Perl-friendly organization would certify PAUSE, like GoDaddy did for KDE [dattitu.de].

      • GoDaddy seem willing to do it for any open source project https://www.godaddy.com/gdshop/ssl/ssl_opensource.asp?ci=5988 [godaddy.com]
      • I'm just saying nothing's changed except the browser's handling of self-signed certs. Admittedly, that change is rather jarring, since it looks a lot like a "failed to connect to server" error, as opposed to the old "insecure cert" popup.

        The GoDaddy option does seem like a good one.
        • Admittedly, that change is rather jarring, since it looks a lot like a "failed to connect to server" error, as opposed to the old "insecure cert" popup.

          Yep. I just got it for rt.cpan.org as well and it surprised me again.

          The GoDaddy option does seem like a good one.

          Indeed. I shall try and find someone to bring it to their attention.

  • Thanks for the heads up!

    On Sat Apr 19 2008 PAUSE will switch to a cacert certificate. Please prepare your browser [perl.org].