mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 11:15:54 +03:00
[GH-ISSUE #522] Security vulnerability in 'untrusted' crate which trust-dns uses #217
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#217
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 @cswindle on GitHub (Jul 4, 2018).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/522
When running cargo audit against a crate which uses trust-dns it reports there is a security vulnerability in the version of 'untrusted' create which trust-dns uses:
Could you upgrade to 0.6.2 of 'untrusted' so that cargo audit does not flag a failure?
@bluejekyll commented on GitHub (Jul 4, 2018):
Thank you for the report. I’ll try and do this ASAP.
@bluejekyll commented on GitHub (Jul 4, 2018):
@cswindle can you give me the features you're enabling for trust-dns? I'm guessing it's either
dnssec-ringordns-over-rustls...As of now, the underlying *ring* library is still in alpha: https://crates.io/crates/ring, 0.13 has the upgraded 0.6.1, but I've been hesitant to upgrade until 0.13 stabalizes.
@briansmith, any guidance here?
@briansmith commented on GitHub (Jul 5, 2018):
I would use 0.13-alpha over 0.12 any day, myself. It means everybody using Trust-DNS and using ring for anything would need to upgrade to 0.13-alpha too.
@bluejekyll commented on GitHub (Jul 6, 2018):
Ok, I'll work on getting this in: #327
@cswindle do you need this in 0.9 or in master?
@bluejekyll commented on GitHub (Jul 8, 2018):
I’m going to close this as it’s resolved in master. If we need this before the next release, it can be backported to 0.9
@cswindle commented on GitHub (Jul 9, 2018):
I am happy for it to just be in master.