Load legacy openssl provider when buildpack.yml config is set #905
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If a user sets the following in their
buildpack.yml
file: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: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.