Description of problem: While trying to figure why our (Gluster upstream) test suite failed on Fedora, I found out that sudo on Centos 7 do have the option "always_set_home" activated by default, but Fedora don't, and since, for some reason, our CI use sudo -E, this break on Fedora. Since the comment on the RHEL/Centos file speak of "security implication", I think it would be interesting to keep the 2 of them somehow in sync. However, since that's also supposed to be dealt with "env_reset", it might be something subtle going on. Version-Release number of selected component (if applicable): sudo-1.8.27-1.fc30.x86_64 How reproducible: Each time Steps to Reproduce: 1. run "sudo -E env" on Fedora 2. see that /home is not reset (so /home is not /root 3. run "sudo -E env" on Centos or RHEL 4. see that /home is reset (so HOME=/root ) Actual results: /home is kept as is Expected results: /home shouldn't be kept Additional info:
Yes, we can add that option into fedora default sudoers.
FEDORA-2019-67998e9f7e has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-67998e9f7e
sudo-1.8.28-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-67998e9f7e
sudo-1.8.28-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.