Move to rind from the library you use
Each page gives the change for one library: the Cargo.toml lines, the code that changes, and what rind cannot back.
This survey is MIGRATING.md's, as main has it.
Crates with their own crypto backend
Surveyed on 2026-10-31 against each crate's latest release, by reading its
features and source; none were built. A migrated graph should give no output
from cargo tree -e normal,build -i ring or -i aws-lc-sys, except
ring v0.17.999 from rind-patch under the ring patch.
"Install" means calling rind_rustls::default_provider().install_default()
before the crate builds its TLS config. Crates that read rustls's process
default panic without one, and a few (jsonrpsee, pingora, tauri on mobile)
install ring's if nothing is installed first.
- rind-rustls: TLS runs through rustls. Pick the listed features and install or pass rind-rustls's provider.
- rind-x: an existing adapter crate covers it.
- Pure Rust: its default build, or the listed features, use neither.
- Patch: ring 0.17 is hard-wired, and a binary moves it with the ring patch. Built against the patch on 2026-11-06, with no other ring left in the tree.
- Adapter: a new
rind-*crate could cover it through a public hook. Adapters says which are worth building. - Unsupported: aws-lc-rs, ring 0.16, or a ring item rind-ring leaves out is hard-wired. The cell names the alternative or the upstream change that would fix it.
TLS and HTTP
| Crate | What ties it | On rind |
|---|---|---|
| rustls 0.23 | ring and aws_lc_rs features pick a provider |
rind-rustls: default-features = false, std, tls12 |
| rustls-webpki 0.103 | ring and aws-lc-rs fill ALL_VERIFICATION_ALGS |
rind-rustls: no features; direct callers pass rind_rustls::default_provider().signature_verification_algorithms.all |
| rustls-platform-verifier 0.7 | none | rind-rustls: Verifier::new(provider) |
| tokio-rustls 0.26, futures-rustls 0.26 | default aws_lc_rs |
rind-rustls: default-features = false, logging, tls12 |
| hyper-rustls 0.27 | default aws-lc-rs |
rind-rustls: default-features = false and a with_provider_and_* builder; with_native_roots() and its siblings need ring or aws-lc-rs |
| reqwest 0.13 | default rustls is aws-lc-rs |
rind-rustls: rustls-no-provider, install. http3 always enables aws-lc-rs |
| ureq 3 | default rustls is ring |
rind-rustls: rustls-no-provider (marked unstable) and rustls-webpki-roots, or platform-verifier with the agent's roots set to RootCerts::PlatformVerifier, install |
| axum-server 0.8 | tls-rustls is aws-lc-rs |
rind-rustls: tls-rustls-no-provider, install |
| actix-web 4, actix-tls 3, awc 3 | none | rind-rustls: rustls-0_23, with a server config built on rind-rustls; awc's default client needs rustls-0_23-webpki-roots or rustls-0_23-native-roots, install |
| tonic 0.14 | tls-ring, tls-aws-lc |
rind-rustls: tls-native-roots or tls-webpki-roots alone (a server-only build needs _tls-any), install |
| tungstenite 0.30, tokio-tungstenite 0.30 | none | rind-rustls: a rustls-tls-*-roots feature, install |
| tokio-websockets 0.13 | handshake SHA-1 from ring, aws-lc-rs, or OpenSSL | rind-rustls: sha1_smol and rustls-bring-your-own-connector |
| lettre 0.11 | rustls-tls is ring |
rind-rustls: rustls-no-provider, install |
| kube 4 | default rustls-tls with ring |
rind-rustls: client and rustls-tls, install. oidc and oauth need Patch |
| async-nats 0.51 | default ring; crypto hashes with it |
rind-rustls: without ring, crypto, or object-store, install; with them, Patch |
| mysql_async 0.37 | default-rustls is aws-lc-rs |
rind-rustls: default-rustls-no-provider, install |
| tokio-postgres-rustls 0.14 | optional, off by default | rind-rustls: default features |
| bollard 0.21 | ssl is ring |
rind-rustls: ssl_providerless, install |
| ldap3 0.12 | tls-rustls-*; gssapi and ntlm call ring |
rind-rustls: tls-rustls and rustls-provider, install; not gssapi or ntlm |
| metrics-exporter-prometheus 0.18 | push-gateway is aws-lc-rs |
rind-rustls: push-gateway-no-tls-provider, install |
| tauri 2 | mobile rustls-tls installs ring |
rind-rustls: desktop needs nothing; mobile skips rustls-tls; tauri-plugin-http goes through reqwest 0.12's rustls-tls-native-roots-no-provider |
| AWS SDK: aws-config 1, aws-smithy-http-client 1 | default-https-client is aws-lc-rs; the legacy rustls default is ring |
rind-rustls only under --cfg aws_sdk_unstable, through CryptoMode::Custom; otherwise Adapter. Request signing (aws-sigv4) is pure Rust |
| poem 3 | rustls calls aws-lc-rs; acme* calls ring |
Adapter: a TLS Acceptor over tokio-rustls |
| sqlx 0.9 | tls-rustls-* hard-code ring's or aws-lc-rs's provider |
Patch: tls-rustls-ring-webpki or tls-rustls-ring-native-roots |
| mongodb 3 | default rustls-tls hard-codes ring's provider |
Patch |
| fred 10 | rustls only behind enable-rustls (aws-lc-rs) or enable-rustls-ring |
Patch: enable-rustls-ring |
| rskafka 0.6 | transport-tls enables ring |
Patch |
| jsonrpsee 0.26 | tls enables and installs ring |
Patch |
| pingora 0.9 | pingora-rustls depends on ring | Patch: rustls |
| tiny_http 0.12 | ssl-rustls is rustls 0.20 |
Unsupported over TLS |
| webpki 0.22 | calls ring's io DER reader, which rind-ring leaves out |
Unsupported: legacy; move to rustls 0.23 and rustls-webpki |
| sct 0.7 | ring, unconditionally | Patch |
QUIC, WebRTC, and peer-to-peer
| Crate | What ties it | On rind |
|---|---|---|
| quinn 0.11, quinn-proto 0.11, h3-quinn | rustls is an alias for rustls-ring; the Retry tag, reset key, and token key call ring or aws-lc-rs |
Patch: the default rustls-ring, or noq on rind-rustls |
| noq 1.4 | default ring |
rind-rustls: rustls without ring, plus the caller's HmacKey and HandshakeTokenKey on rind's HMAC, HKDF, and AES-256-GCM |
| iroh 1.4 | default tls-ring picks the provider |
rind-rustls: default-features = false, Endpoint::builder().crypto_provider(..). iroh-relay's server enables ring |
| wtransport 0.7 | needs ring or aws-lc-rs, and quinn's defaults |
Patch: the default ring |
| s2n-quic 1 | s2n-quic-crypto always links aws-lc-rs | Unsupported |
| quiche 0.30 | BoringSSL | Unsupported: C |
| dimpl 0.9 | default aws-lc-rs | rind-dimpl |
| str0m 0.25 | default aws-lc-rs | rind-str0m |
| webrtc 0.21 (rtc 0.21) | default crypto-ring, or crypto-aws-lc-rs |
Patch: the default crypto-ring |
| webrtc-dtls 0.12, stun 0.17, turn 0.17 | ring, unconditionally | Patch |
| libp2p-tls 0.7, libp2p-quic 0.14, libp2p-noise 0.47 | aws-lc-rs and ring, unconditionally | Unsupported: needs a provider hook upstream |
| snow 0.10 | opt-in ring-resolver |
Pure Rust by default. Adapter through CryptoResolver, once rind loads static X25519 keys |
| boringtun 0.7 | ring's ChaCha20-Poly1305 and constant-time comparison | Patch |
DNS
| Crate | What ties it | On rind |
|---|---|---|
| hickory-proto, hickory-net, hickory-resolver 0.26 | TLS, HTTPS, and QUIC need a *-ring or *-aws-lc-rs feature; DNSSEC validation calls them internally |
Patch: the *-ring features. Plain DNS is unaffected |
| domain 0.12 | DNSSEC and TSIG need ring or OpenSSL | Patch: ring, tsig, and unstable-validator. unstable-sign builds RSA keys from components, which rind-ring leaves out |
Certificates, ACME, and tokens
| Crate | What ties it | On rind |
|---|---|---|
| rcgen 0.14 | default ring, or aws_lc_rs, gates KeyPair |
rind-rcgen: ECDSA P-256 and P-384, Ed25519, and loaded RSA keys. Without rcgen's crypto feature, set each certificate's serial number, and its key_identifier_method or the key identifiers are empty |
| instant-acme | 0.8 calls aws-lc-rs or ring; the unreleased 0.9 takes a CryptoProvider |
Unsupported: 0.8 has no provider hook, and 0.9 is unreleased |
| rustls-acme 0.15, tokio-rustls-acme 0.9 | account keys and CSRs call ring or aws-lc-rs | Patch: rustls-acme's ring without its default aws-lc-rs |
| x509-parser 0.18 | verify is ring, verify-aws aws-lc-rs |
Patch: verify, or verify tbs_certificate with the key's module, such as rind::ecdsa::PublicKey::verify |
| x509-certificate 0.25, cryptographic-message-syntax 0.28 | ring types in their public API | Patch |
| sigstore 0.14, tough 0.24 | aws-lc-rs, unconditionally | Unsupported |
| jsonwebtoken 11 | optional aws_lc_rs |
rind-jsonwebtoken, every algorithm. rust_crypto is the pure-Rust alternative |
| jwtk 0.5 | default aws-lc for RSA verification and JWK conversion |
Adapter, for caller-held keys only |
| biscuit 0.8, rusty_paseto 0.10 | ring, unconditionally | Patch |
| paseto 2 | ring 0.16 and OpenSSL | Unsupported |
| passkey 0.6 (passkey-crypto) | optional aws-lc-rs |
Pure Rust by default |
| tame-oauth 0.10 | jwt is ring |
Patch |
| gcp_auth 0.12 | default ring for TLS and service-account signing |
rind-rustls without ring or aws-lc-rs; service-account keys need Patch with the default ring |
| google-cloud-auth 1 | defaults are aws-lc-rs | rind-rustls: default-features = false, install; signing loads keys through the installed provider. idtoken also installs rind-jsonwebtoken |
| yup-oauth2 12 | default ring for TLS and service-account signing |
rind-rustls for user flows, through with_client and hyper-rustls; service accounts need Patch with the default ring |
| matrix-sdk-crypto 0.19 | opt-in rust-x509-verifier-impl |
Pure Rust without it |
Storage, databases, and other
| Crate | What ties it | On rind |
|---|---|---|
| object_store 0.14 | aws, gcp, azure and http enable aws-lc-rs |
rind-object-store, with the *-base features; HTTPS through reqwest on rind-rustls |
| parquet 60 | encryption calls ring |
Patch |
| russh 0.65 | default aws-lc-rs, or ring, for its AES-GCM and ChaCha20-Poly1305 transport |
Unsupported: its cipher trait is private, and its ring calls chacha20_poly1305_openssh, which rind refuses |
| scram 0.6 | ring 0.16, unconditionally | Unsupported |
| ethereum_hashing 0.8 | default ring for SHA-256 |
Pure Rust on x86_64; other targets need ring |
| openmls 0.9 | a provider crate, openmls_rust_crypto or openmls_libcrux_crypto | rind-openmls, in place of openmls_rust_crypto |
Switch with an agent
Paste this into your coding agent, in your repository:
Move this repository from ring or aws-lc-rs to rind, following
https://raw.githubusercontent.com/kixel-ai/rind/main/MIGRATE.mdIt migrates on a local branch, reports the build time, binary size, benchmarks, and tests before and after, and asks before opening a PR or filing an issue. To migrate by hand, MIGRATING.md maps each ring and aws-lc-rs item to rind's.