get the best and fastest answer
|
|
|
|
Clear questions and runnable code get the best and fastest answer |
|
| PerlMonks |
Re^3: Clues on writing a secure daemonby roju (Friar) |
| on Oct 16, 2004 at 21:20 UTC ( #399823=note: print w/replies, xml ) | Need Help?? |
|
You don't need to run the listener as root.
On startup, you open a pipe. You then fork. Process A drops privs to a junk user like nobody. Process B stays as root and blocks reading the pipe. Process A then listens on the network and performs any work, and then just passes a simple message onto B. B double-checks its input, and if it's good, forks a process as the requested user. The openssh have a good writeup, they call it Privilege Separation.
In Section
Seekers of Perl Wisdom
|
|
||||||||||||||||||||||||