From 0a8dff525669a5f974e29bf03daba744b2d84e47 Mon Sep 17 00:00:00 2001 From: wolfbeast Date: Thu, 14 Nov 2019 12:13:54 +0100 Subject: Issue #1289 - Part 1: Add a pref to disable HPKP header processing. --- netwerk/base/security-prefs.js | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'netwerk/base') diff --git a/netwerk/base/security-prefs.js b/netwerk/base/security-prefs.js index ef78ddccb..702315d43 100644 --- a/netwerk/base/security-prefs.js +++ b/netwerk/base/security-prefs.js @@ -132,6 +132,14 @@ pref("security.cert_pinning.process_headers_from_non_builtin_roots", false); // blacking themselves out by setting a bad pin. (60 days by default) // https://tools.ietf.org/html/rfc7469#section-4.1 pref("security.cert_pinning.max_max_age_seconds", 5184000); +// Controls whether or not HPKP (the HTTP Public Key Pinning header) is enabled. +// If true, the header is processed and collected HPKP information is consulted +// when looking for pinning information. +// If false, the header is not processed and collected HPKP information is not +// consulted when looking for pinning information. Preloaded pins are not +// affected by this preference. +// Default: false +pref("security.cert_pinning.hpkp.enabled", false); // If a request is mixed-content, send an HSTS priming request to attempt to // see if it is available over HTTPS. -- cgit v1.2.3