290acfa3ba
Cargo.lock files should be checked into version control, per the FAQ.[1] This edits .gitignore to stop ignoring these files, and checks in the latest Cargo.lock generated for bssl-sys and bssl-crypto crates. Unrelatedly, start ignoring /out directories which may be used for builds. [1] https://doc.rust-lang.org/cargo/faq.html#why-have-cargolock-in-version-control Change-Id: I77764645cb550b60b1fc15f6c54163da5cf7cac9 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/80447 Commit-Queue: Lily Chen <chlily@google.com> Auto-Submit: Lily Chen <chlily@google.com> Reviewed-by: David Benjamin <davidben@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.
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.