mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 03:05:51 +03:00
[GH-ISSUE #100] Fix mtls, client auth feature #348
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#348
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 @bluejekyll on GitHub (Mar 9, 2017).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/100
As of now, there have been some unexpected results when working with the ClientAuth feature of rust-native-tls.
See https://github.com/sfackler/rust-native-tls/pull/23 for additional details.
@briansmith commented on GitHub (Oct 24, 2017):
I mentioned this to @bluejekyll already, but AFAICT the Rustls-based TLS support should not run into any of the trouble that is plaguing the rust-native-tls-based implementation, so maybe we can enable mtls using Rustls first.