mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 11:15:54 +03:00
[PR #2852] [MERGED] ede-dot-com: Add spaces to regexes used on DS sets #3367
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#3367
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/2852
Author: @divergentdave
Created: 3/14/2025
Status: ✅ Merged
Merged: 3/14/2025
Merged by: @divergentdave
Base:
main← Head:david/harden-ede-dot-com-regexes📝 Commits (1)
33c2c06ede-dot-com: Add spaces to regexes used on DS sets📊 Changes
1 file changed (+8 additions, -8 deletions)
View changed files
📝
conformance/packages/dns-test/src/docker/ede-dot-com/configure_child.sh(+8 -8)📄 Description
This fixes an intermittent flake in
hermetic_ds_reserved_key_algo, etc. The root cause was that the/8 2/regex was matching both on the key algorithm and digest type fields, as expected, but also the end and start of the two chunks of the digest, with probability 1/256. Some of these substitutions resulted in adding two extra numbers to the digest, anddnssec-signzonewould later fail with "bad hex encoding", upon reading a 33-byte digest for a SHA-256 DS record. I spot-checked the DS set for each of these zones and confirmed that the records are still modified as expected.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.