Skip to content

Allow using system's crypto library instead of BoringSSL. #219

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

Merged
merged 2 commits into from
Jan 12, 2022

Conversation

PiotrSikora
Copy link
Member

Use: bazel test --define crypto=system //test/...

Signed-off-by: Piotr Sikora [email protected]

Use: bazel test --define crypto=system //test/...

Signed-off-by: Piotr Sikora <[email protected]>
@PiotrSikora PiotrSikora merged commit 4540d32 into proxy-wasm:master Jan 12, 2022
jwendell added a commit to jwendell/envoy-1 that referenced this pull request Aug 15, 2022
Upstream has support for using a local SSL library, which was added in
this PR: proxy-wasm/proxy-wasm-cpp-host#219

The change above incorporates our downstream changes so there's no need
to use our fork for the OpenSSL purpose.
maistra-bot pushed a commit to maistra/envoy that referenced this pull request Aug 25, 2022
Upstream has support for using a local SSL library, which was added in
this PR: proxy-wasm/proxy-wasm-cpp-host#219

The change above incorporates our downstream changes so there's no need
to use our fork for the OpenSSL purpose.
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