mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 19:25:56 +03:00
[GH-ISSUE #213] [Server] DNSSEC works only with RSASHA256 #99
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#99
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 @Darkspirit on GitHub (Sep 27, 2017).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/213
build
tested both
RSASHA512 (not working)
http://dnsviz.net/d/ikenmeyer.com/e/178696140/dnssec/
RSASHA256 (working)
http://dnsviz.net/d/ikenmeyer.com/e/178696161/dnssec/
config
zone = zone from #209
config.toml
Didn't test RSASHA1 until now: not working.
@bluejekyll commented on GitHub (Sep 27, 2017):
Thank you for working through this! The table you produced in the other #209 is really nice.
@bluejekyll commented on GitHub (Sep 27, 2017):
It looks like we also have an issue with the DNSKEY not being signed or possibly it's RRSIG is not being returned in the request.
I opened #214 for this.
@bluejekyll commented on GitHub (Sep 27, 2017):
Can you also post the config for the RSASHA512 configuration?
@Darkspirit commented on GitHub (Sep 27, 2017):
@bluejekyll commented on GitHub (Sep 28, 2017):
I’m going to see how much progress I can make tonight on this. Add some more test cases, etc. I’ll post to this issue a branch once I have it ready.
@briansmith commented on GitHub (Sep 30, 2017):
As of now, there's no way to create an RSA-SHA1 signature using ring, intentionally.
@Darkspirit commented on GitHub (Sep 30, 2017):
Thinking of the resolver: Verifying 2048+ bit RSA-SHA1 would work (RSA_PKCS1_2048_8192_SHA1), but not beneath (shitty RSA 1024 bit signed zones), right?
I (also?) think one shouldn't be able to deploy such legacy stuff anymore and therefore it shouldn't be possible to use sha1 for signing zones in trust-dns.
@briansmith commented on GitHub (Sep 30, 2017):
Yes, that's right.
I agree. That's why there's no SHA-1 signing API.