05c6a41270
This ensures that all the Rust functions, types and constants always match the actual BoringSSL definitions. It also removes quite a lot of manually maintained code, as well as the need for systest. The value for `SslOptions::ALL`, for example, was wrong. On current BoringSSL versions, this is a no-op, and is set to `0`. Clearing it does nothing. So, the `clear_ctx_options` test, that passed by accident, was adjusted to use a different option. The `libc` crate is not required, as we only use it for types that are already defined in the standard library. It was removed from `boring-sys`. The same can be done to other crates later. |
||
|---|---|---|
| .. | ||
| examples | ||
| src | ||
| test | ||
| Cargo.toml | ||
| LICENSE | ||
| README.md | ||
README.md
boring
BoringSSL bindings for the Rust programming language and TLS adapters for tokio and hyper built on top of it.
Release Support
The crate statically links with the latest BoringSSL master branch.
Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed under the terms of both the Apache License, Version 2.0 and the MIT license without any additional terms or conditions.
Accolades
The project is based on a fork of rust-openssl.