Skip to content

Fix with newer LibreSSL #528

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

Merged
merged 2 commits into from
Apr 5, 2022
Merged

Fix with newer LibreSSL #528

merged 2 commits into from
Apr 5, 2022

Conversation

gahr
Copy link
Contributor

@gahr gahr commented Mar 29, 2022

I'm not totally positive I picked the right version number.

I'm not totally positive I picked the right version number.
@absurdfarce
Copy link
Collaborator

Thanks for the contribution @gahr!

After a bit of code spelunking it looks like SSL_CTX_clear_chain_certs was introduced in 2.9.1 by way of this commit. If that's the case I believe the version number we want in our check would be "0x2090100fL" (based on the opensslv.h in 2.9.1). Are you able to verify that your application works correctly with that code in place?

@absurdfarce absurdfarce self-requested a review April 1, 2022 18:33
@gahr
Copy link
Contributor Author

gahr commented Apr 2, 2022

Hi @absurdfarce, yup that looks correct, thanks for double checking. What I wasn't able to properly figure out is when the struct became opaque. We might have an interval between when that happened and when the new API became available. Hopefully nobody is using a libressl version older then 2.9.1, which came out 3 years ago :)

So, yes, a check on 2.9.1 works fine to me.

@absurdfarce
Copy link
Collaborator

Makes sense @gahr. I'm okay with the change since it certainly makes our LibreSSL support more correct than it was. We can always refine this check if we see issues with LibreSSL versions in the interval you describe.

If you can apply the change I suggested I think we're almost there. I'm looking into the issues around the build failure on Jenkins; I'll see if there's an easy fix there as well.

@absurdfarce
Copy link
Collaborator

@gahr Jenkins build failures were just a formatting issue. I've updated my suggested change to include a formatting fix which should address that issue as well. If you're good with the changes there just accept them and we'll see if the resulting build is green again. :)

Co-authored-by: Bret McGuire <absurdfarce@users.noreply.github.com>
@gahr
Copy link
Contributor Author

gahr commented Apr 5, 2022

Thanks!

@absurdfarce
Copy link
Collaborator

Thank you @gahr! Looks like we're all set here!

@absurdfarce absurdfarce merged commit 3f480db into datastax:master Apr 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants