mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 03:05:51 +03:00
[PR #899] [MERGED] Allow for custom rustls::ClientConfig to be passed to the Resolver #1780
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#1780
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/899
Author: @ziprandom
Created: 10/23/2019
Status: ✅ Merged
Merged: 10/26/2019
Merged by: @bluejekyll
Base:
master← Head:nameserverconfig-holds-rustls-clientconfig📝 Commits (3)
0100f9cAllow for the rustls client to be passed to the resolver6a54e11remove HttpsClientStreamBuilder::add_ca, assert ALPN_H2 in build8277666remove NameServerConfigGroup.set_tls_client_config, add with_client_config📊 Changes
16 files changed (+260 additions, -52 deletions)
View changed files
📝
Cargo.lock(+1 -0)📝
bin/Cargo.toml(+1 -0)📝
bin/tests/named_https_tests.rs(+19 -3)📝
crates/client/src/https_client_connection.rs(+1 -1)📝
crates/https/src/https_client_stream.rs(+15 -18)📝
crates/resolver/src/config.rs(+133 -5)📝
crates/resolver/src/https.rs(+8 -9)📝
crates/resolver/src/name_server/connection_provider.rs(+21 -2)📝
crates/resolver/src/name_server/name_server.rs(+6 -0)📝
crates/resolver/src/name_server/name_server_pool.rs(+24 -10)📝
crates/resolver/src/system_conf/unix.rs(+8 -0)📝
crates/resolver/src/system_conf/windows.rs(+4 -0)📝
crates/resolver/src/tls/dns_over_rustls.rs(+12 -2)📝
crates/resolver/src/tls/mod.rs(+1 -1)📝
tests/integration-tests/tests/client_future_tests.rs(+4 -1)📝
tests/integration-tests/tests/name_server_pool_tests.rs(+2 -0)📄 Description
Currently the
trust-dns-resolveruses a hardcodedrustls::ClientConfigwhen built with thedns-over-rustlsfeature. This makes it impossible to change the accepted root certificates and other properties of the TLS client.This PR adds a new field to the
NameServerConfigto optionally pass arustls::ClientConfigwhich gets used instead. Thewebpki-rootsstore is used as the default fallback so existing implementations should work as before.A new type
TlsClientConfigwas added as a wrapper forrustls::ClientConfigwhich doesn't implement theDebug,Eq&PartialEqtraits. This might become obsolete if rustls can provide the trait implementations one day.The custom
rustls:ClientConfigcan be set via aset_tls_client_configmethod which exists both ontrust-dns-resolver::NameServerConfigGroupandtrust-dns-resolver::ResolverConf.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.