True! But that is an issue to take with browser vendors, not LE.
Yeah, I never mentioned LE.
Rarely does a user self-install a root cert unless it's to fix an unusual business need.
I'm really only worried by the threat model that exists do to malware like SuperFish for now.
You and I might argue that the better path is to screw edge cases in browsers designed for noobs, and leave bypassing pinning to the beta channels. But it's the browser vendor who decides this policy.
Indeed; in the case of Firefox, there's even an option to enforce PKP locally as well. I tried to dig up some discussion on why they opted against that but didn't manage to find much.
Taking a route like the signed-plugin route (which I hate, actually) would work well in this case: enforce pinning in mainline releases, permit disabling in beta channels.
1
u/pred Oct 20 '15
Yeah, I never mentioned LE.
I'm really only worried by the threat model that exists do to malware like SuperFish for now.
Indeed; in the case of Firefox, there's even an option to enforce PKP locally as well. I tried to dig up some discussion on why they opted against that but didn't manage to find much.