linux-kernel - Re: [PATCH v9 13/25] security: Introduce file

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3b440f064a1ae04d69f7e85f4077f8406c0eac67.camel@huaweicloud.com>
Date: Tue, 16 Jan 2024 09:47:34 +0100
From: Roberto Sassu <roberto.sassu@...weicloud.com>
To: Al Viro <viro@...iv.linux.org.uk>, casey@...aufler-ca.com
Cc: brauner@...nel.org, chuck.lever@...cle.com, jlayton@...nel.org,
 neilb@...e.de,  kolga@...app.com, Dai.Ngo@...cle.com, tom@...pey.com,
 paul@...l-moore.com,  jmorris@...ei.org, serge@...lyn.com,
 zohar@...ux.ibm.com,  dmitry.kasatkin@...il.com, eric.snowberg@...cle.com,
 dhowells@...hat.com,  jarkko@...nel.org, stephen.smalley.work@...il.com,
 eparis@...isplace.org,  shuah@...nel.org, mic@...ikod.net,
 linux-kernel@...r.kernel.org,  linux-fsdevel@...r.kernel.org,
 linux-nfs@...r.kernel.org,  linux-security-module@...r.kernel.org,
 linux-integrity@...r.kernel.org,  keyrings@...r.kernel.org,
 selinux@...r.kernel.org,  linux-kselftest@...r.kernel.org, Roberto Sassu
 <roberto.sassu@...wei.com>
Subject: Re: [PATCH v9 13/25] security: Introduce file_release hook

On Mon, 2024-01-15 at 19:15 +0000, Al Viro wrote:
> On Mon, Jan 15, 2024 at 07:17:57PM +0100, Roberto Sassu wrote:
> > From: Roberto Sassu <roberto.sassu@...wei.com>
> > 
> > In preparation for moving IMA and EVM to the LSM infrastructure, introduce
> > the file_release hook.
> > 
> > IMA calculates at file close the new digest of the file content and writes
> > it to security.ima, so that appraisal at next file access succeeds.
> > 
> > An LSM could implement an exclusive access scheme for files, only allowing
> > access to files that have no references.
> 
> Elaborate that last part, please.

Apologies, I didn't understand that either. Casey?

Thanks

Roberto