-
Notifications
You must be signed in to change notification settings - Fork 101
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
Protecting from NULL parameters #350
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can confirm this PR addresses the issues I reported,
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM too. Thank you @baentsch !
* guard against possible NULL parameters passed * fix SECURITY status [skip ci] Signed-off-by: Felipe Ventura <felipe.ventura@entrust.com>
* guard against possible NULL parameters passed * fix SECURITY status [skip ci] Signed-off-by: Felipe Ventura <felipe.ventura@entrust.com>
* guard against possible NULL parameters passed * fix SECURITY status [skip ci] Signed-off-by: Felipe Ventura <felipe.ventura@entrust.com>
* guard against possible NULL parameters passed * fix SECURITY status [skip ci] Signed-off-by: Felipe Ventura <felipe.ventura@entrust.com>
* guard against possible NULL parameters passed * fix SECURITY status [skip ci] Signed-off-by: Felipe Ventura <felipe.ventura@entrust.com>
This adds more protections against incorrect use of the OpenSSL<->provider API, notably incorrect NULL pointers passed.
Thanks again to @pcwizz for pointing these out. Please check that the issues found are indeed resolved with this PR.
This PR also updates missing release information in SECURITY.md.