Re:Public Key Pinning Extension for HTTP
by pierre_massat on Tuesday October 28, 2014 @10:52AM
(#8521224)
I believe your first link is still version 20. Here is version 21: https://tools.ietf.org/html/draft-ietf-websec-key-pinning-21 .
Also, your second link point to a 404.
There is a 'g' missing in the link to Mozilla Wiki: https://wiki.mozilla.org/SecurityEngineering/Public_Key_Pinn... .
And https://tack.io doesn't respond for me whereas http://tack.io does.
Somehow I managed to break every single link. Fixed them now. Thanks for the heads-up!
HPKP has actually been implemented in Firefox as of a few days ago. [1] We also started on putting together a wiki page on MDN, feel free to help! [2]
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=787133 [2] https://developer.mozilla.org/en-US/docs/Web/Security/Public...
Chrome has been doing public key pinning out of the box for about three years now, though the feature has only been active for some Google properties and a couple of hand-picked high-profile sites [2]. Firefox has recently added support for static pins, plans to support the HTTP extensions exist [3].
Alternative or complementary proposals include DANE/TLSA [4] (DNS-based Authentication of Named Entities; stores certificate infos for any protocols in a new DNS record; requires DNSSEC) and TACK [5] (Trust Assertions for Certificate Keys; a similar mechanism to the one proposed in this draft but implemented as a TLS extension; possibly discontinued).
[1] https://tools.ietf.org/html/draft-ietf-websec-key-pinning-21
[2] https://www.imperialviolet.org/2011/05/04/pinning.html
[3] https://wiki.mozilla.org/SecurityEngineering/Public_Key_Pinn...
[4] https://en.wikipedia.org/wiki/DNS-based_Authentication_of_Na...
[5] http://tack.io