rustls-rustcrypto-azul 0.1.0

Pure Rust cryptography provider for the Rustls TLS library using algorithm implementations from the RustCrypto organization (azul's fork of rustls-rustcrypto: the unreleased upstream master on the elliptic-curve 0.14 / crypto-bigint 0.7 generation, published so dependents need no [patch]; otherwise upstream's code)
docs.rs failed to build rustls-rustcrypto-azul-0.1.0
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.

rustls-rustcrypto-azul

azul fork. This is rustls-rustcrypto-azul, a fork of rustls-rustcrypto for the azul GUI framework. The newest upstream release, 0.0.2-alpha, is built on p256/p384 0.13, whose crypto-bigint 0.5 leaks timing in its Montgomery multiplication (RUSTSEC-2026-0387), and it pulls in rustls-webpki 0.102, a line without security fixes. Upstream's master already moved to the elliptic-curve 0.14 / crypto-bigint 0.7 generation but is not released; a [patch] cannot reach the users of a published crate, so this fork publishes that master (commit 70f76c0) with three changes:

  • crypto-bigint is held at 0.7.6 or newer, the first release with the timing fixes;
  • a SEC1 EC key is parsed by its curve's SecretKey again, so a key of another curve or with a mismatching public key is refused, as in 0.0.2-alpha (upstream's master took the raw scalar);
  • an in-memory handshake test covering every suite, key exchange group and key type.

The library keeps upstream's name, so rustls_rustcrypto::provider() works unchanged. Use the official rustls-rustcrypto crate once it releases this generation.

crate Docs Build Status Apache2/MIT licensed Rust Version Project Chat

RustCrypto-based provider implementation for version 0.23 of rustls, maintained by the RustCrypto organization.

⚠️USE THIS AT YOUR OWN RISK! DO NOT USE THIS IN PRODUCTION⚠️

Not only that this is incomplete that only few selected TLS suites implemented (it should be well enough to cover 70% of the usage), but the elephant in the room is that neither did rustls nor RustCrypto packages were formally verified and certified with FIPS compliance.

Note that RustCrypto performance is generally inferior than ring, but in exchange you got a pure Rust implementation that theoretically compiles everywhere Rust was ported to. In our case, we need to have std but foundational support for future no_std expansion is already here.

Supported Cipher Suites

  • TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
  • TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
  • TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
  • TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
  • TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
  • TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
  • TLS13_AES_128_GCM_SHA256
  • TLS13_AES_256_GCM_SHA384
  • TLS13_CHACHA20_POLY1305_SHA256

License

Licensed under either of:

at your option.

Some code authored by @ctz was adapted from upstream rustls. Licensed as above with permission.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.