Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-3133

Remove default pre-exec hook directories.

    • None
    • Critical
    • ZStream
    • rhel-sst-container-tools
    • 3
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • If docs needed, set a value
    • None

      +++ This bug was initially created as a clone of Bug #2189578 +++

      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:

              rhn-support-jnovy Jindrich Novy
              tsweeney@redhat.com Tom Sweeney
              Yuhui Jiang Yuhui Jiang
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: