Security/Foreign Certificate Warning: Difference between revisions

→‎Challenges: add "private CA" (for internal sites) challenge
(→‎Challenges: add a note from ekr)
(→‎Challenges: add "private CA" (for internal sites) challenge)
Line 54: Line 54:
#* We should steer people towards the SUMO page on [https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-caused-malware how to remove malware].
#* We should steer people towards the SUMO page on [https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-caused-malware how to remove malware].
# The name of the certificate issuer is under the controller of the person minting the cert (i.e. the attacker in malicious cases).
# The name of the certificate issuer is under the controller of the person minting the cert (i.e. the attacker in malicious cases).
# Organizations using private CAs would be affected by this even though in this case there is no MITM (see [https://code.google.com/p/chromium/issues/detail?id=81623#c20 rsleevi's comment] on a similar feature).
#* This may not be perceived as bad for internal sites as [https://code.google.com/p/chromium/issues/detail?id=81623#c28 suggested by mnot].


== Related ==
== Related ==


* [https://bugzilla.mozilla.org/show_bug.cgi?id=1135776 Bug 1135776]: show a different UI for certificates issued by non-built-in root certificates
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1135776 Bug 1135776]: show a different UI for certificates issued by non-built-in root certificates
Confirmed users
908

edits