Sites with untrusted issuers *and* SHA-1 certs issued in 2016 show SHA-1 error
Categories
(Firefox :: Security, defect)
Tracking
()
People
(Reporter: April, Unassigned)
References
()
Details
(Keywords: sec-moderate)
Comment 1•10 years ago
|
||
Comment 2•10 years ago
|
||
| Reporter | ||
Comment 3•10 years ago
|
||
Comment 5•10 years ago
|
||
| Reporter | ||
Comment 7•10 years ago
|
||
Updated•9 years ago
|
Comment 8•6 years ago
|
||
-> frontend
Comment 9•6 years ago
|
||
Seems like another case of bug 1524323
Comment 10•6 years ago
|
||
Firefox before Quantum actually used to report multiple errors.
This is what you get with the current version [if you allow TLS1.0]
Websites prove their identity via certificates, which are valid for a set time period. The certificate for www.pizzolo.com expired on 3/31/2010.
Error code: SEC_ERROR_UNKNOWN_ISSUER
This is what you got before Quantum:
pizzolo.com uses an invalid security certificate.
The certificate is not trusted because the issuer certificate is unknown.
The server might not be sending the appropriate intermediate certificates.
An additional root certificate may need to be imported.
The certificate is not valid for domain pizzolo.com.
The certificate expired on Wednesday March 31. 2010 HH:MM. The current time is Friday August 21. XX:YY
There also used to be a dialogue that listed all the issues by severity, found a picture of it here: https://becomethesolution.com/images/easyblog_articles/1191/b2ap3_large_firefox-confirm-security-exception.png
Comment 11•6 years ago
|
||
Regarding the priority of SHA1 vs unknown issuers - I believe "unknown issuer" should definitely have the priority.
If you have control over "the unknown authority", you can easily make it SHA1 (or expired) and try to hide behind a misleading error.
Description
•