[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: conflict between system user and normal user

previously on this list Simon McVittie contributed:

> > So I'd agree with the underscore but see the not allowing the local
> > sysadmin to create accounts easily with it as a bad thing as they could
> > perfectly well want to avoid collisions with packages as much as a
> > debian dev.  
> A concrete example, please? If you (as local sysadmin) always create
> accounts matching [a-z]*, and Debian packages always create accounts
> matching _*, then your local actions can't collide with Debian packages.

Oops, I guess I read it too fast, sorry for wasting your time. I thought
system accounts were going to get the underscore. Which means the
preventing admin makes more sense but the synergy possibly being the

In any case, before this morning I thought OpenBSD underscored users
were chrooted or something along those lines and it turns out it was the
Absolute OpenBSD book that says they are unpriviledged users which from
taking a look stands up with mysql package/port unpriviledged user also
using underscore. The fact that basically all of the daemons are
unpriviledged is a testament to OpenBSD I guess.

So the mailing list thread I based OpenBSD using underscore for non
base users was wrong despite being made by a usually reliable source
or actually I'm guessing has possibly changed now that basically all
base daemons are unpriviledged.


'Write programs that do one thing and do it well. Write programs to work
together. Write programs to handle text streams, because that is a
universal interface'

(Doug McIlroy)

In Other Words - Don't design like polkit or systemd

Reply to: