David Benjamin
a4c3f8de44
I believe it is currently fine, but we probably should either box it, or get to the point that the assumptions are less precarious. Rust FFI is anything but safe. Bug: 682 Change-Id: I4b45dd3c3f58fb0ce7c0b8b80b1e6d7d2f7f119f Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/65627 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: David Benjamin <davidben@google.com>
756 B
756 B
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.
WARNING - This crate is experimental and does NOT have a stable API. We expect to iterate on the API as it develops. If you use this crate you must be prepared to adapt your code to future changes as they occur. Additionally, this crate must be updated atomically with BoringSSL. The crate, internally, may depend on implementation details of the library.