SSL certificates report incorrect years

Bug #1372414 reported by Michael Sheldon on 2014-09-22
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Oxide
Medium
Chris Coulson
1.2
Medium
Chris Coulson

Bug Description

The effectiveDate and expiryDate properties on SSL certificates are currently returning incorrect year components (usually something like 2381).

To reproduce:

 1. Use webbrowser-app with SSL warning support: https://code.launchpad.net/~michael-sheldon/webbrowser-app/ssl-status/+merge/235309

 2. Visit page with bad SSL certificate, e.g. https://testssl-expire.disig.sk/

 3. Click "Learn more" on the SSL error page.

The "valid from" and "valid to" fields will display an incorrect year in their date.

Chris Coulson (chrisccoulson) wrote :
Changed in oxide:
assignee: nobody → Chris Coulson (chrisccoulson)
importance: Undecided → Medium
milestone: none → branch-1.3
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers