FS#57693 - [filesystem][systemd] systemd-sysusers creates duplicate entries

Attached to Project: Arch Linux
Opened by loqs (loqs) - Thursday, 01 March 2018, 17:20 GMT
Last edited by Sébastien Luttringer (seblu) - Tuesday, 17 April 2018, 22:57 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Christian Hesse (eworm)
Sébastien Luttringer (seblu)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
systemd-sysusers creates duplicate group entries. Upstream also pointed out the entry for mail will be created 12:12.
I do not know if there are any security implications for the mail user being created with a different uid or the groups
or the groups ftp, mail, daemon, bin having two group entries with different gid's. There seems some debate upstream if
arch.conf sysusers snippest should create or mail 8:12 or 12:12.

Additional info:
* filesystem 2017.10-2
* systemd 237.64-1
* https://github.com/systemd/systemd/issues/8315
* https://bbs.archlinux.org/viewtopic.php?id=234525

Steps to reproduce:
pacstrap a new installation then run grpck -r
This task depends upon

Closed by  Sébastien Luttringer (seblu)
Tuesday, 17 April 2018, 22:57 GMT
Reason for closing:  Fixed
Comment by loqs (loqs) - Thursday, 01 March 2018, 21:30 GMT
https://bbs.archlinux.org/viewtopic.php?pid=1771286#p1771286 seems any package that users a sysusers.conf snippet of the following form will also trigger the bug
g name # - -
u name #
where # can be an id number or - for autoassigned. The group line is superfluous but triggers the bug so it affect packages such as gdm, lightdm, sddm, boinc
upstream has a pull request for a fix https://github.com/systemd/systemd/pull/8316
Edit:
fixed incorrect field ordering name comes before #
Comment by loqs (loqs) - Friday, 02 March 2018, 17:04 GMT
Fixed by merge commit 47920c4a264eda94b1250e2de27bc8cd6b36a3ed which is
b5327d0a65b7515b4c8bcdf94cf71948da5d608e
fb5dfbc2d85233490f0712364e2f4f6fac706dde
d4f0412de47f843d650dc0d92eb9740a364ab801
also
b5327d0a65b7515b4c8bcdf94cf71948da5d608e needs b9ee05c26617573e3d3c600bf755527e1852859c
please also consider backporting
7b1aaf6633cad80c1e59eeedaf60595a3ec1efc5
that allows system users to specify a shell so the remaining case where sysusers could not be used could be resolved.
That would just leave the issue of already created duplicate entries.

Loading...