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_strcasecmp build, cleanup, and initialization fixes #18282
Conversation
It also allows for passing -DOPENSSL_NO_LOCALE as a workaround to ./Configure command. Fixes openssl#18233
Otherwise the implementation is unnecessarily duplicated in legacy.so.
a504e44
to
07c3248
Compare
07c3248
to
2456d53
Compare
I like this approach. And you managed to deduplicate the initialization (failed by me). I'm not sure that TANDEM fix isn't worth a separate PR, BTW I'll make a more thorough review when tests are passed. |
Considering this PR is to fix the breakage originally introduced, it might be a bit of overkill. However, if needed, I can put the PR together once this is merged. We are unable to move our CI forward without both, however, which continues to fail on |
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.
One small fixup pushed @beldmit @paulidale still OK? |
Still LGTM |
Don't need to reset the timer, I think |
I launched a build/test cycle for this branch and will report back when done. |
Is this PR based on the |
Still good. |
24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set. Please review the updates and set the label manually. |
@@ -498,6 +484,9 @@ int OPENSSL_init_crypto(uint64_t opts, const OPENSSL_INIT_SETTINGS *settings) | |||
aloaddone = 1; | |||
} | |||
|
|||
if (!ossl_init_casecmp()) |
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.
Kind of wondering about the need for this. Why not let it lazily init itself? This will simplify things a little.
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 prefer explicit initialization to lazy one. I want to keep it.
Merged to master branch. Thank you for your reviews. |
Reviewed-by: Dmitry Belyavskiy <beldmit@gmail.com> Reviewed-by: Paul Dale <pauli@openssl.org> (Merged from #18282)
Otherwise the implementation is unnecessarily duplicated in legacy.so. Reviewed-by: Dmitry Belyavskiy <beldmit@gmail.com> Reviewed-by: Paul Dale <pauli@openssl.org> (Merged from #18282)
Reviewed-by: Dmitry Belyavskiy <beldmit@gmail.com> Reviewed-by: Paul Dale <pauli@openssl.org> (Merged from #18282)
Reviewed-by: Dmitry Belyavskiy <beldmit@gmail.com> Reviewed-by: Paul Dale <pauli@openssl.org> (Merged from #18282)
This PR encompasses cleanups, build, and initialization fixes for the OPENSSL_strcasecmp related fix.
I recommend reviewing by individual commits.
We will need similar PR for 3.0 but that will require some backporting effort because the patches won't apply cleanly. In the end however the final state on 3.0 should be exactly the same.