Closed
Bug 1360212
Opened 7 years ago
Closed 7 years ago
SSL Certificate details shows the wrong timezone for the expiry date
Categories
(Core :: Security: PSM, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1351427
People
(Reporter: yufiel, Unassigned)
References
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:53.0) Gecko/20100101 Firefox/53.0 Build ID: 20170418123818 Steps to reproduce: 1. Have a ssl certificate that expires today (e.g. 15:00 CEST) 2. Look at the ssl cert details in the FF, it shows the same time but as GMT (15:00 GMT) Actual results: The browser shows the wrong expiry of the cert. (not tested: marks the cert to early as invalid) Expected results: Use the timesome from the cert or recalculate the expiry datetime correctly.
Updated•7 years ago
|
Component: Untriaged → Security: PSM
Product: Firefox → Core
Your user-agent indicates you are on Linux. Is that where you saw this? Also, can you attach the certificate in question? Thanks.
Flags: needinfo?(yufiel)
Yes, I saw it with a FF 53 on Kbuntu 14.04 and the certificate was deployed on a tomcat 7.0.62. I attached the certificate.
Ah - I can reproduce this in 53 but not 55. Jorg, I'm assuming this was caused by bug 1301640 but was fixed by something like bug 1351427 possibly - can you confirm?
Flags: needinfo?(jorgk)
Comment 5•7 years ago
|
||
Hard to say where this was caused and when it got fixed since there were so many changes in date/time formatting lately. But you're right, those two bugs affected the C++ interface which is used for certificate details. Note that there is still bug 1355977 comment #5 which shows that the " GMT" as appended in a hard-coded fashion: http://searchfox.org/mozilla-central/source/security/manager/ssl/nsNSSCertHelper.cpp#1697 Someone should address this together with bug 1355977 if there's anything to address.
Flags: needinfo?(jorgk)
See Also: → 1355977
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•