note 61873 deleted from function.exec by danbrown

Note Submitter: hanno at theuprightape dot net ---- (quoting rassehund) "Just find sudoers in your system and add there rights to NOBODY." This is, of course, a MAJOR security risk. You don't need sudo if you use it like that, you might just as well change permissions for all commands and paths. For remote server administration, if I don't use ssh, I would let root run cronjobs that look at configuration parameters which were set using a web interface, preferrably using a database (for comfort) and input checks (for security). The logging/status/statistical information that the cronjobs produce are also made available via a web interface. That way, you don't have to perforate your security mechanisms. And one more personal opinion: sudo isn't that safe anyway: ever tried "sudo bash" or "sudo vi"? I would avoid using it, if you get groups and permissions right, you are not going to need it.