3 ms·
One of the main implementors of TLS in Chrome answered why: <https://www.imperialviolet.org/2015/01/17/notdane.html> https://www.imperialviolet.org/2015/01/17/n
by jcranmer 10y ago
One of the main implementors of TLS in Chrome answered why: <https://www.imperialviolet.org/2015/01/17/notdane.html> https://www.imperialviolet.org/2015/01/17/notdane.html>.
It boils down to:
* Getting the DANE and DNSSEC records to the end users' machines is surprisingly difficult (they recorded 4-5% failure to lookup TXT records that they knew existed), so requiring that it be done to accept a certificate isn't going to work.
* DNSSEC uses 1024-bit RSA, which is now considered too weak to use in web browsers, and the IETF/ICANN refuse to up its security.
- teddyh 10y ago> DNSSEC uses 1024-bit RSA, which is now considered too weak to use in web browsers, and the IETF/ICANN refuse to up its security. False. The root KSK is currently 2048 bits¹, and the ZSK will be changed this year from 1024 to 2048 bits². ① https://www.iana.org/dnssec/icann-dps.txt https://www.iana.org/dnssec/icann-dps.txt ② https://www.icann.org/en/system/files/files/ksk-rollover-operational-implementation-plan-22jul16-en.pdf#22 https://www.icann.org/en/system/files/files/ksk-rollover-ope...