Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp1260897ybl; Tue, 3 Dec 2019 04:27:46 -0800 (PST) X-Google-Smtp-Source: APXvYqykDQYDzPvP62i73TqFYFUvQMacg4gtGly+y7MuX2+DGVYMgGAX+CqvKP7X8FaOzPvkgbLU X-Received: by 2002:aca:fc07:: with SMTP id a7mr3483681oii.28.1575376065940; Tue, 03 Dec 2019 04:27:45 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575376065; cv=none; d=google.com; s=arc-20160816; b=UIZ5MGyGh1klSg9vX27XqWeZMVIcyLxY+ZCCvLGJzB7QK6kaKeAHKRQ/jx3fnjpabu 3HK+0aMP8PXiwEo5kc3ZJU8a3S5bGFc27vTNYDuMkGFnu6P/xFKQGF9onYAZLiTJEDPT Vh0/AY5ajpBCZ/vcDaPUO5/Zppf/kbb23QQjm6r86HnyLY2eEa1bkmLZ37JYD2plu8IJ ij1eq89gdjr27oUg4eI7pd7oArw0z46f8/HcCjyNKJR7WR5rFtXUa17nL4Sq+PKZRrws 6yhKOZ2coeqtz4sb8lNzehR9I9lIbFEQT7cug5DAy0zYhJDKOT5m82JNZGL3dXEnkqYO Xysg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:content-transfer-encoding :mime-version:references:in-reply-to:date:cc:to:from:subject; bh=qZeGLxLXC0UKmTe2OWnO8C+eaqRnCVdnHvmxULNpNH8=; b=b1xCVW8j65G7w2byWBpZp4UlbkFCAXdP9VEpVok8dzYpKZ9lJ3LVsobbTsfvDldzXa SjUE82o5JHNF22HHmYLp1Ve2fuAfMrKIz564W66ILLzD8J4HiZjU7lD2IXTDRcSaQqMW h5CrLLZEPj7Fvh89EiidiGUsjuWTZIPK9uK3cQohSYmn+HOIxjRPBg7qsuRoLZ8noout +6NMdbpezwWVKEFHtfaDP3TurZB2Fde9PaLDmx+SK65pn54ubr9N1jyuvwVBcOWZZCtH 3Z03Ak+w1fOP3LdSzzXOLBLNqXqnKzJFLVrywtUxxGOFDmjn3s8KcZBAHok+EaxkK2bv s0/A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m24si1108470otn.67.2019.12.03.04.27.34; Tue, 03 Dec 2019 04:27:45 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726254AbfLCMZ4 (ORCPT + 99 others); Tue, 3 Dec 2019 07:25:56 -0500 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:59962 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725907AbfLCMZ4 (ORCPT ); Tue, 3 Dec 2019 07:25:56 -0500 Received: from pps.filterd (m0098420.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id xB3CMvdF170787 for ; Tue, 3 Dec 2019 07:25:52 -0500 Received: from e06smtp04.uk.ibm.com (e06smtp04.uk.ibm.com [195.75.94.100]) by mx0b-001b2d01.pphosted.com with ESMTP id 2wnp8rcbn3-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 03 Dec 2019 07:25:52 -0500 Received: from localhost by e06smtp04.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 3 Dec 2019 12:25:50 -0000 Received: from b06avi18626390.portsmouth.uk.ibm.com (9.149.26.192) by e06smtp04.uk.ibm.com (192.168.101.134) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Tue, 3 Dec 2019 12:25:48 -0000 Received: from d06av23.portsmouth.uk.ibm.com (d06av23.portsmouth.uk.ibm.com [9.149.105.59]) by b06avi18626390.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id xB3CP7YJ49611108 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 3 Dec 2019 12:25:07 GMT Received: from d06av23.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 50C9DA4055; Tue, 3 Dec 2019 12:25:47 +0000 (GMT) Received: from d06av23.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 49AC7A4051; Tue, 3 Dec 2019 12:25:46 +0000 (GMT) Received: from localhost.localdomain (unknown [9.85.191.79]) by d06av23.portsmouth.uk.ibm.com (Postfix) with ESMTP; Tue, 3 Dec 2019 12:25:46 +0000 (GMT) Subject: Re: [PATCH v9 5/6] IMA: Add support to limit measuring keys From: Mimi Zohar To: Lakshmi Ramasubramanian , linux-integrity@vger.kernel.org Cc: eric.snowberg@oracle.com, dhowells@redhat.com, matthewgarrett@google.com, sashal@kernel.org, jamorris@linux.microsoft.com, linux-kernel@vger.kernel.org, keyrings@vger.kernel.org Date: Tue, 03 Dec 2019 07:25:45 -0500 In-Reply-To: <20191127015654.3744-6-nramas@linux.microsoft.com> References: <20191127015654.3744-1-nramas@linux.microsoft.com> <20191127015654.3744-6-nramas@linux.microsoft.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.20.5 (3.20.5-1.fc24) Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-TM-AS-GCONF: 00 x-cbid: 19120312-0016-0000-0000-000002D0578F X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 19120312-0017-0000-0000-0000333250B9 Message-Id: <1575375945.5241.16.camel@linux.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572 definitions=2019-12-03_02:2019-12-02,2019-12-03 signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 mlxlogscore=732 suspectscore=0 clxscore=1015 impostorscore=0 bulkscore=0 adultscore=0 spamscore=0 phishscore=0 mlxscore=0 malwarescore=0 lowpriorityscore=0 priorityscore=1501 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000 definitions=main-1912030098 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Lakshmi, On Tue, 2019-11-26 at 17:56 -0800, Lakshmi Ramasubramanian wrote: > Limit measuring keys to those keys being loaded onto a given set of > keyrings only. > > This patch defines a new IMA policy option namely "keyrings=" that > can be used to specify a set of keyrings. If this option is specified > in the policy for "measure func=KEY_CHECK" then only the keys > loaded onto a keyring given in the "keyrings=" option are measured. > > Added a new parameter namely "keyring" (name of the keyring) to > process_buffer_measurement(). The keyring name is passed to > ima_get_action() to determine the required action. > ima_match_rules() is updated to check keyring in the policy, if > specified, for KEY_CHECK function. > > Signed-off-by: Lakshmi Ramasubramanian A keyring can be created by any user with any keyring name, other than  ones dot prefixed, which are limited to the trusted builtin keyrings.  With a policy of "func=KEY_CHECK template=ima-buf keyrings=foo", for example, keys loaded onto any keyring named "foo" will be measured.  For files, the IMA policy may be constrained to a particular uid/gid.  An additional method of identifying or constraining keyring names needs to be defined. Mimi