Received: by 2002:a05:6a10:eb17:0:0:0:0 with SMTP id hx23csp542563pxb; Thu, 9 Sep 2021 06:47:27 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxAbSz6IJjyqlNQEKL73H5TK06z2WKOV4MM16i9dzxAMJVePgL4dGEllM8PJrHHy2SevA1z X-Received: by 2002:a02:878f:: with SMTP id t15mr2876254jai.102.1631195247612; Thu, 09 Sep 2021 06:47:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1631195247; cv=none; d=google.com; s=arc-20160816; b=ClEElSJbRxyHm/fOo+pZKv7Vp84HFQsMLe7Guc3busiPj+/I3NBV5DP+ennwF9XG8b TwXEnQaEOOWHX6090GApBivKREVj4FZ0wkUSF9NQbmxbfiwY3RFxHOCpW7wEWuiyHclb YVrHduwEAp4Z/5ElhPPh4POXxUJmdTj6jRAi+WD/axwmCHXH+zLJRYtPviv95GXo38gO gpDflF3Gu9vTf4nHZ64GJxCdN1xmKJ08nMFl9zZpWdqJqk2hJZ7gqLZf97BpgzjNI7Vf yBikRQSt8IK2z2mC7PZUfh7NU6+IU01F6Chur7HyZIwFGYGdB0Douv3OtoHxEGUtmJI0 010Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent :content-transfer-encoding:references:in-reply-to:date:cc:to:from :subject:message-id:dkim-signature; bh=xnCuDc3JCRI1RtgT42GeqGFFWn9OWtLpbTlapHM7JWM=; b=ThUgQQMjHtnOBFg07EZ6ZuAhqn9hy+W0T9a/FcFhnkW5TxeO4GyfxfrvD07V1PfwVT obvb3FYfRROgMECpxhMC8Evb2D06alU4rGvBq6jiG/+ZccK1TLOZRgWKPbOYxJzfUQ/V e/1Ryd1OKscmB04xQCWg//YyXNHt2hxKDlqq02Io1JZaiXx08puB3JiS335Kkp9rglcy dL5Ty+T+e1xfTmrv+0ZHJVlRFDcfxjLminAROenivBlzPPkbAFemgksUUio9rPQ4RmHv b1QZG+Dfk/w+2ftI2lhMECXSl8n9OwVtMjzi2NZplzd0axCoXzb57cXfT1ADZkcgcc5R z16g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=NWE31h3V; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d12si2209817ilg.105.2021.09.09.06.47.07; Thu, 09 Sep 2021 06:47:27 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=NWE31h3V; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1356409AbhIINsC (ORCPT + 99 others); Thu, 9 Sep 2021 09:48:02 -0400 Received: from mail.kernel.org ([198.145.29.99]:58970 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1358439AbhIINpG (ORCPT ); Thu, 9 Sep 2021 09:45:06 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 33A2C6120A; Thu, 9 Sep 2021 13:43:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1631195036; bh=idZqf3ls3/HkHNWsIFzESMREJZQWH8w+Xz30IeQkcbE=; h=Subject:From:To:Cc:Date:In-Reply-To:References:From; b=NWE31h3VqH4BM7wuW7e9UHCznhisydulTuq9bvmjURcQtjv0O5lI547C9kwjpwPM6 Nwo5qP9XoUnwl0R0k4lau7cN9+tVu31smSsqRj22yXFtYwjcUmTEZGumqzNCyAQvH8 ElMcjPRcaC1HuqG8nR+EmRVgqN3ocVRyvkVajLs7nLqvnFnI2OeXUcWCg61//qlMw8 Btemw96tYM/EJjujPexiv5cs568ey4m9PfUf02ZeQylww6bvBZt2KPjfAe+811f7vZ MeFjzPZoTvyIYX6l3bdO1aZgxvN/OpLd2EenEP3Gj6FFzTF0aXFIyqj2jobHJdRmDv sjKoYTOk+/YmA== Message-ID: <82166554e7174b349bf45a7c25d2fcbbc84a4d64.camel@kernel.org> Subject: Re: [PATCH v5 02/12] integrity: Do not allow machine keyring updates following init From: Jarkko Sakkinen To: Eric Snowberg , keyrings@vger.kernel.org, linux-integrity@vger.kernel.org, zohar@linux.ibm.com, dhowells@redhat.com, dwmw2@infradead.org, herbert@gondor.apana.org.au, davem@davemloft.net, jmorris@namei.org, serge@hallyn.com Cc: keescook@chromium.org, gregkh@linuxfoundation.org, torvalds@linux-foundation.org, scott.branden@broadcom.com, weiyongjun1@huawei.com, nayna@linux.ibm.com, ebiggers@google.com, ardb@kernel.org, nramas@linux.microsoft.com, lszubowi@redhat.com, linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org, linux-security-module@vger.kernel.org, James.Bottomley@HansenPartnership.com, pjones@redhat.com, konrad.wilk@oracle.com Date: Thu, 09 Sep 2021 16:43:54 +0300 In-Reply-To: <20210907160110.2699645-3-eric.snowberg@oracle.com> References: <20210907160110.2699645-1-eric.snowberg@oracle.com> <20210907160110.2699645-3-eric.snowberg@oracle.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.36.5-0ubuntu1 MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Tue, 2021-09-07 at 12:01 -0400, Eric Snowberg wrote: > The machine keyring is setup during init. No additional keys should be > allowed to be added afterwards. Leave the permission as read only. >=20 > Signed-off-by: Eric Snowberg > --- > v2: Initial version > v4: Unmodified from v2 > v5: Rename to machine keyring > --- > security/integrity/digsig.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) >=20 > diff --git a/security/integrity/digsig.c b/security/integrity/digsig.c > index 8c315be8ad99..5a75ac2c4dbe 100644 > --- a/security/integrity/digsig.c > +++ b/security/integrity/digsig.c > @@ -140,7 +140,8 @@ int __init integrity_init_keyring(const unsigned int = id) > return -ENOMEM; > =20 > restriction->check =3D restrict_link_to_ima; > - perm |=3D KEY_USR_WRITE; I would add here inline comment to say mostly the same as the commit message does. > + if (id !=3D INTEGRITY_KEYRING_MACHINE) > + perm |=3D KEY_USR_WRITE; > =20 > out: > return __integrity_init_keyring(id, perm, restriction); I checked patch 01 but I lost the email somewhere. The keyring definition looks now sane. /Jarkko