[GH-ISSUE #2499] DigestType specifies 5 as ED25519, but IANA says that's actually GOST R 34.11-2012 #1001

Closed
opened 2026-03-16 01:14:08 +03:00 by kerem · 4 comments
Owner

Originally created by @jcgruenhage on GitHub (Oct 8, 2024).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2499

DigestType is an enum of digest types for DNSSEC. For 5 ED25519 it 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 ED25519 anymore, but as GOST R 34.11-2012, linking to RFC 9558.

Originally created by @jcgruenhage on GitHub (Oct 8, 2024). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2499 `DigestType` is an enum of digest types for DNSSEC. For `5 ED25519` it specifies an RFC draft as the source, and the docs link to the relevant IANA registry as well. https://github.com/hickory-dns/hickory-dns/blob/7887002d1198ed9faaaae531e0f9815c10589f7a/crates/proto/src/rr/dnssec/digest_type.rs#L33 https://github.com/hickory-dns/hickory-dns/blob/7887002d1198ed9faaaae531e0f9815c10589f7a/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 `ED25519` anymore, but as `GOST R 34.11-2012`, linking to RFC 9558.
kerem closed this issue 2026-03-16 01:14:13 +03:00
Author
Owner

@djc commented on GitHub (Oct 8, 2024):

Thanks for the report, would you be able to submit a PR for this?

<!-- gh-comment-id:2399437910 --> @djc commented on GitHub (Oct 8, 2024): Thanks for the report, would you be able to submit a PR for this?
Author
Owner

@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.

<!-- gh-comment-id:2399451281 --> @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.
Author
Owner

@djc commented on GitHub (Oct 8, 2024):

Trying is a good start, please open a draft PR if things get too messy.

<!-- gh-comment-id:2399499699 --> @djc commented on GitHub (Oct 8, 2024): Trying is a good start, please open a draft PR if things get too messy.
Author
Owner

@jcgruenhage commented on GitHub (Feb 18, 2025):

Resolved in f0a72c67c5

<!-- gh-comment-id:2665130203 --> @jcgruenhage commented on GitHub (Feb 18, 2025): Resolved in f0a72c67c5dbab564ad63e50078ed6173f4c1cf9
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hickory-dns#1001
No description provided.