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

openssl: fix the SSL_get_tlsext_status_ocsp_resp call #3478

Closed
wants to merge 1 commit into from

Conversation

bagder
Copy link
Member

@bagder bagder commented Jan 15, 2019

.... to not pass in a const in the second argument as that's not how it
is supposed to be used and might cause compiler warnings.

Reported-by: Pavel Pavlov
Fixes #3477

.... to not pass in a const in the second argument as that's not how it
is supposed to be used and might cause compiler warnings.

Reported-by: Pavel Pavlov
Fixes #3477
@jay
Copy link
Member

jay commented Jan 16, 2019

It would be cleaner to use just status.

@bagder
Copy link
Member Author

bagder commented Jan 16, 2019

except that it causes compiler warnings, so it would also require typecasts that I consider are worse than using the approach I did here...

@jay
Copy link
Member

jay commented Jan 16, 2019

Ok. I didn't get any warnings here which is why I suggested it. I've since read the related issue thread and see this discrepancy is covered there. Sorry for the noise.

@bagder bagder closed this in 16a3307 Jan 16, 2019
@bagder bagder deleted the bagder/SSL_get_tlsext_status_ocsp_resp branch January 16, 2019 07:21
@lock lock bot locked as resolved and limited conversation to collaborators Apr 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

SSL_get_tlsext_status_ocsp_resp expects pointer to non-const pointer
2 participants