Bug 2189578 - Remove default pre-exec hook directories.
Summary: Remove default pre-exec hook directories.
Keywords:
Status: POST
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.9
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Tom Sweeney
QA Contact: Yuhui Jiang
URL:
Whiteboard:
Depends On:
Blocks: 2189582 2189593
TreeView+ depends on / blocked
 
Reported: 2023-04-25 15:44 UTC by Tom Sweeney
Modified: 2023-08-17 07:29 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2189582 2189593 (view as bug list)
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github containers podman pull 18331 0 None Merged Add file switch for pre-exec hooks 2023-07-04 14:03:00 UTC
Red Hat Issue Tracker RHELPLAN-155743 0 None None None 2023-04-25 15:45:59 UTC

Description Tom Sweeney 2023-04-25 15:44:07 UTC
Description of problem:

Currently, Podman searches the directories /usr/libexec/podman/pre-exec-hooks or /etc/containers/pre-exec-hooks on the host machine, and if there are any scripts in those directories, they are run at the startup of the container.  Per RHEL Security Alert, we should not do this.  Instead, we should use a configurable option to allow this to happen or use an environment variable to specify the directory.

The longer-term fix is to add an option somewhere to allow for those directories to be used.  However, given the ZeroDay deadline, for that release, we will be just using the environment variable: PODMAN_PREEXEC_HOOKS_DIR.  If that EnVar is defined, scripts in the specified directory will be run.  If not specified, any scripts found in the suggested directories: /usr/libexec/podman/pre-exec-hooks or /etc/containers/pre-exec-hooks will not be run at the container startup.  


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:


Note You need to log in before you can comment on or make changes to this bug.