boring2/hyper-boring
Christopher Patton c774afc859 Add feature "fips-no-compat"
As of boringSSL commit a430310d6563c0734ddafca7731570dfb683dc19, we no
longer need to make exceptions for the types of BufLen, ProtosLen, and
ValueLen, which means the "fips-compat" feature is no longer needed for
"fips" users.

Currently "fips" implies "fips-compat". To allow users to upgrade
without breaking API compatibility with boring version 4, add a new
feature, "fips-no-compat", that does not imply "fips-compat".

In boring 5, we should remove "fips-no-compat" and decouple
"fips-compat" from "fips".
2025-03-14 22:22:41 +00:00
..
src Revert "Refactor!: Remove strict `TokioIo` response requirement from `hyper_boring::v1::HttpsConnector`" 2025-02-21 10:41:18 +00:00
tests Revert "Refactor!: Remove strict `TokioIo` response requirement from `hyper_boring::v1::HttpsConnector`" 2025-02-21 10:41:18 +00:00
.gitignore Add hyper-boring 2020-11-11 20:29:54 +00:00
Cargo.toml Add feature "fips-no-compat" 2025-03-14 22:22:41 +00:00
LICENSE-APACHE Add hyper-boring 2020-11-11 20:29:54 +00:00
LICENSE-MIT Add hyper-boring 2020-11-11 20:29:54 +00:00
README.md Add hyper-boring 2020-11-11 20:29:54 +00:00

README.md

hyper-boring

Documentation

Hyper SSL support via BoringSSL.

License

Licensed under either of

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.