Conversation
Signed-off-by: Zafer Balkan <zafer@zaferbalkan.com>
zbalkan
changed the title
zbalkan
changed the title
Signed-off-by: Zafer Balkan <zafer@zaferbalkan.com>
Signed-off-by: Zafer Balkan <zafer@zaferbalkan.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.
ML-DSA-44 DNSSEC authoritative signing support
Adds experimental authoritative DNSSEC signing support for ML-DSA-44 using DNSSEC algorithm number 18.
This PR depends on TechnitiumLibrary PR #70, which provides algorithm-18 DNSKEY/RRSIG handling and resolver-side ML-DSA validation.
Included
ML-DSA private-key import currently requires a PKCS#8 representation that retains the 32-byte seed. Expanded-only ML-DSA private-key encodings are rejected because the existing DnsServer persistence format stores and reconstructs ML-DSA keys from that seed.
The implementation intentionally reuses the existing
DnssecPrivateKey, zone-signing, persistence, rollover, API, and UI paths rather than introducing ML-DSA-specific abstractions.This remains experimental while the DNSSEC ML-DSA specification is a draft.