Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rework rpk and no-patches features #172

Merged
merged 2 commits into from
Oct 23, 2023
Merged

Rework rpk and no-patches features #172

merged 2 commits into from
Oct 23, 2023

Conversation

nox
Copy link
Collaborator

@nox nox commented Oct 11, 2023

This removes rpk from tokio-boring and hyper-boring, and replaces feature no-patches with env variable BORING_BSSL{,_FIPS}_ASSUME_PATCHED, see individual commits for rationale.

@nox nox force-pushed the features branch 3 times, most recently from 385c046 to 35c099f Compare October 11, 2023 12:53
@nox
Copy link
Collaborator Author

nox commented Oct 11, 2023

@howardjohn Does the removal of feature no-patches in favour of BORING_BSSL{,_FIPS}_ASSUME_PATCHED adresses the issue from #156?

nox added 2 commits October 23, 2023 12:29
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.
Feature no-patches is ever only useful when setting other env variables
BORING_BSSL{,_FIPS}{,_SOURCE}_PATH, and it has no impact on the APIs
provided by any of the boring crates, so we may as well make it an env
variable itself so downstream users have less features to propagate
across their own crate graph.
@nox nox merged commit 9a0bd94 into cloudflare:master Oct 23, 2023
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants