Last modified: 2014-11-09 13:15:38 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T75190, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 73190 - bugzilla.wikimedia.org certificate validity period too long
bugzilla.wikimedia.org certificate validity period too long
Status: RESOLVED DUPLICATE of bug 71156
Product: Wikimedia
Classification: Unclassified
Bugzilla (Other open bugs)
wmf-deployment
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-11-09 07:15 UTC by Jimmy Xu
Modified: 2014-11-09 13:15 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Jimmy Xu 2014-11-09 07:15:39 UTC
Apparently Chrome Canary is unhappy with a certificate expiring in 2017 now.  I'm not sure if this has anything to do with the SHA-1 signature.

You attempted to reach bugzilla.wikimedia.org, but the server presented a certificate for which the period is too long.

NET::ERR_CERT_VALIDITY_TOO_LONG

User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.2 Safari/537.36
Comment 1 Jimmy Xu 2014-11-09 07:17:00 UTC
The same error for gerrit.wikimedia.org.  However phabricator seem to be fine.
Comment 2 Logan Rosen 2014-11-09 08:02:18 UTC
Related Chromium bug: https://code.google.com/p/chromium/issues/detail?id=119211

Looks like the validity of the certificate should not exceed 39 months, with some exceptions.
Comment 3 Andre Klapper 2014-11-09 13:15:38 UTC
Hi Jimmy. Thanks for taking the time to report this!
This particular problem has already been reported into our bug tracking system, but please feel free to report any further issues you find.

*** This bug has been marked as a duplicate of bug 71156 ***

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links