On 2018-02-27 17:23, Alex Gaynor wrote:
A reasonable compromise that jumps out to me is allowing extensions to make an otherwise-secure connection fail, but not allow them to rehabilitate an insecure connection. This would allow experimenting with stricter controls while avoiding some of the really scary risks.
I've seen extensions give a dialog box about an error and asking the user what to do in case the extensions thinks it's an invalid certificate by firefox say it's ok. But I think those dialogs actually happen after the connection has been set up and maybe even already closed. Adding them as part of the validation might cause delays and errors in some circumstances, which is why OCSP currently has a timeout.
Kurt _______________________________________________ dev-security-policy mailing list [email protected] https://lists.mozilla.org/listinfo/dev-security-policy
