There are 11 open security issues in forky.
There are 10 open security issues in bookworm.
There are 8 open security issues in bullseye.
commit b32742997d4075e85a3120039e20a28546488e5d
Merge: 1dd7e0f9 d5645fe6
Author: Yves-Alexis Perez <corsac@debian.org>
Date: Sun Sep 13 13:01:29 2026 +0000
Merge branch 'sysusers' into 'debian/master'
Install and use sysusers.d config file
See merge request debian/strongswan!14
commit d5645fe6981bf178776358f548225ee23e79a155
Author: Luca Boccassi <luca.boccassi@gmail.com>
Date: Thu Apr 23 20:00:00 2026 +0100
Install and use sysusers.d config file
sysusers.d config files allow a package to use declarative
configuration instead of manually written maintainer scripts.
This also allows image-based systems to be created with /usr/
only, and also allows for factory resetting a system and
recreating /etc/ on boot.
debhelper already takes care of starting the init script
on install with the generated snippet, so drop the manual
start, to avoid ordering issues with the creation of the
system user.
https://www.freedesktop.org/software/systemd/man/latest/sysusers.d.html
commit 3f12bbc6155934c12e06bb1a94c4480672ee4ede
Author: Luca Boccassi <luca.boccassi@gmail.com>
Date: Thu Apr 23 19:59:19 2026 +0100
Stop deleting system user on remove/purge
This is widely considered bad practice, as the kernel recycles
UIDs/GIDs. So any potential leftover file/directory can then
become owned by the next user/group that gets added, with
unpredictable consequences.
Among the 4 debian patches available in version 6.1.0-2 of the package, we noticed the following issues: