[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f9ccc9be6cc084e9cab6cd75e87735492d120002.camel@linux.ibm.com>
Date: Fri, 11 Feb 2022 07:40:53 -0500
From: Mimi Zohar <zohar@...ux.ibm.com>
To: Roberto Sassu <roberto.sassu@...wei.com>, shuah@...nel.org,
ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
kpsingh@...nel.org
Cc: linux-integrity@...r.kernel.org,
linux-security-module@...r.kernel.org,
linux-kselftest@...r.kernel.org, netdev@...r.kernel.org,
bpf@...r.kernel.org, linux-kernel@...r.kernel.org,
Florent Revest <revest@...gle.com>
Subject: Re: [PATCH] ima: Calculate digest in ima_inode_hash() if not
available
Hi Roberto,
On Fri, 2022-02-11 at 11:48 +0100, Roberto Sassu wrote:
> __ima_inode_hash() checks if a digest has been already calculated by
> looking for the integrity_iint_cache structure associated to the passed
> inode.
>
> Users of ima_file_hash() and ima_inode_hash() (e.g. eBPF) might be
> interested in obtaining the information without having to setup an IMA
> policy so that the digest is always available at the time they call one of
> those functions.
Things obviously changed, but the original use case for this interface,
as I recall, was a quick way to determine if a file had been accessed
on the system.
--
thanks,
Mimi
Powered by blists - more mailing lists