219a6bccea
Merge remote-tracking branch 'upstream/master'
2025-09-08 17:00:51 +08:00
ca9cb3fc66
build(deps): update compio requirement from 0.15.0 to 0.16.0 ( #96 )
...
* build(deps): update compio requirement from 0.15.0 to 0.16.0
Updates the requirements on [compio](https://github.com/compio-rs/compio ) to permit the latest version.
- [Release notes](https://github.com/compio-rs/compio/releases )
- [Commits](https://github.com/compio-rs/compio/compare/v0.15.0...v0.15.0 )
---
updated-dependencies:
- dependency-name: compio
dependency-version: 0.15.0
dependency-type: direct:production
...
Signed-off-by: dependabot[bot] <support@github.com>
* update
* update
* update
---------
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: 0x676e67 <gngppz@gmail.com>
2025-09-08 16:51:01 +08:00
197b9fcb5c
Merge remote-tracking branch 'upstream/master'
2025-09-04 16:20:35 +08:00
c5045fb6b4
Fix patched docs.rs builds
2025-09-03 17:24:22 +01:00
8966ca27b7
Test docs.rs docs
2025-09-03 17:24:22 +01:00
d9a1d9442e
feat(boring): adapt boring2 for quinn ( #87 )
2025-07-25 07:28:03 +08:00
109c35839c
chore: fix ci and docs
2025-07-07 21:32:45 +08:00
83e049d8d9
feat(boring): adapt `boring2` for compio async runtime ( #85 )
...
close: https://github.com/0x676e67/boring2/issues/78
2025-07-07 21:10:50 +08:00
9fb6143b11
chore(boring): deprecate legacy `CertCompressionAlgorithm` API ( #69 )
...
* chore(boring): deprecate legacy `CertCompressionAlgorithm` API
* ci: fix windows build
2025-05-18 18:55:08 +08:00
ee6d225ea3
ci: use ubuntu-latest ( #66 )
2025-04-23 12:54:54 +08:00
9c4ea22f72
Use ubuntu-latest for all ci jobs
...
ubuntu 20.04 is now deprecated:
https://github.com/actions/runner-images/issues/11101
2025-04-17 01:18:30 -07:00
ba1ee0dd48
v4.15.11
2025-03-21 20:38:44 +08:00
f55f9e1dd2
build: update workflows action ( #61 )
2025-03-21 19:36:03 +08:00
20f203cb57
Update ci.yml
2025-03-21 18:19:39 +08:00
11630058f0
Revert "Remove "fips-no-compat", decouple "fips-compat" from "fips"" ( #334 )
2025-03-17 21:37:14 -05:00
57307d739e
Remove "fips-no-compat", decouple "fips-compat" from "fips"
...
Modify the "fips" feature so that it no longer implies "fips-compat".
The latter is no longer needed for recent builds of boringSSL; users who
need older builds will need to enable "fips-compat" explicitly.
Also, remove the "fipps-no-compat" feature, as it's now equivalent to
"fips".
2025-03-16 08:43:52 +00:00
221efdfea9
Update to actions/cache@v4 ( #328 )
2025-03-10 10:03:32 -07:00
7b4bfcbbee
Revert "Refactor!: Introduce a Cargo feature for optional Hyper 0 support"
...
This reverts commit 49d5a61163
2025-02-21 10:41:18 +00:00
49d5a61163
Refactor!: Introduce a Cargo feature for optional Hyper 0 support
...
Closes #294 . Requires breaking changes. The default v0 is changed in
favor of v1, but v0 is still kept available, just in a forced module
path. It enables dependency de-duplication when consuming it.
Signed-off-by: Paul Mabileau <paul.mabileau@harfanglab.fr>
2024-12-07 21:07:31 +00:00
1946603e15
Work around Rust settings inconsistent iOS SDK version
2024-11-28 11:21:39 -08:00
7bb3647406
(ci): brew link x86 toolchain for macos13 runner
...
It seems we need to manually symlink the x86_64-unknown-linux-gnu
toolchain for the macos13 runner. Also, we don't need to overwrite the
python version anymore
Fixes https://github.com/cloudflare/boring/issues/285
2024-10-24 09:49:47 -07:00
193bf3b9d7
Implement optional Hyper 1 support in hyper-boring ( #246 )
2024-09-18 13:24:35 +02:00
a7bfe0d92c
Fix macos FIPS crossbuild
2024-08-15 15:09:02 -07:00
8786cda639
(ci): Fix macos crossbuild action by forcing brew link w python@3.11
2024-07-24 18:19:22 +01:00
b7baacc047
Fix workflows file, pin mac os FIPS crossbuild runner to macos-13
...
The macos-13 runner uses intel chips and thus x86, so clang 12.0.0 is
easily available.
2024-06-26 16:13:58 +01:00
d9f7e4daf6
Fix crosscompile
2024-05-31 09:38:29 +01:00
a8dea4a22c
Introduce X509CheckFlags::UNDERSCORE_WILDCARDS
2024-01-02 15:37:36 +01:00
dd281f6ab6
Swap build and run order; always build
2023-12-14 13:25:47 +01:00
4d66ada007
Use gcc/g++ as the compilers for windows-gnu, not Clang
2023-12-14 13:25:47 +01:00
016d5cb61e
Always run tests in bash
...
This is only necessary for the windows-gnu target, but causes no
issues anywhere else.
2023-12-14 13:25:47 +01:00
8b86852d8a
Add arm64-macos cross-compile to CI
2023-12-14 13:25:47 +01:00
f82f3fcb0f
Add custom linker for Android cross-compilation
2023-12-14 13:25:47 +01:00
16327cf5c5
Add custom environment for ARM Linux cross-compilation
2023-12-14 13:25:47 +01:00
2f62df492b
Build tests even for cross-compiling
2023-12-14 13:25:47 +01:00
1028909b40
Remove musl test; there's no standard musl C++ setup for us to use
2023-12-14 13:25:47 +01:00
08c417a97e
Make arm and Android builds check-only
2023-12-14 13:25:47 +01:00
f5583312c5
Add matrix.apt_packages
2023-12-14 13:25:47 +01:00
bccb80b115
Refactor check-only and extra-test-args
2023-12-14 13:25:47 +01:00
bbe8cd1b9e
Add relevant `--target` to `cargo test` in CI
2023-12-14 13:25:47 +01:00
0f74eade4b
Add CI for cross-building from macOS
2023-10-26 11:31:47 +01:00
2fa3d96966
Use features to set key exchange preferences
...
Overwrite boringSSL's default key exchange preferences with safe
defaults using feature flags:
* "kx-pq-supported" enables support for PQ key exchange algorithms.
Classical key exchange is still preferred, but will be upgraded to PQ
if requested.
* "kx-pq-preferred" enables preference for PQ key exchange,
with fallback to classical key exchange if requested.
* "kx-nist-required" disables non-NIST key exchange.
Each feature implies "kx-safe-default". When this feature is enabled,
don't compile bindings for `SSL_CTX_set1_curves()` and `SslCurve`. This
is to prevent the feature flags from silently overriding curve
preferences chosen by the user.
Ideally we'd allow both: that is, use "kx-*" to set defaults, but still
allow the user to manually override them. However, this doesn't work
because by the time the `SSL_CTX` is constructed, we don't yet know
whether we're the client or server. (The "kx-*" features set different
preferences for each.) If "kx-sfe-default" is set, then the curve
preferences are set just before initiating a TLS handshake
(`SslStreamBuilder::connect()`) or waiting for a TLS handshake
(`SslStreamBuilder::accept()`).
2023-09-01 14:21:35 -07:00
190fb900a0
run `publish --dry-run` instead of `pacakge` on CI
...
As suggested by @inikulin in
https://github.com/cloudflare/boring/pull/159#issuecomment-1697324821
2023-08-30 14:54:18 +01:00
e9318132d8
fix missing space in cargo package CI command
2023-08-30 14:54:18 +01:00
3056660c86
ci: run the cargo package check for all targets
2023-08-30 14:54:18 +01:00
c8d52a7614
add CI jobs to run `cargo package`
2023-08-30 14:54:18 +01:00
d4ddd16ee2
Add fips-link-precompiled feature
2023-07-26 14:35:40 +01:00
0b542999d4
Address review comments
2023-07-10 14:00:52 +01:00
d1ee9bfd86
Use workspace metadata for crates
2023-07-10 11:38:18 +01:00
c4e8a94a69
Add RPK and PQ crypto features
2023-07-07 13:50:36 +01:00
902e7d0c92
Update BoringCrypto to FIPS 140-2 certificate 4407.
...
Signed-off-by: Piotr Sikora <piotr@aviatrix.com>
2023-05-09 10:37:32 +02:00
0x676e67