Skip to content
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

Merged
merged 1 commit into from
Jul 12, 2024
Merged

add OpenSSL 3.3.0 #525

merged 1 commit into from
Jul 12, 2024

Conversation

Kyle-Neale
Copy link

No description provided.

@Kyle-Neale Kyle-Neale closed this Jun 5, 2024
@chouquette
Copy link

chouquette commented Jul 9, 2024

Reopening as part or https://datadoghq.atlassian.net/browse/BARX-389

@chouquette chouquette reopened this Jul 9, 2024
@chouquette chouquette force-pushed the kyleneale/openssl_3.3.0 branch from 0488353 to ff8950d Compare July 9, 2024 09:15
@chouquette chouquette marked this pull request as ready for review July 9, 2024 09:20
@chouquette chouquette requested a review from a team as a code owner July 9, 2024 09:20
@chouquette
Copy link

Waiting for https://gitlab.ddbuild.io/DataDog/datadog-agent/-/pipelines/38678816 to complete before merging

Copy link

@f4usto f4usto left a 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

@@ -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
Copy link

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?

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

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

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

@chouquette chouquette force-pushed the kyleneale/openssl_3.3.0 branch from ff8950d to 939a472 Compare July 9, 2024 11:38
@chouquette
Copy link

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

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

@chouquette chouquette force-pushed the kyleneale/openssl_3.3.0 branch from 939a472 to 3bd32d1 Compare July 9, 2024 12:41
@chouquette chouquette changed the base branch from master to chouquette/use_sed_openssl July 9, 2024 12:42
Base automatically changed from chouquette/use_sed_openssl to master July 12, 2024 11:48
@chouquette chouquette force-pushed the kyleneale/openssl_3.3.0 branch from 3bd32d1 to 2911e48 Compare July 12, 2024 11:50
@chouquette chouquette merged commit e78ed89 into master Jul 12, 2024
4 checks passed
@chouquette chouquette deleted the kyleneale/openssl_3.3.0 branch July 12, 2024 14:19
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.

4 participants