Hello Chris,
Downstream didn't really do anything so far on this topic.
I also can only reproduce this issue on Kernel 5.15 and higher.
I don't know whether setting / as ReadOnly directly or using
ProtectSystem=strict along with PrivateDevices=true,
ProtectKernelTunables=true and
Hello,
These Problems could theoretically come from other settings, yes.
I did use Bullseye for testing this, I don't have any other Debian
systems currently (if you want, I can test it in bookworm or buster
through).
If you want, you can close this Bug Report if you feel this is a weird
Johannes Bülow
https://jmbfountain.de
tories from
being made read-only. This setting is implied if DynamicUser= is set. This
setting cannot ensure protection in all cases. In general it has the same
limitations as ReadOnlyPaths=, see below. Defaults to off.
Regards,
Johannes Bülow
Package: redis-server
Version: 5:6.0.15-1
Severity: normal
Dear Maintainer,
I installed openvas on my kali vm, but redis broke, so I tried to
install redis-server on a clean debian instance, with the same result.
If I disable System Protection and comment out all Read/Write stuff in
the systemd
attached the part of the
syslog below. If you need any more logs, I'll be welcome to provide
them.
Best Regards,
Johannes Bülow
-- System Information:
Debian Release: 11.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux
6 matches
Mail list logo
