Bug#1074789: [Pkg-utopia-maintainers] Bug#1074789: polkitd: setup uses non-failsafe manner of checking whether user/group exists
Luca Boccassi
bluca at debian.org
Wed Jul 3 22:58:33 BST 2024
On Wed, 3 Jul 2024 21:26:36 +0200 Michael Biebl <biebl at debian.org>
wrote:
> Am 03.07.24 um 21:00 schrieb Lionel Élie Mamane:
> > On Wed, Jul 03, 2024 at 07:25:15PM +0200, Michael Biebl wrote:
> >
> >>>>> connect(5, {sa_family=AF_UNIX,
sun_path="/run/systemd/userdb/io.systemd.DynamicUser"}, 45) = -1
ECONNREFUSED (Connection refused)
> >
> >> systemd should be listening on this socket
> >
> > Well, on no less than four different Debian machines, it does not.
> >
> >> $ sudo lsof /run/systemd/userdb/io.systemd.DynamicUser
> >> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
> >> systemd 1 root 28u unix 0x0000000073ac41e2 0t0 8696
> >> /run/systemd/userdb/io.systemd.DynamicUser type=STREAM (LISTEN)
> >
> > Isn't that on a machine where systemd-userdb is installed maybe?
The
> > installation of that package triggers the systemd binary to listen?
>
> No, systemd-userdb is not installed and as you can see from the above
> output it's actually systemd which listens on that socket.
I can reproduce it by mounting a tmpfs on /run/systemd/userdb/ _and_
creating an empty io.systemd.DynamicUser file on it. Maybe it should
not abort like that, however, if you have the directory in /run/ _and_
the socket file exists _but_ nothing is listening on it, then your
machine is broken in some way. If the directory/socket are missing they
are just skipped gracefully.
--
Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20240703/ce9f68ed/attachment-0001.sig>
More information about the Pkg-systemd-maintainers
mailing list