Confirmed in ngrok v0.15.0. In [futures-rustls’s Cargo.toml](https://github.com/rustls/futures-rustls/blob/944fe7ef3b7bddc0f71529bbbb62046d9abdfbab/Cargo.toml#L19-L27), `aws-lc-rs` is feature enabled by default: ```toml [features] default = ["aws-lc-rs", "tls12", "logging"] # <- enabling aws-lc-rs by default aws-lc-rs = ["rustls/aws_lc_rs"] aws_lc_rs = ["aws-lc-rs"] early-data = [] fips = ["rustls/fips"] logging = ["rustls/logging"] ring = ["rustls/ring"] tls12 = ["rustls/tls12"] ``` And in [ngrok’s Cargo.toml](https://github.com/ngrok/ngrok-rust/blob/3add9a52aed0739be8bb41a3ddf9ffeaa1f2b44d/ngrok/Cargo.toml#L21): ```toml futures-rustls = { version = "0.26.0" } ``` `futures-rustls` is depended upon with all the default features. This prevent the consumer of ngrok to control the backend to be used with rustls. It would help to expose the same features as `futures-rustls` to choose between the two.