Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 863319[details]
sesh loginshell argv[0] replacement patch
Description of problem:
/usr/libexec/sesh if called as -sesh by sudo executes the login shell with wrongly replaced argv[0]. The last "/" is replaced with "-", but the rest of the path remains intact. I expect login shell should be called as "-shell", not "/bin-shell".
This can cause unexpected behaviour e.g. in case /bin/zsh which thinks it was called as /bin-zsh, thus runs in sh emulation mode because bin-zsh starts with "b".
Version-Release number of selected component (if applicable):
sudo-1.8.6p3-12.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
1. add
%wheel ALL=(ALL) ROLE=unconfined_r TYPE=unconfined_t NOPASSWD: ALL
to sudoers (this triggers sesh, without selinux context specified sesh isn't involved)
2. # chsh -s /bin/zsh
3. # usermod -G wheel zshuser
4. [zshuser@rhel6]~% sudo -i
Actual results:
only
#
prompt is shown, no zsh specific rc scripts are sourced in sh emulation mode
In strace we see:
execve("/bin/zsh", ["/bin-zsh"], ...
Expected results:
[root@rhel62]~#
prompt is shown, zsh is launched without emulation
In strace we see:
execve("/bin/zsh", ["-zsh"], ...
Additional info:
Reproduces in sudo-1.8.8-1.fc20.x86_64 as well
Patch attached
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2014-1484.html
Created attachment 863319 [details] sesh loginshell argv[0] replacement patch Description of problem: /usr/libexec/sesh if called as -sesh by sudo executes the login shell with wrongly replaced argv[0]. The last "/" is replaced with "-", but the rest of the path remains intact. I expect login shell should be called as "-shell", not "/bin-shell". This can cause unexpected behaviour e.g. in case /bin/zsh which thinks it was called as /bin-zsh, thus runs in sh emulation mode because bin-zsh starts with "b". Version-Release number of selected component (if applicable): sudo-1.8.6p3-12.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. add %wheel ALL=(ALL) ROLE=unconfined_r TYPE=unconfined_t NOPASSWD: ALL to sudoers (this triggers sesh, without selinux context specified sesh isn't involved) 2. # chsh -s /bin/zsh 3. # usermod -G wheel zshuser 4. [zshuser@rhel6]~% sudo -i Actual results: only # prompt is shown, no zsh specific rc scripts are sourced in sh emulation mode In strace we see: execve("/bin/zsh", ["/bin-zsh"], ... Expected results: [root@rhel62]~# prompt is shown, zsh is launched without emulation In strace we see: execve("/bin/zsh", ["-zsh"], ... Additional info: Reproduces in sudo-1.8.8-1.fc20.x86_64 as well Patch attached