Received-SPF: pass (google.com: domain of linux-kernel+bounces-93502-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
Message-ID: <720e7d0d55c2a22742ede0104fc884609b2f840d.camel@huaweicloud.com>
Subject: Re: [PATCH v2 24/25] commoncap: use vfs fscaps interfaces
From: Roberto Sassu <roberto.sassu@huaweicloud.com>
To: "Seth Forshee (DigitalOcean)" <sforshee@kernel.org>
Cc: Christian Brauner <brauner@kernel.org>, Serge Hallyn <serge@hallyn.com>,
  Paul Moore <paul@paul-moore.com>, Eric Paris <eparis@redhat.com>, James
 Morris <jmorris@namei.org>,  Alexander Viro <viro@zeniv.linux.org.uk>, Jan
 Kara <jack@suse.cz>, Stephen Smalley <stephen.smalley.work@gmail.com>,
 Ondrej Mosnacek <omosnace@redhat.com>,  Casey Schaufler
 <casey@schaufler-ca.com>, Mimi Zohar <zohar@linux.ibm.com>, Roberto Sassu
 <roberto.sassu@huawei.com>,  Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
 Eric Snowberg <eric.snowberg@oracle.com>, "Matthew Wilcox (Oracle)"
 <willy@infradead.org>, Jonathan Corbet <corbet@lwn.net>, Miklos Szeredi
 <miklos@szeredi.hu>, Amir Goldstein <amir73il@gmail.com>, 
 linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, 
 linux-security-module@vger.kernel.org, audit@vger.kernel.org, 
 selinux@vger.kernel.org, linux-integrity@vger.kernel.org, 
 linux-doc@vger.kernel.org, linux-unionfs@vger.kernel.org
Date: Wed, 06 Mar 2024 09:30:54 +0100
In-Reply-To: <Zed91y4MYugjI1/K@do-x1extreme>
References: <20240221-idmap-fscap-refactor-v2-0-3039364623bd@kernel.org>
	 <20240221-idmap-fscap-refactor-v2-24-3039364623bd@kernel.org>
	 <dcbd9e7869d2fcce69546b53851d694b8ebad54e.camel@huaweicloud.com>
	 <ZeXpbOsdRTbLsYe9@do-x1extreme>
	 <a7124afa6bed2fcadcb66efa08e256828cd6f8ab.camel@huaweicloud.com>
	 <ZeX9MRhU/EGhHkCY@do-x1extreme>
	 <20240305-fachjargon-abmontieren-75b1d6c67a83@brauner>
	 <3098aef3e5f924e5717b4ba4a34817d9f22ec479.camel@huaweicloud.com>
	 <7058e2f93d16f910336a5380877b14a2e069ee9d.camel@huaweicloud.com>
	 <Zed91y4MYugjI1/K@do-x1extreme>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.44.4-0ubuntu2 
Precedence: bulk
MIME-Version: 1.0

On Tue, 2024-03-05 at 14:17 -0600, Seth Forshee (DigitalOcean) wrote:
> On Tue, Mar 05, 2024 at 06:11:45PM +0100, Roberto Sassu wrote:
> > On Tue, 2024-03-05 at 13:46 +0100, Roberto Sassu wrote:
> > > On Tue, 2024-03-05 at 10:12 +0100, Christian Brauner wrote:
> > > > On Mon, Mar 04, 2024 at 10:56:17AM -0600, Seth Forshee (DigitalOcea=
n) wrote:
> > > > > On Mon, Mar 04, 2024 at 05:17:57PM +0100, Roberto Sassu wrote:
> > > > > > On Mon, 2024-03-04 at 09:31 -0600, Seth Forshee (DigitalOcean) =
wrote:
> > > > > > > On Mon, Mar 04, 2024 at 11:19:54AM +0100, Roberto Sassu wrote=
:
> > > > > > > > On Wed, 2024-02-21 at 15:24 -0600, Seth Forshee (DigitalOce=
an) wrote:
> > > > > > > > > Use the vfs interfaces for fetching file capabilities for=
 killpriv
> > > > > > > > > checks and from get_vfs_caps_from_disk(). While there, up=
date the
> > > > > > > > > kerneldoc for get_vfs_caps_from_disk() to explain how it =
is different
> > > > > > > > > from vfs_get_fscaps_nosec().
> > > > > > > > >=20
> > > > > > > > > Signed-off-by: Seth Forshee (DigitalOcean) <sforshee@kern=
el.org>
> > > > > > > > > ---
> > > > > > > > >  security/commoncap.c | 30 +++++++++++++-----------------
> > > > > > > > >  1 file changed, 13 insertions(+), 17 deletions(-)
> > > > > > > > >=20
> > > > > > > > > diff --git a/security/commoncap.c b/security/commoncap.c
> > > > > > > > > index a0ff7e6092e0..751bb26a06a6 100644
> > > > > > > > > --- a/security/commoncap.c
> > > > > > > > > +++ b/security/commoncap.c
> > > > > > > > > @@ -296,11 +296,12 @@ int cap_capset(struct cred *new,
> > > > > > > > >   */
> > > > > > > > >  int cap_inode_need_killpriv(struct dentry *dentry)
> > > > > > > > >  {
> > > > > > > > > -	struct inode *inode =3D d_backing_inode(dentry);
> > > > > > > > > +	struct vfs_caps caps;
> > > > > > > > >  	int error;
> > > > > > > > > =20
> > > > > > > > > -	error =3D __vfs_getxattr(dentry, inode, XATTR_NAME_CAPS=
, NULL, 0);
> > > > > > > > > -	return error > 0;
> > > > > > > > > +	/* Use nop_mnt_idmap for no mapping here as mapping is =
unimportant */
> > > > > > > > > +	error =3D vfs_get_fscaps_nosec(&nop_mnt_idmap, dentry, =
&caps);
> > > > > > > > > +	return error =3D=3D 0;
> > > > > > > > >  }
> > > > > > > > > =20
> > > > > > > > >  /**
> > > > > > > > > @@ -323,7 +324,7 @@ int cap_inode_killpriv(struct mnt_idm=
ap *idmap, struct dentry *dentry)
> > > > > > > > >  {
> > > > > > > > >  	int error;
> > > > > > > > > =20
> > > > > > > > > -	error =3D __vfs_removexattr(idmap, dentry, XATTR_NAME_C=
APS);
> > > > > > > > > +	error =3D vfs_remove_fscaps_nosec(idmap, dentry);
> > > > > > > >=20
> > > > > > > > Uhm, I see that the change is logically correct... but the =
original
> > > > > > > > code was not correct, since the EVM post hook is not called=
 (thus the
> > > > > > > > HMAC is broken, or an xattr change is allowed on a portable=
 signature
> > > > > > > > which should be not).
> > > > > > > >=20
> > > > > > > > For completeness, the xattr change on a portable signature =
should not
> > > > > > > > happen in the first place, so cap_inode_killpriv() would no=
t be called.
> > > > > > > > However, since EVM allows same value change, we are here.
> > > > > > >=20
> > > > > > > I really don't understand EVM that well and am pretty hesitan=
t to try an
> > > > > > > change any of the logic around it. But I'll hazard a thought:=
 should EVM
> > > > > > > have a inode_need_killpriv hook which returns an error in thi=
s
> > > > > > > situation?
> > > > > >=20
> > > > > > Uhm, I think it would not work without modifying
> > > > > > security_inode_need_killpriv() and the hook definition.
> > > > > >=20
> > > > > > Since cap_inode_need_killpriv() returns 1, the loop stops and E=
VM would
> > > > > > not be invoked. We would need to continue the loop and let EVM =
know
> > > > > > what is the current return value. Then EVM can reject the chang=
e.
> > > > > >=20
> > > > > > An alternative way would be to detect that actually we are sett=
ing the
> > > > > > same value for inode metadata, and maybe not returning 1 from
> > > > > > cap_inode_need_killpriv().
> > > > > >=20
> > > > > > I would prefer the second, since EVM allows same value change a=
nd we
> > > > > > would have an exception if there are fscaps.
> > > > > >=20
> > > > > > This solves only the case of portable signatures. We would need=
 to
> > > > > > change cap_inode_need_killpriv() anyway to update the HMAC for =
mutable
> > > > > > files.
> > > > >=20
> > > > > I see. In any case this sounds like a matter for a separate patch
> > > > > series.
> > > >=20
> > > > Agreed.
> > >=20
> > > Christian, how realistic is that we don't kill priv if we are setting
> > > the same owner?
> > >=20
> > > Serge, would we be able to replace __vfs_removexattr() (or now
> > > vfs_get_fscaps_nosec()) with a security-equivalent alternative?
> >=20
> > It seems it is not necessary.
> >=20
> > security.capability removal occurs between evm_inode_setattr() and
> > evm_inode_post_setattr(), after the HMAC has been verified and before
> > the new HMAC is recalculated (without security.capability).
> >=20
> > So, all good.
> >=20
> > Christian, Seth, I pushed the kernel and the updated tests (all patches
> > are WIP):
> >=20
> > https://github.com/robertosassu/linux/commits/evm-fscaps-v2/
> >=20
> > https://github.com/robertosassu/ima-evm-utils/commits/evm-fscaps-v2/
> >=20
> >=20
> > The tests are passing:
> >=20
> > https://github.com/robertosassu/ima-evm-utils/actions/runs/8159877004/j=
ob/22305521359
>=20
> Thanks! I probably won't be able to take them exactly as-is due to other
> changes for the next version (rebasing onto the changes to make IMA and
> EVM LSMs, forbidding xattr handlers entirely for fscaps), but they will
> serve as a good road map for what needs to happen.

Welcome. Yes, both ima_inode_set_fscaps() and ima_inode_remove_fscaps()
will be registered as LSM hooks in ima_appraise.c. It will be probably
straightforward for you to make those changes, but if you have any
question, let me know.

Roberto