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
This came up during the security review. pack build <trusted-builder> --buildpack <untrusted-buildpack> would allow a malicious buildpack to run in the same container as registry credentials and/or the docker socket.
Proposed solution
If any buildpacks are added (via --buildpack, --extension or project.toml) we should use the untrusted (5 phases) flow. We should probably make an exception for inline buildpacks as these are added directly by the developer.
Describe alternatives you've considered
Additional context
This feature should be documented somewhere
The text was updated successfully, but these errors were encountered:
Description
This came up during the security review.
pack build <trusted-builder> --buildpack <untrusted-buildpack>
would allow a malicious buildpack to run in the same container as registry credentials and/or the docker socket.Proposed solution
If any buildpacks are added (via
--buildpack
,--extension
or project.toml) we should use the untrusted (5 phases) flow. We should probably make an exception for inline buildpacks as these are added directly by the developer.Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: