mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 11:15:54 +03:00
[GH-ISSUE #2714] DNSSEC validation incorrectly returning bogus instead of insecure #1045
Labels
No labels
blocked
breaking-change
bug
bug:critical
bug:tests
cleanup
compliance
compliance
compliance
crate:all
crate:client
crate:native-tls
crate:proto
crate:recursor
crate:resolver
crate:resolver
crate:rustls
crate:server
crate:util
dependencies
docs
duplicate
easy
easy
enhance
enhance
enhance
feature:dns-over-https
feature:dns-over-quic
feature:dns-over-tls
feature:dnsssec
feature:global_lb
feature:mdns
feature:tsig
features:edns
has workaround
ops
perf
platform:WASM
platform:android
platform:fuchsia
platform:linux
platform:macos
platform:windows
pull-request
question
test
tools
tools
trust
unclear
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hickory-dns#1045
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @divergentdave on GitHub (Jan 10, 2025).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2714
Describe the bug
With some zones, the Hickory DNS validating recursive resolver incorrectly gets a bogus validation result instead of an insecure validation result in cases where there's a signed proof of nonexistence of a DS record.
To Reproduce
The ede-dot-com tests for
unsigned.extended-dns-errors.comandno-ds.extended-dns-errors.comdemonstrate this.@divergentdave commented on GitHub (Jan 29, 2025):
This is due to a NSEC3 validation bug. The root cause is a case-sensitive comparison of base32-encoded hash labels:
github.com/hickory-dns/hickory-dns@5df2783517/crates/proto/src/dnssec/dnssec_dns_handle/nsec3_validation.rs (L547)The zones signed and served by BIND use uppercase labels, while the validation routine encodes hashes into lowercase labels here. I'm going to work on a fix for this, and look for any other similar comparisons.