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

Load legacy openssl provider when buildpack.yml config is set #905

Merged
merged 3 commits into from
Jan 30, 2024

Conversation

sophiewigmore
Copy link
Member

@sophiewigmore sophiewigmore commented Jan 25, 2024

If a user sets the following in their buildpack.yml file:

use_legacy_openssl: true

It will enable the legacy openssl provider to be loaded in via adding an openssl.cnf file to the application workspace with the following content:

[provider_sect]
default = default_sect
legacy = legacy_sect

[default_sect]
activate = 1

[legacy_sect]
activate = 1

This ties in with the change made in this PR: cloudfoundry/cflinuxfs4#11, but will add the openssl.cnf file directly to the workspace without a user needing to add this file themselves.

If a user wants to provide their own openssl.cnf file, that will take precedence over this functionality.

@ForestEckhardt ForestEckhardt merged commit 72b0619 into develop Jan 30, 2024
7 checks passed
@ForestEckhardt ForestEckhardt deleted the openssl-cnf branch January 30, 2024 20:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants