Bug 14002

Summary: User id 119 has been used for tor user in the past
Product: IPFire Reporter: Stefan Schantl <stefan.schantl>
Component: ---Assignee: Assigned to nobody - feel free to grab it and work on it <nobody>
Status: CLOSED FIXED QA Contact:
Severity: - Unknown -    
Priority: - Unknown - CC: adolf.belka, michael.tremer
Version: 2   
Hardware: unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 13972    

Description Stefan Schantl 2026-06-01 07:24:34 UTC 
The user id 119 which has been choosen for the knot-resolver user and group already has been used for tor in the past.

So one some systems this id is taken and therefore the required user and group for knot-resolver cannot be created and as a result of this the service wont start.

[root@desktop-36784 ~]# getent passwd
root:x:0:0:root:/root:/bin/bash
bin:x:1:1:bin:/bin:/bin/false
daemon:x:2:2:daemon:/sbin:/bin/false
mail:x:8:12:mail:/var/spool/mail:/bin/false
.
.
.
tor:x:119:119:Tor daemon user:/var/empty:/bin/false
.
.
.
unbound:x:103:103:unbound User:/var/empty:/bin/false
Comment 1 Stefan Schantl 2026-06-01 07:31:14 UTC 
The tor user und group with this id will be created during installation of tor.

See:

https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/paks/tor/install.sh;h=369b65f7188083b2a1eaacf39e0d36c30b5fc63d;hb=HEAD
Comment 2 Stefan Schantl 2026-06-01 07:32:07 UTC 
We have to assign a new user and group id for the resolver.
Comment 3 Adolf Belka 2026-06-01 08:05:08 UTC 
I did a grep check on the add-on paks.

There are 7 that use useradd in the install.sh script.

4 of them don't specify a uid/gid

avahi
frr
libvirt
wsdd

tor uses 119
stunnel uses 51
zabbix_agentd uses 118

Another thing to bear in mind is that no users or groups are every removed after they have been created with any of the addons.

I found in my production system

clamav 109
amavis 110
asterix 114

So choice of a new uid/gid for knot-resolver will need to take account of the above.
Comment 6 Michael Tremer 2026-07-20 16:14:17 UTC 
Core Update 203 has been released:

> https://www.ipfire.org/blog/ipfire-2-29-core-update-203-released