docs.rs failed to build wolfcrypt-ring-compat-1.16.2
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.
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.
wolfcrypt-ring-compat
API-compatible replacement for the ring crate, backed by wolfCrypt instead of BoringSSL.
Usage
# Before
= "0.17"
# After
= { = "1.16", = ["ring-sig-verify"] }
Same API. No application code changes required.
Coverage
AES-GCM, ChaCha20-Poly1305, ECDH (P-256, P-384, X25519), SHA-{1,256,384,512}, HMAC, HKDF, PBKDF2, ECDSA, Ed25519, RSA PKCS#1v1.5 and PSS, SystemRandom. Targets API parity with ring 0.17.
FIPS
= { = "1.16", = ["fips"] }
ring is not FIPS 140-3 certifiable. wolfCrypt is. This is the migration path if you need ring's API with a FIPS-certifiable backend.
Requires a wolfSSL commercial FIPS license and the validated source tree. See the workspace README.
License
MIT