Created attachment 578133 [details] fix for sudo The new sudo includes a backport from 1.7.4 that adds selinux support, but it also includes a change to the way commands parsed that escapes certain characters, including '/' and '.'. The attached patch fixes the problem.
Any idea when this fix is getting rolled into the RHEL5 base repository?
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Is this is a duplicate to bug 806073? Patches are quite different in size.
To be more specific, for this rule: msmith servera01=(svcusr) ALL svcusr servera01=(svcusr2) /bin/bash -c /tmp/command.sh This command used to work: [msmith@servera01]$ sudo -iu svrusr sudo -iu svcusr2 /tmp/command.sh However, now sudo outputs: Sorry, user svrusr is not allowed to execute '/bin/bash -c \/tmp\/command\.sh' as svcusr2 on servera01. After trying many iterations, this rule seems to be an (insecure) workaround: msmith servera01=(svcusr) ALL svcusr servera01=(svcusr2) /bin/bash -c ?/tmp?/command?.sh I've verified this bug exists in sudo-1.7.2p1-14.el5_8, and was introduced in sudo-1.7.2p1-13.el5.
Thanks for the "?/" workaround. I ended up downgrading to sudo-1.7.2p1-10 when I found that "\" and "\\" escapes did't work. I assumed this bug would have been resolved by now, but I guess not.
*** This bug has been marked as a duplicate of bug 806073 ***