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

Begin building with BoringSSL in our CI, no tests yet #6554

Merged
merged 7 commits into from
Nov 6, 2021

Conversation

alex
Copy link
Member

@alex alex commented Nov 6, 2021

No description provided.

@alex alex force-pushed the boringssl-build-only branch 2 times, most recently from 2620515 to 15cb7eb Compare November 6, 2021 03:15
@alex alex force-pushed the boringssl-build-only branch 3 times, most recently from e6eb473 to 1e9f23d Compare November 6, 2021 04:04
@alex alex force-pushed the boringssl-build-only branch from 1e9f23d to 417606f Compare November 6, 2021 13:02
@reaperhulk reaperhulk merged commit 3e0ab39 into pyca:main Nov 6, 2021
@alex alex deleted the boringssl-build-only branch November 7, 2021 03:13
vishwin pushed a commit to vishwin/py-cryptography that referenced this pull request Dec 23, 2022
* Attempt to build against BoringSSL in CI

* Check for BoringSSL in the SSL bindings

* Check for BoringSSL in the err bindings

* Check for BoringSSL in the pkcs7 bindings

* Check for BoringSSL in the bignum bindings

* Check for BoringSSL in the EVP bindings

* Check for BoringSSL in the X.509 verify bindings
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants