Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

How can I prevent a sudoer from editing the /etc/sudoer file?

share|improve this question
What's currently defined for that user in the sudoers file? – Andrew Sep 5 '11 at 7:09
up vote 11 down vote accepted

This depends on how much access you have given people who use sudo. If you have given people sufficient privilege to enable them to use sudo in an unrestricted manner then you pretty much have to trust them.

You can explicitly deny access to the visudo command

sudouser ALL=ALL, !/usr/sbin/visudo


$ sudo visudo
[sudo] password for sudouser:
Sorry, user sudouser is not allowed to execute '/usr/sbin/visudo' as root on host1.lan

however this doesn't stop people from, for example, running a shell and then running visudo

sudo -s

Bingo !

The only other solution is to reduce the scope of people's access via sudo. To do this you would have to analyse their privilege requirements and give them access via sudo to only those commands that they really need by use of command aliases etc.

share|improve this answer
If I understand the OP right, he means he want to restrict an user to edit /etc/sudoers file directly. – quanta Sep 5 '11 at 7:52
The answer is the same either way. Once you give people sufficient access you can't stop them doing whatever they want. – Iain Sep 5 '11 at 7:54
what I have add in /etc/sudoers are: !/bin/texteditor /etc/sudoers and it works, but the messy part is I have to find out all editor that is installed in the system. – regmaster Sep 6 '11 at 7:28
@regmaster: If you allow your sudoers to use sudo -s then they will still be able to edit it because they have a root shell. – Iain Sep 6 '11 at 9:15
@lain I have disable that feature too with adding below line: Cmnd_Alias NSHELLS = /bin/sh, /bin/bash, /sbin/nologin, /bin/tcsh, /bin/csh, /bin/zsh, /bin/ksh Cmnd_Alias NSU = /bin/su username ALL=(ALL) NOPASSWD: ALL, !NSHELLS, !NSU – regmaster Sep 9 '11 at 7:18

Using traditional unix permissions, I think that is hard: as long as you can run any command via sudo that will allow you to do editing[*], then you're kinda screwed.

There are other security models available in Linux, though not so widely deployed and configured; for example, SELinux and AppArmour. You might be able to configure those to restrict access to what you desire.

Starting with a goal of "I want my sudo users to be able to do anything" and then taking away certain privileges is probably a hard way to do things: there are many ways to modify sudoers that don't involve directly editing (for example, replace the mail startup script with a script that i) copies over a new sudoers and then starts sendmail; reboot system; voila!)

In that sense, if you trust your users to do anything to your system, then you have to trust them to do anything to your system (on a technical level, at least).

share|improve this answer
+1 for mentioning both SELinux and AppArmor, it's the only way to go once you've handed the root keys to a user through sudo :) – lynxman Sep 5 '11 at 12:08

Bit clunky, but you could set up another machine to ssh in to your box(es) and alert you if there's a change, or if it can't ssh in. Gives an attacker a small window of opportunity... but is a reduction in risk. Might not solve your particular case at all though.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.