-
Notifications
You must be signed in to change notification settings - Fork 834
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
fix bad & statement that was setting ocspSendNonce #6627
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.
Please share steps to reproduce and make sure we have test coverage.
Originally,
When it was moved and refactored in , it looks like a logical error was made and
which sets Anyways, all we need to do is change it to |
The current code works for me:
|
Test code: This is backwards, right? |
yes it's backwards, when it's set the result should be zero, not 1 |
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.
Confirmed backwards logic is correctly fixed with this. Thanks @jpbland1
retest this please |
to 1 when WOLFSSL_OCSP_NO_NONCE was selected related to but doesn't solve zd 16377
ee81f92
to
a9c9662
Compare
retest this please |
to 1 when WOLFSSL_OCSP_NO_NONCE was selected
related to but doesn't solve zd 16377
Description
OCSP sends an optional nonce which is supposed to be disabled by
WOLFSSL_OCSP_NO_NONCE
but the logical statement was doing the opposite and sending the nonce whenWOLFSSL_OCSP_NO_NONCE
was setTesting
Tested in gdb to confirm the nonce was being skipped
Checklist