3 ms·
the issue is that HPKP is as user friendly as GPG but without the same benefits. (learning-curve vs ROI) Also IMO the underlying problem is choosing a CA's in t
by DyslexicAtheist 10y ago
the issue is that HPKP is as user friendly as GPG but without the same benefits. (learning-curve vs ROI) Also IMO the underlying problem is choosing a CA's in the first place. None of them have 'Skin in the Game'[0]. How do you actually decide on which CA is trustworthy?? Trust is measured by how long they have been in the business and how many trust related incidents[0] they had. And how is that confidence measured/created? (hint it isn't Math but whoever has the best marketing or lowest price - not the most trustworthy certs).
CAs are a business model impatiently waiting to be replaced (with something decentralized). It's a self-serving quasi-monopoly that all other vendors that want to implement trust must use.
[0] http://www.fooledbyrandomness.com/SITG.html http://www.fooledbyrandomness.com/SITG.html
[1] https://www.schrauger.com/the-story-of-how-wosign-gave-me-an-ssl-certificate-for-github-com https://www.schrauger.com/the-story-of-how-wosign-gave-me-an...
- DyslexicAtheist 10y agoafterthought: I wouldn't actually call HPKP dead. It's a prerequisite if you want to do any PKI related functions on your site. E.g. <keygen> support was dropped by most browsers and the industry is heading towards native clients. Nevertheless WebCrypto[0] is supposed to offer the same type of quality and you need both HSTS/HPKP if you want to secure your implementation in any meaningful way. [0] https://www.w3.org/TR/WebCryptoAPI/ https://www.w3.org/TR/WebCryptoAPI/