Resolve DETs via public DNS with the IANA root trust anchor - #7
Open
erkki wants to merge 1 commit into
Open
Conversation
DNS_SERVER pointed at a lab resolver (141.227.148.117) with lab-zone DNSSEC trust anchors, so DETs registered in the public DNS tree (IANA-registered DRIP prefix, reverse under ip6.arpa) were unreachable. - Use a public recursive resolver (1.1.1.1); validate with the IANA root zone trust anchors (KSK-2017 tag 20326 and KSK-2024 tag 38696, both live during the root rollover). The root anchor is the one key DNSSEC cannot bootstrap in-band; carrying both published anchors covers the rollover since dnsjava's ValidatingResolver does not implement RFC 5011. - Query the DET-certificate RR (type 67, draft-ietf-drip-registries) at the DET's ip6.arpa name and extract the HI from its Ed25519 SubjectPublicKeyInfo, in dnsLookup and resolveDetKey. The legacy PTR -> FQDN -> TXT pubkey chain remains as fallback. The extracted key still passes the existing DET-hash self-certification checks. Rdata test vector fetched from the live registry zone (0.0.0.0.8.3.0.0.1.0.0.2.ip6.arpa); the embedded SPKI equals the UA HI broadcast over the air. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DNS_SERVERpointed at a lab resolver (141.227.148.117) with lab-zone DNSSEC trustanchors, so DETs registered in the public DNS tree (IANA-registered DRIP prefix,
reverse under
ip6.arpa) were unreachable.zone keys (KSK-2017 tag 20326 + KSK-2024 tag 38696, both live during the root
rollover; dnsjava's ValidatingResolver has no RFC 5011, so both are carried).
ip6.arpaname indnsLookupandresolveDetKey; extract the HI from its Ed25519SubjectPublicKeyInfo. Legacy PTR → FQDN → TXT chain kept as fallback. Extracted keys
still pass the DET-hash self-certification checks.
Device-verified against a live NSEC3-signed public zone: the DET certificate resolves
with the AD flag set, its SPKI equals the HI broadcast over the air, and the DNS card
reports DNSSEC valid + DET hash valid. Rdata from the live zone is the test vector.