Feature rpk in boring doesn't do anything unless you explicitly use `SslAcceptor::rpk` or `SslContext::rpk_builder`, and neither of these types are directly reachable if the user depends only on tokio-boring or hyper-boring, which means you still need to explicitly depend on the boring crate to use RPK, in which case you can enable the feature there. |
||
|---|---|---|
| .. | ||
| src | ||
| test | ||
| .gitignore | ||
| Cargo.toml | ||
| LICENSE-APACHE | ||
| LICENSE-MIT | ||
| README.md | ||
README.md
hyper-boring
Hyper SSL support via BoringSSL.
License
Licensed under either of
- Apache License, Version 2.0, (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.
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 as above, without any additional terms or conditions.
Accolades
The project is based on a fork of hyper-openssl.