From 8ef497490b61a91d382f3a9c8c562106129bb6a0 Mon Sep 17 00:00:00 2001 From: Edward Houston Date: Thu, 2 Jul 2026 17:06:39 +0200 Subject: [PATCH] fix(features): don't enable rustls/default from rustls-ring "rustls/ring" (without ?) also activates the crate's explicit `rustls` feature, which enables rustls/default, i.e. the aws-lc-rs provider. So use-rustls-ring ends up enabling both crypto providers on rustls, and any crate in the same binary relying on the process-default provider panics ("exactly one of aws-lc-rs and ring"). Use the ?/ syntax so rustls-ring stays ring-only. Fixes #219 --- Cargo.toml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Cargo.toml b/Cargo.toml index eaa9638..57ce896 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -41,7 +41,7 @@ winapi = { version="0.3.9", features=["winsock2"], optional = true } default = ["proxy", "rustls"] proxy = ["byteorder", "winapi", "libc"] rustls = ["webpki-roots", "dep:rustls", "rustls/default"] -rustls-ring = ["webpki-roots", "dep:rustls", "rustls/ring", "rustls/logging", "rustls/std", "rustls/tls12"] +rustls-ring = ["webpki-roots", "dep:rustls", "rustls?/ring", "rustls?/logging", "rustls?/std", "rustls?/tls12"] openssl = ["dep:openssl"] # Old feature names