-
Notifications
You must be signed in to change notification settings - Fork 127
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
Add support of setting CAPath and relevant test #4982
Add support of setting CAPath and relevant test #4982
Conversation
Thank you for your contribution @phoebusm! We will review the pull request and get back to you soon. |
@microsoft-github-policy-service agree company="Man Group" |
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.
Overall, the changes look good to me, I still have a few nits though.
Thank you so much for the hard work you've put into this PR.
cd41297
to
89b9b3b
Compare
Documentation (https://curl.se/libcurl/c/CURLOPT_CAPATH.html) says it is not supported on Windows. |
@antkmsft Yes only Linux is support. |
c27f923
to
a206ea2
Compare
a206ea2
to
236232e
Compare
It seems discussions are settled and comments are addressed as well. |
@phoebusm Thank you so very much for your contributions. I've signed off on the PR, it looks good to me. |
Thank you everyone for the review and the merge! |
FYI, this change should be available on vcpkg at some time next week with the October release of the Azure SDK. |
Signed-off-by: Julien Jerphanion <[email protected]> Co-authored-by: Phoebus Mak <[email protected]>
@phoebusm could you please share some more details on the scenario where you need this capability? What are you trying to do in your application, and which service are you trying to talk to? |
To hopefully clarify, we are planning to release this change as 1.11.0-beta.1 on Thursday, October 5th. |
#if OPENSSL_VERSION_NUMBER >= 0x00905100L | ||
#define _azure_SUPPORT_SETTING_CAPATH | ||
#endif // OPENSSL_VERSION_NUMBER >= 0x00905100L |
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 am not sure we need this openssl version check.
0x00905100L seems to correspond to 0.9.5 which is 20+ years old. We can assume the version of openssl is 1.1.1 or higher, since we don't support older versions anyway.
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.
Which means we can remove the _azure_SUPPORT_SETTING_CAPATH
and assume this option is available wherever (AZ_PLATFORM_LINUX)
is defined.
Hi I have noticed that azure-core_1.11.0, which has my patch, doesn't get released on 10th Nov. |
Hi @ahsonkhan @antkmsft @LarryOsterman would you please kindly advise when will this patch be released? |
We are hoping to release it in a GA release today, January 11, 2024. |
#4983
Pull Request Checklist
Please leverage this checklist as a reminder to address commonly occurring feedback when submitting a pull request to make sure your PR can be reviewed quickly:
See the detailed list in the contributing guide.