On Mon, 10.07.17 18:36, Lennart Poettering (lenn...@poettering.net) wrote: > > After all (as other people said) systemd has no such requirements > > itself. It is true that such user names are confusing and > > non-portable, but if the local admin has or wants to have such an > > account for whatever reason, we don't really care. > > I don't think things are that simple. We do our user name validation > in two places: for User=/Group= and for sysusers.d drop-ins. In both > cases the setting may have the effect of registering users in the > system user database (in the first case if DynamicUser= is used, in > the latter case if the user doesn't exist yet), and I am pretty sure > we shouldn't register users in the system user databases that aren't > portable.
Or to say this differently: User=/Group=/sysusers.d shouldn't be something you can create users with that for example ArchLinux' useradd command wouldn't allow you to create. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
