3 ms·
Not a good idea to hardcode the name of the "owner". Standard practice is to setuid/gid to 65535 (nobody).
by Hello71 14y ago
Not a good idea to hardcode the name of the "owner". Standard practice is to setuid/gid to 65535 (nobody).
- zorked 14y agoActually, even in the classical Unix security model, setuid'ing to nobody is considered a bad idea. Because so many services do it, giving an attacker an opportunity to become nobody will likely grant him access to those other services as well.
- Hello71 14y agoPoint taken. Allow me to revise my statement. "In production, one should create a specialized user to run any service." And if you have lots of money to waste, stick 'em all in separate VMs too.