Hmm.. i admit, i should've read the comments in the file i was editing.
But just a suggestion; you could have sudo keep a backup copy of the last known
good for /etc/sudoers.
If it detects a corrupt /etc/sudoers, it tells you it's using the backup (and
it's location).
That way, i as an app code
Thanks for opening this bug.
You should edit the sudoers file with the "visudo" command. That way, a
parsing error won't lock yourself out.
Closing this bug as per your last comment.
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
** Changed in: ub
