mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 11:15:54 +03:00
[PR #148] [MERGED] Fix sig0 key tag #1269
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#1269
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?
📋 Pull Request Information
Original PR: https://github.com/hickory-dns/hickory-dns/pull/148
Author: @mwanner
Created: 6/12/2017
Status: ✅ Merged
Merged: 6/13/2017
Merged by: @bluejekyll
Base:
master← Head:fix-sig0-key-tag📝 Commits (3)
c1cc8f7Set KeyUsage::Zone for sig0 keys so key tags match with Bind.93a9308Add more specific unit tests for key tags on sig0 keys.94402abAdjust KeyPair::to_sig0key to remain backwards compatible.📊 Changes
2 files changed (+107 additions, -20 deletions)
View changed files
📝
client/src/rr/dnssec/keypair.rs(+19 -1)📝
client/src/rr/dnssec/signer.rs(+88 -19)📄 Description
Please consider adjusting generation of sig0 keys for key tags matching those of Bind. These adjustments fix #147.
I'm not quite sure on why KeyUsage is deprecated, yet used by Bind9. Maybe adjusting a key generated by dnssec-keygen (from Bind) to use a different KeyUsage would work as well. However, I thought I'd rather try to adjust trust-dns than bind.
Note that the RSA parameters are unaffected, but the key tag depends on the configured key's usage. This information is not included in the PEM format of the RSA key, for example.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.