FS#45898 - [umurmur] Home directory defaults to non-existent directory

Attached to Project: Community Packages
Opened by Alex W (awh) - Tuesday, 04 August 2015, 21:20 GMT
Last edited by Ivy Foster (escondida) - Thursday, 10 October 2019, 03:52 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Levente Polyak (anthraxx)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
umurmur creates its user with "useradd -r -M -g umurmur -s /bin/false umurmur" - the home directory defaults to /home/umurmur but since it's not being created because of -M, it causes pwck (and shadow.service) to fail. I believe the standard procedure is to add "-d /".
This task depends upon

Closed by  Ivy Foster (escondida)
Thursday, 10 October 2019, 03:52 GMT
Reason for closing:  Implemented
Additional comments about closing:  Current version creates the user with systemd's sysusers, not with useradd, and testing with pwck and shadow.service suggest that this fixed the bug.
Comment by Ben (Clap) - Thursday, 06 October 2016, 19:07 GMT
Here is a patch for package version 0.2.16_a-4 .

The patch changes the following :
- creates the umurmur user and group with id 123 instead of letting the system choose it
- creates umurmur's home directory as /var/db/murmur (with appropriate rights)
- starts umurmur in its home folder so that it can write its ban list there

I chose uid and gid 123 for umurmur because it's not yet used here : https://wiki.archlinux.org/index.php/DeveloperWiki:UID_/_GID_Database
I chose the home location based on murmur's
   umurmur_home.patch (1.6 KiB)
Comment by Ivy Foster (escondida) - Thursday, 10 October 2019, 03:52 GMT
Current umurmur uses systemd's sysusers mechanism to create the user; a quick install and test with "pwck" and "systemctl start shadow" showed no complaints. Seems anthraxx has already fixed this; closing.

Loading...