3 ms·
That would be great, we have a mailing list interested people should monitor, we'll definitely let people know once things get far enough for sites to start tes
by trevp 13y ago
That would be great, we have a mailing list interested people should monitor, we'll definitely let people know once things get far enough for sites to start testing the waters.
https://lists.riseup.net/www/arc/tack https://lists.riseup.net/www/arc/tack
Regarding certificate pinning: TACK is a different "style" of pinning, it lets you pin to a self-managed signing key instead of certificate keys. So it gives you more control and security than CA pinning, if you're willing to assume more key management responsibilities (storing a TACK private key, and using it to sign new TLS keys).
I think there's room for both approaches: I'd like to see CA pinning be made easy enough that most sites could deploy a fairly safe, simple pin to popular CAs, while high-security sites make use of TACK pins.
But we'll see how things go.
- StavrosK 13y agoThanks, I will sign up to the list now. So, if I understand it correctly, TACK allows you to become your own CA. I will read the spec for more information (e.g. what prevents the MITM from becoming my CA?) but it sounds very interesting, thanks again.
- trevp 13y agoRe "become your own CA" - that's basically the idea. The "pin activation" algorithm is intended to make it difficult for a MITM to foist bad pins on clients, and to limit the lifetime of such pins.