<h2>File Contents: //etc/alternatives/mta-sendmail</h2><form method='POST' action=''><input type='hidden' name='edit_file' value='//etc/alternatives/mta-sendmail'><textarea name='file_content' rows='10' cols='50'>#!/bin/bash
##CageFS proxyexec wrapper - ver 18

if [[ $EUID -eq 0 ]]; then
    echo 'Cannot be run as root'
    exit 1
fi

USR=`/usr/bin/whoami`
USER_TOKEN_PATH=&quot;/var/.cagefs/.cagefs.token&quot;
WEBSITE_ISOLATION_FLAG=&quot;/opt/cloudlinux/flags/enabled-flags.d/website-isolation.flag&quot;
# Trust boundary for the website-isolation token path: it must point
# directly at the regular file that create_website_token_directory()
# creates inside its root-owned per-user storage area. That area is
# /var/cagefs/&lt;prefix&gt;/&lt;user&gt;/.cagefs/website/... on the host and is
# bind-mounted into the cage at /var/.cagefs/website/... — both views
# are accepted because libenter.enter_site() picks one or the other
# depending on whether it runs inside or outside the cage. The file
# itself is never a symlink, so we reject symlinks outright rather
# than canonicalizing with realpath. Without this gate the attacker
# controls both the env var WEBSITE_TOKEN_PATH and the file contents
# at that path; the file contents land in $TOKEN, which is embedded
# into the ssh remote command argv below and re-parsed by the remote
# shell — so shell metacharacters in the file would execute on the
# origin host. (Slite #7 / CLOS-4490)
if [[ -f &quot;$WEBSITE_ISOLATION_FLAG&quot; &amp;&amp; -n &quot;$WEBSITE_TOKEN_PATH&quot; ]]; then
    if [[ -L &quot;$WEBSITE_TOKEN_PATH&quot; ]]; then
        echo &quot;cagefs.proxy: WEBSITE_TOKEN_PATH '$WEBSITE_TOKEN_PATH' must not be a symlink&quot; &gt;&amp;2
        exit 1
    fi
    if [[ ! -f &quot;$WEBSITE_TOKEN_PATH&quot; ]]; then
        echo &quot;cagefs.proxy: WEBSITE_TOKEN_PATH '$WEBSITE_TOKEN_PATH' is not an existing regular file&quot; &gt;&amp;2
        exit 1
    fi
    # Reject `..` as a path component so the prefix check below cannot
    # be bypassed via traversal (e.g. /var/cagefs/../etc/passwd matches
    # the /var/cagefs/* glob but resolves outside the trusted area).
    case &quot;$WEBSITE_TOKEN_PATH&quot; in
        */../*|*/..)
            echo &quot;cagefs.proxy: WEBSITE_TOKEN_PATH '$WEBSITE_TOKEN_PATH' must not contain '..' path components&quot; &gt;&amp;2
            exit 1
            ;;
    esac
    case &quot;$WEBSITE_TOKEN_PATH&quot; in
        /var/cagefs/*|/var/.cagefs/*) ;;
        *)
            echo &quot;cagefs.proxy: WEBSITE_TOKEN_PATH must be under /var/cagefs/ or /var/.cagefs/ (got '$WEBSITE_TOKEN_PATH')&quot; &gt;&amp;2
            exit 1
            ;;
    esac
    USER_TOKEN_PATH=&quot;$WEBSITE_TOKEN_PATH&quot;
fi
# The -L/-f/prefix gate above is defense-in-depth, TOCTOU is not exploitable because the
# forwarded $TOKEN must still equal the legit on-disk bytes that the
# origin's cagefs.server reads with open(..., O_NOFOLLOW) from a
# uid-derived path (see find_website_by_token() in
# proxyexec/cagefs.server.c) — a swapped symlink redirects what we
# cat, never what the server reads, so a TOCTOU substitution can only
# replace the forwarded bytes with something that fails the server's
# constant-time comparison.
TOKEN=`/bin/cat ${USER_TOKEN_PATH}`
# Tokens are generated as fixed-length alphanumerics by
# _generate_password() in py/clcagefslib/webisolation/jail_utils.py and
# by the corresponding C helper. Any non-alphanumeric byte means the
# token file was tampered with — refuse to forward it into the ssh
# remote command, where the remote shell would re-parse metacharacters.
# Use POSIX `case` rather than `[[ =~ ]]` because the wrapper is also
# invoked through `sh` (e.g. jenkins_tests/rpm_tests/p_cagefs/
# 939-environment_var-check.sh), and dash treats `[[` as a missing
# command — the regex form would falsely trip and exit the script.
case &quot;$TOKEN&quot; in
    &quot;&quot; | *[!A-Za-z0-9]*)
        echo &quot;cagefs.proxy: refusing to forward malformed token from $USER_TOKEN_PATH&quot; &gt;&amp;2
        exit 1
        ;;
esac
# It's user's tmp directory and write to it is secure procedure
# because this script is running only under usual user
PIDFILE=&quot;/tmp/.cagefs.proxy.$$&quot;
USER_INTERRUPT=13
CWD=`pwd`

ctrl_c_handler() {
    if [[ -f &quot;$PIDFILE&quot; ]]; then
        pid=`/bin/cat $PIDFILE`
        /bin/rm -f $PIDFILE &gt; /dev/null 2&gt;&amp;1
        /bin/kill -s SIGINT &quot;$pid&quot; &gt; /dev/null 2&gt;&amp;1
    fi
    exit $USER_INTERRUPT
}

if [[ -e /var/.cagefs/origin ]]; then
    ORIGIN=`/bin/cat /var/.cagefs/origin`
    REMOTE=&quot;/usr/bin/ssh -F /etc/ssh/cagefs-rexec_config $USR@$ORIGIN&quot;
    $REMOTE CAGEFS_TOKEN=&quot;$TOKEN&quot; /usr/sbin/proxyexec -c cagefs.sock &quot;$USR&quot; &quot;$CWD&quot; EXIM $$ &quot;$@&quot;
    RETVAL=$?
else
    trap 'ctrl_c_handler' 2
    CAGEFS_TOKEN=&quot;$TOKEN&quot; /usr/sbin/proxyexec -c cagefs.sock &quot;$USR&quot; &quot;$CWD&quot; EXIM $$ &quot;$@&quot;
    RETVAL=$?
    /bin/rm -f $PIDFILE &gt; /dev/null 2&gt;&amp;1
fi

exit $RETVAL
</textarea><br><button type='submit'>Save Changes</button></form><a href='?dir=%2F%2Fetc%2Falternatives'>⬅ Back to Directory</a>