Public bug reported:
i have a bad habit of fiddling with the sudoers file. since the file
comes with 440 permissions, i first sudo chmod 640 on it. while doing
this in hardy i noticed this:
sudo chmod 640 /etc/sudoers would succeed, but then, any command issued
with sudo would give a "/etc/sudoers is mode 0640 instead of 0440". it
wouldnt even let me sudo chmod 440 /etc/sudoers!!!
so i ended up booting to single user mode, doing my usual stuff to the
sudoers file and then taking it back to its usual 0440 mode.
i have always liked ubuntu because it combines simplicity in a lot of
areas which are just plain boring to deal with, while at the same time
not getting in my way in the likes of suse (call me yast) when dealing
with configuration file editing. if we're trying to make it hard to
fiddle the /etc/sudoers, why did the initial chmod 640 succeed? it
doesn't make sense to allow such a change if every following sudo
command will fail complaining about the permissions on that file.
/antonis
notes:
1. im not filing this as a security bug, although i suspect it *could* lead to
denial of service since sudo fails if any sudoer succeeds to change the
permissions of the sudoers file.
2. i suspect this is a problem with the sudo package, but i have been
wrong before...
** Affects: sudo (Ubuntu)
Importance: Undecided
Status: New
--
editing sudoers in hardy
https://bugs.launchpad.net/bugs/192166
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
