We recently encountered an issue in the .NET Core buildpack (related to https://github.com/dotnet/runtime/issues/67353) in which due to an out-of-date gss-ntlm package in Ubuntu 22.04, certain NTLM-related behaviour fails because it is not compatible with Openssl 3. The workaround (unless Canonical upgrades gss-ntlm) involves modifying the openssl.cnf file to rollback Openssl provider settings.
This PR adds an include path to the openssl.cnf file so that users can provide their own openssl.cnf file in their application directory to modify openssl settings
We recently encountered an issue in the .NET Core buildpack (related to https://github.com/dotnet/runtime/issues/67353) in which due to an out-of-date
gss-ntlmpackage in Ubuntu 22.04, certain NTLM-related behaviour fails because it is not compatible with Openssl 3. The workaround (unless Canonical upgrades gss-ntlm) involves modifying theopenssl.cnffile to rollback Openssl provider settings.We have seen other instances where a user being able to modify the Openssl configuration would be useful: https://github.com/cloudfoundry/dotnet-core-buildpack/issues/567
This PR adds an
includepath to theopenssl.cnffile so that users can provide their ownopenssl.cnffile in their application directory to modify openssl settings