GnuTLS: Backend support for CURLINFO_SSL_VERIFYRESULT #5287
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
|
@emilengler, have you looked into creating a test case for this? |
|
Merged this for now anyway, thanks! |
Not yet, will try to work one later today. |
|
I think the problem is that there is no common interface or libcurl related returns for CURLINFO_SSL_VERIFYRESULT. It is depended on both. The TLS library and the site |
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.
This makes it possible to get a return for peer verification when getting
CURLINFO_SSL_VERIFYRESULTwhen using GnuTLS