Conversation

Now that HPKP is removed, browsers should do what they should have done from the beginning by supporting DNSSEC and DANE as a pinning mechanism. No need to support using it as an alternate root of trust. For compatibility can limit it to when DoT or DoH are being used by default.
1
11
This Tweet was deleted by the Tweet author. Learn more
Replying to
Please don't let them impose inane policies on what sort of DANE records are acceptable for web. Anything should be accepted and completely override webpki if DANE semantics say it does (DANE-EE(3) or -TA(2) vs PKIX-*(0 or 1)).
3
Replying to
They aren't going to implement it. It's very clear that it isn't going to happen. It's never going to get implemented if it's only advocated as a replacement for WebPKI instead of something usable alongside it. I want it to get implemented.
2
Replying to and
Similarly, the only reason I mentioned the option of ignoring long TTL records is because I know they'll bring that up as an argument against pinning in general. I wasn't saying they SHOULD do it but that they COULD so their argument doesn't make sense. Perhaps it wasn't clear.