WIP Adds OCSP support for BoringSSL #6982
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Does this mean you copied the source code? It might cause license issue. Copying source code from their main (master) branch would make things safe and easy because it's AL2. |
Contributor
Author
|
@MasakiT Good point. I'm going to close for now do some research. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Takes some source files from openssl-1.0.2u that implement the missing server-side OCSP response fetching APIs that were removed in boringssl and creates a new library from that (ocsp4boringssl). This is built and linked against if boringssl is detected.
NOTE: This is currently incomplete (still migrating changes to this branch)