Test x509 store api #2652
Closed
Test x509 store api #2652
Conversation
This file contains 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
Fortunately, "openssl verify" makes good use of that API
|
This should increase coverage somewhat. |
richsalz
approved these changes
Feb 16, 2017
levitte
added a commit
that referenced
this pull request
Feb 17, 2017
Reviewed-by: Rich Salz <rsalz@openssl.org> (Merged from #2652)
levitte
added a commit
that referenced
this pull request
Feb 17, 2017
Fortunately, "openssl verify" makes good use of that API Reviewed-by: Rich Salz <rsalz@openssl.org> (Merged from #2652)
|
Merged |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Checklist
Description of change
It turns out that we don't have any test of the
X509_STORE/X509_LOOKUPAPI.openssl verifyuses that API when given-CApathand-CAfile, so this is a fairly simple test based on that command.