And an update to the DNS-resolver checks script
And an update to the DNS-resolver checks script
Update for the DNS (zone/authoritative) monitoring test suite
RE: https://mastodon.social/@quad9dns/116211030194032280
An #NTA may reduce short term pain when a #DNSSEC signed zone is broken, but it also weakens validation consistency and can delay proper fixes. That's why @quad9dns wants to keep the use of Negative Trust Anchors to an absolute minimum and handle it with more transparency.
Ouch! @mailbox_org uses RSASHA1-NSEC3-SHA1 for #dnssec, which is not recommended for signing.
How do I know? unbound refuses to resolve it for me.
See also: https://dnsviz.net/d/mailbox.org/dnssec/
So, previously on post-quantum #DNSSEC: not a lot of action. Standardized post-quantum cryptography algorithms like ML-DSA have keys and signatures which are way too long for the #DNS.
https://mastodon.gougere.fr/@DNSresolver/116241567126448201
TLS can deal with it (they run on TCP or QUIC) but we cannot, with UDP. No obvious solution.
@bortzmeyer Sorry, answer is 1828 characters, too large for Mastodon
Cert Authorities Check for DNSSEC from Today
https://www.grepular.com/Cert_Authorities_Check_for_DNSSEC_From_Today
#HackerNews #CertAuthorities #DNSSec #CyberSecurity #TechNews #OnlineSafety