You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 16, 2022. It is now read-only.
Based on this, it seems like the auto detection is run but it's missing OpenSSL. It should have been though as when I run composer check-platform-reqs locally, it shows openssl as required.
The php.ini snippet generated by the buildpack only has:
extension = fileinfo.so
extension = mbstring.so
My theory is that because openssl is a required extension to run Composer, we enable it in the php.ini that's used to execute composer. Thus when composer check-platform-reqs executes, it sees openssl as already available. This isn't correct though because it's only available in the limited environment where we execute Composer.
I think there's a couple ways that we could fix this:
Always enable the openssl extension. It is quite widely used at this point. I think the risk here is that if we enable it, and there's a security vulnerability then an app that doesn't use it could potentially be vulnerable when it otherwise wouldn't be.
When we check for extensions with composer check-platform-reqs, we normally filter by extensions listed missing. We need to look for both missing or the name openssl. If openssl is listed, it'll never be missing, so we just need to add it to the list of extensions to enable.
What were you attempting to do?
Run an app where openssl is a extension required through Composer.
What did you expect to happen?
The composer extension to be available.
What was the actual behavior? Please provide log output, if possible.
Other extensions were detected correctly, but not openssl.
Build Configuration
What platform (pack, kpack, tekton buildpacks plugin, etc.) are you
using? Please include a version.
Pack.
What buildpacks are you using? Please include versions.
What builder are you using? If custom, can you provide the output from pack inspect-builder <builder>?
full
Can you provide a sample app or relevant configuration (buildpack.yml, nginx.conf, etc.)?
When we check for extensions with composer check-platform-reqs, we normally filter by extensions listed missing. We need to look for both missing or the name openssl. If openssl is listed, it'll never be missing, so we just need to add it to the list of extensions to enable.
What happened?
Create and run the sample app as described in this issue. When deployed, it will not have the openssl extension enabled.
paketo-buildpacks/php#366 (comment)
Based on this, it seems like the auto detection is run but it's missing OpenSSL. It should have been though as when I run
composer check-platform-reqs
locally, it shows openssl as required.The php.ini snippet generated by the buildpack only has:
My theory is that because openssl is a required extension to run Composer, we enable it in the php.ini that's used to execute composer. Thus when
composer check-platform-reqs
executes, it sees openssl as already available. This isn't correct though because it's only available in the limited environment where we execute Composer.I think there's a couple ways that we could fix this:
composer check-platform-reqs
, we normally filter by extensions listed missing. We need to look for both missing or the name openssl. If openssl is listed, it'll never be missing, so we just need to add it to the list of extensions to enable.Run an app where openssl is a extension required through Composer.
The composer extension to be available.
Other extensions were detected correctly, but not openssl.
Build Configuration
pack
,kpack
,tekton
buildpacks plugin, etc.) are youusing? Please include a version.
Pack.
What buildpacks are you using? Please include versions.
What builder are you using? If custom, can you provide the output from
pack inspect-builder <builder>
?full
buildpack.yml
,nginx.conf
, etc.)?paketo-buildpacks/php#366 (comment)
Checklist
The text was updated successfully, but these errors were encountered: