[GH-ISSUE #100] Fix mtls, client auth feature #51

Open
opened 2026-03-07 22:18:20 +03:00 by kerem · 1 comment
Owner

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.

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.
Author
Owner

@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.

<!-- gh-comment-id:338874771 --> @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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hickory-dns#51
No description provided.