mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 11:15:54 +03:00
[GH-ISSUE #2499] DigestType specifies 5 as ED25519, but IANA says that's actually GOST R 34.11-2012 #1001
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#1001
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 @jcgruenhage on GitHub (Oct 8, 2024).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2499
DigestTypeis an enum of digest types for DNSSEC. For5 ED25519it specifies an RFC draft as the source, and the docs link to the relevant IANA registry as well.github.com/hickory-dns/hickory-dns@7887002d11/crates/proto/src/rr/dnssec/digest_type.rs (L33)github.com/hickory-dns/hickory-dns@7887002d11/crates/proto/src/rr/dnssec/digest_type.rs (L56)By now, the IANA registry for "DNSSEC Delegation Signer (DS) Resource Record (RR) Type Digest Algorithms" does not specify 5 as
ED25519anymore, but asGOST R 34.11-2012, linking to RFC 9558.@djc commented on GitHub (Oct 8, 2024):
Thanks for the report, would you be able to submit a PR for this?
@jcgruenhage commented on GitHub (Oct 8, 2024):
I can try, but I'm not sure how deep I have to get into the codebase for this.
@djc commented on GitHub (Oct 8, 2024):
Trying is a good start, please open a draft PR if things get too messy.
@jcgruenhage commented on GitHub (Feb 18, 2025):
Resolved in
f0a72c67c5