mirror of
https://boringssl.googlesource.com/boringssl
synced 2026-07-21 14:43:51 +00:00
David Benjamin
b08e6f859a
I haven't yet done ECPrivateKey. That one is a bit hairy since it is two formats in one. Bug: 42290408 Change-Id: Ie579392f5df34c221f79879fa468b930a692e196 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/98730 Reviewed-by: Lily Chen <chlily@google.com> Commit-Queue: David Benjamin <davidben@google.com>
bssl-crypto
Rust bindings to BoringSSL which wrap bssl-sys. Before using this crate, first set up bssl-sys.
Then to run all tests:
cd rust/bssl-crypto && cargo clippy && cargo deny check && cargo test
Unlike BoringSSL itself, this crate does not attempt to handle allocation failures. If an allocation fails, functions in this crate will panic.
Like BoringSSL's API, the crate's API is not strictly stable. We may iterate on it as necessary to meet the needs of our consumers. See this discussion for general notes on how BoringSSL approaches breaking changes.
This crate must be updated atomically with BoringSSL, as it may depend on implementation details of the library. (For example, Rust has different expectations on struct movability than C/C++ APIs typically promise.)