-
Notifications
You must be signed in to change notification settings - Fork 27
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 OpenSSL 3.3.0 #525
add OpenSSL 3.3.0 #525
Conversation
Reopening as part or https://datadoghq.atlassian.net/browse/BARX-389 |
0488353
to
ff8950d
Compare
Waiting for https://gitlab.ddbuild.io/DataDog/datadog-agent/-/pipelines/38678816 to complete before merging |
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, since it is approved, I will just add an question.
Since we will be looking into the openSSL with the FIPS provider. Will these changes be possible to accommodate a more custom openssl build as proposed in here
config/software/openssl3.rb
Outdated
@@ -89,8 +90,6 @@ | |||
|
|||
command configure_command, env: env, in_msys_bash: true | |||
|
|||
patch source: "openssl-3.0.9-do-not-build-docs.patch", env: env |
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.
What is the reasoning for this removal?
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 haven't checked but I suppose the patch doesn't apply anymore. I will double check
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't see an obvious reason not to apply the patch, I restored it and will check the pipeline
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 assumed openssl's Makefile was versionned but it isn't 🤦 I opened a new PR to have the same behavior regardless of the openssl version and will rebase this PR on top of it
ff8950d
to
939a472
Compare
It will not be an issue, we can still select a different version that the default and add new configure arguments as required. Although the simplest approach might be to add a new software definition that would stick to the FIPS validated branch, build as usual, and copy the 2 files that are needed for FIPS |
939a472
to
3bd32d1
Compare
3bd32d1
to
2911e48
Compare
No description provided.