3 ms·
What happens if a random site gets compromised and serves an HPKP header pinning a bad key for ten years?
by JoshTriplett 11y ago
What happens if a random site gets compromised and serves an HPKP header pinning a bad key for ten years?
- 0x0 11y agoNext generation ransomware, holding pinned SSL keys hostage? :O
- lstamour 11y agoThere's max-age support, the ability to preload pins in the browser, and certificate transparency to work around this, see section 4.5: https://tools.ietf.org/html/rfc7469#page-21 https://tools.ietf.org/html/rfc7469#page-21 As to this original point, it would be best if this didn't apply to the address bar URL / main document request. But it's a good point, worth considering. Perhaps the UA should set a timer, and two or three refreshes in a row would be the equivalent to the prior refresh behaviour.