Public bug reported:
Ubuntu 16.04 Amazon AWS image.
sudo:
Installed: 1.8.16-0ubuntu1.5
Used sudo visudo to edit /etc/sudoers file from the ubutntu admin user
At the bottom of the file is a line
#includedir /etc/sudoers.d
I added a couple of lines at the end of the file to give permissions to
another user. I accidentally hit backspace and altered the includedir
line so it looked like this
#includedir /etc/sudoercs
I couldn't remember what the actual directory was at the time, but I
thought, hey, its a commented line, it doesn't matter anyway. I was
wrong.
So visudo saved the file OK, but from then on, no valid sudo commands
would work for any user. Including sudo visudo of course. Its an AWS
instance, so no root login. Only recourse was to detach the volume, re-
attach it to another instance, fix the spelling mistake.
So obviously sudo freaked when the directory given didn't exist. But why
would it, if the line is a comment? Something obviously wrong here. And
given the lack of root, a particularly irritating and time consuming
one.
** Affects: sudo (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741398
Title:
Commented line in sudoers file breaks sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1741398/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
