explain 0-RTT
This commit is contained in:
parent
93f0ff89c8
commit
bb56056a68
7
user.js
7
user.js
@ -481,7 +481,7 @@ user_pref("_user.js.parrot", "1200 syntax error: the parrot's a stiff!");
|
||||
* safe from the attack if it disables renegotiations but the problem is that the browser can't
|
||||
* know that. Setting this pref to true is the only way for the browser to ensure there will be
|
||||
* no unsafe renegotiations on the channel between the browser and the server.
|
||||
* [STATS] SSL Labs (July 2021) reports over 99% of sites have secure renegotiation [4]
|
||||
* [STATS] SSL Labs (July 2021) reports over 99% of top sites have secure renegotiation [4]
|
||||
* [1] https://wiki.mozilla.org/Security:Renegotiation
|
||||
* [2] https://datatracker.ietf.org/doc/html/rfc5746
|
||||
* [3] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3555
|
||||
@ -490,8 +490,11 @@ user_pref("security.ssl.require_safe_negotiation", true);
|
||||
/* 1203: reset TLS 1.0 and 1.1 downgrades i.e. session only ***/
|
||||
user_pref("security.tls.version.enable-deprecated", false); // [DEFAULT: false]
|
||||
/* 1206: disable TLS1.3 0-RTT (round-trip time) [FF51+]
|
||||
* This data is not forward secret, as it is encrypted solely under keys derived using
|
||||
* the offered PSK. There are no guarantees of non-replay between connections
|
||||
* [1] https://github.com/tlswg/tls13-spec/issues/1001
|
||||
* [2] https://blog.cloudflare.com/tls-1-3-overview-and-q-and-a/ ***/
|
||||
* [2] https://www.rfc-editor.org/rfc/rfc9001.html#name-replay-attacks-with-0-rtt
|
||||
* [3] https://blog.cloudflare.com/tls-1-3-overview-and-q-and-a/ ***/
|
||||
user_pref("security.tls.enable_0rtt_data", false);
|
||||
|
||||
/** OCSP (Online Certificate Status Protocol)
|
||||
|
Loading…
x
Reference in New Issue
Block a user