set effective user to root 1575
On Mon, 05 Jun 2006 20:41:44 -0400, Mike - EMAIL IGNORED
Excellent! Concrete requirements. See Unruh's detailed howto on the sgid program, which was what I was trying to drive at.
Linux advocates love to point to Dell as a major company offering Linux as an alternative to...
You're looking at the wrong manpage. That's the setuid system call, not the setuid bit on a file. Although its effects in this case work out to be the same. If root runs a suid program (where suid is to a non-root user), that program cannot switch back to root.
It can, but is overkill. The theory is that you want to give your program the least amount of priviledges possible. That way if your program is compromised in any way, you're minimizing the possible damage.
flatfish+++ Notice that you have the option of getting Windows with, or without, media. Dell has to buy the licenses in bulk. They will probably never sell off the...
Nope... as Unruh has pointed out... chmod g+s TheExt seems to be the best answer (given your constraints).
On 2 Jun 2006, in the Usenet newsgroup comp.os.linux.misc, in article Ahhh... and which cron daemon are...
Oh... one thing that Unruh overlooked... your daemon would need to be started with the appropriate privs as well, so that it may access the file. Offhand I wouldn't suggest even sgid for the daemon. In most cases, daemons are launched by root to begin with, so either you can use some sort of wrapper (start-stop-daemon on Debian for example) which will launch your daemon under the right privs (daemon:DataAccessor... or at least not root....), or your daemon can call setgid explicitly to change what groupID it's running under. Same theory. If your daemon doesn't have root privs anymore, then even it is compromised, it cannot regain root.
Linux groups from Newsgroups