3 ms·
> First off, TLSA Certificate Usage 2 also effectively turns the DNS into a CA, so you're just factually off here. Whoops. Usages 0 and 1, then. > Second, wh
by amluto 10y ago
> First off, TLSA Certificate Usage 2 also effectively turns the DNS into a CA, so you're just factually off here.
Whoops. Usages 0 and 1, then.
> Second, why is this a compelling argument? The first 2 TLSA usages are essentially what we already have: HPKP, bootstrapped from the DNS.
TLSA usages 1 and 2 bootstrap off something that still works even if you've
never visited the site before (or if you're in private browsing mode, etc).
HPKP can't do that unless you preload.
> Further: all the problems people have with pinning (certificate suicide) remain in place with TLSA 0 and 1.
That's just not true. You can set a reasonable TTL and rescue yourself in a timely manner from a lost certificate without significantly impacting security. With HPKP, if you set a very short expiration, you lost almost all of your security.