min
/
boring2
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
fork of boring2 with prefix patch
2,978 Commits 2 Branches 0 Tags 16 MiB
Rust 99.9%
Go to file
Anthony Ramine 6274f70726 Update boringssl to latest upstream commit 
Notable commits that cause code changes here:

X509 fields notBefore and notAfter need to be specified
https://boringssl-review.googlesource.com/c/boringssl/+/49349

X509ReqBuilder only accepts X509v1 now
https://boringssl-review.googlesource.com/c/boringssl/+/52605

Some functions switched from int to size_t
https://boringssl-review.googlesource.com/c/boringssl/+/54985

CECPQ2 support was dropped
https://boringssl-review.googlesource.com/c/boringssl/+/58645

This is a breaking change.
 		2023-05-09 10:28:10 +02:00
.github/workflows ci: Test builds for iOS targets 2022-06-03 09:11:38 -05:00
boring Update boringssl to latest upstream commit 2023-05-09 10:28:10 +02:00
boring-sys Update boringssl to latest upstream commit 2023-05-09 10:28:10 +02:00
hyper-boring Update changelogs and bump version numbers 2022-09-16 13:03:26 -05:00
scripts Add publish script 2020-11-12 13:08:13 +00:00
tokio-boring bump version number for tokio-boring 2022-09-16 13:13:08 -05:00
.gitignore Rename stuff 2020-11-11 17:47:30 +00:00
.gitmodules Add fips-3678 feature (#52) 2022-01-31 16:11:33 -06:00
.rusty-hook.toml Add tokio-boring 2020-11-11 19:26:22 +00:00
CHANGELOG.md Update changelogs and bump version numbers 2022-09-16 13:03:26 -05:00
Cargo.toml Use bindgen to automatically generate boring-sys 2021-02-12 15:03:45 +01:00
README.md Add fips-3678 feature (#52) 2022-01-31 16:11:33 -06:00
THIRD_PARTY Rename stuff 2020-11-11 17:47:30 +00:00

README.md

boring

crates.io

BoringSSL bindings for the Rust programming language and TLS adapters for tokio and hyper built on top of it.

Documentation.

Release Support

By default, the crate statically links with the latest BoringSSL master branch.

Support for pre-built binaries

While this crate can build BoringSSL on its own, you may want to provide pre-built binaries instead. To do so, specify the environment variable BORING_BSSL_PATH with the path to the binaries.

You can also provide specific headers by setting BORING_BSSL_INCLUDE_PATH.

Notes: The crate will look for headers in the $BORING_BSSL_INCLUDE_PATH/openssl/ folder, make sure to place your headers there.

Warning: When providing a different version of BoringSSL make sure to use a compatible one, the crate relies on the presence of certain functions.

Building with a FIPS-validated module

Only BoringCrypto module version ae223d6138807a13006342edfeef32e813246b39, as certified with certificate 3678 is supported by this crate. Support is enabled by this crate's fips feature.

boring-sys comes with a test that FIPS is enabled/disabled depending on the feature flag. You can run it as follows:

$ cargo test --features fips fips::is_enabled

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.