News for hackers. Stuff that matters.
Re:The Security Impact of HTTPS Interception [pdf] by jusob on Tuesday February 07, 2017 @04:04PM (#13592787)
It is part of the RFC: if a certificate is signed by a root certificate that is trusted in your private store (meaning it was added later on), HPKP is ignored. Unfortunately, this is required in the enterprise world where corporate MiTM is often done (Palo Alto Network SSL proxy, Websense/Forcepoint, Zscaler, Blue Coat, etc.) for content inspection.
Re:The Security Impact of HTTPS Interception [pdf] by voidlogic on Tuesday February 07, 2017 @04:18PM (#13592894)
>Unfortunately, this is required in the enterprise world where corporate MiTM is often done

This still should not be the default, rather corps should have an easy about:config switch they can flip. The default should protect private users.

Re:The Security Impact of HTTPS Interception [pdf] by ryan-c on Tuesday February 07, 2017 @04:36PM (#13593051)
How is that a meaningfully different experience? Anything able to install a CA can flip the config value.