Keeping it to X25519/Ed25519 for now, but arguably we could pick "raw" options for most of our keys. The problem is just when there's a couple different options. (ECPrivateKey or just the serialized scalar for EC keys, compressed vs uncompressed points.) Bug: 42290364 Change-Id: I1e1a0a3fa971f27a962946301091ebe11bac2725 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/81667 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@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.
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.