[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <do66st3vh2bg5beq4b3s22djn7kdtdp563grttfzmo64suegzb@k3lj3wu4cf3p>
Date: Tue, 25 Nov 2025 11:00:00 +0100
From: Nicolas Bouchinet <nicolas.bouchinet@....cyber.gouv.fr>
To: Xiujianfeng <xiujianfeng@...weicloud.com>
Cc: Daniel Tang <danielzgtg.opensource@...il.com>,
Xiu Jianfeng <xiujianfeng@...wei.com>, Paul Moore <paul@...l-moore.com>,
linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org,
Nathan Lynch <nathanl@...ux.ibm.com>, Matthew Garrett <mjg59@...gle.com>,
Kees Cook <keescook@...omium.org>, David Howells <dhowells@...hat.com>,
James Morris <jmorris@...ei.org>
Subject: Re: [PATCH v2] lockdown: Only log restrictions once
Hi,
> Currently lockdown does not support the audit function, so I believe the
> logs here serve a purpose similar to auditing. Based on this, I think
> this change will meaningfully degrade the quality of the logs, making it
> hard for users to find out what happens when lockdown is active,
> especially after a long time running.
I agree with Xiu.
I'm not sure to understand how this is a kernel issue. I mean beside
that we do not support hibernation in Lockdown for now.
Can't you just disable hibernation with systemd-logind using someting like
'AllowHibernation=no' ?
Best regards,
Nicolas
Powered by blists - more mailing lists