Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp2407105ybc; Wed, 13 Nov 2019 14:05:31 -0800 (PST) X-Google-Smtp-Source: APXvYqzzH+WEEoI9kSVyY01q48cW76tOqvz8ElD36ddWSxf0WCw57/zsbuuCeIw3iFsK6LPIgVDn X-Received: by 2002:a17:906:1d02:: with SMTP id n2mr5080577ejh.219.1573682731039; Wed, 13 Nov 2019 14:05:31 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573682731; cv=none; d=google.com; s=arc-20160816; b=Cro0g6O/LrB7+Z7+jemYOyD0XhXAFYIQM0RdpUiLVriSM65oNkKs4Zb0P7jgMSVMsw VbnmRYFUrhwYMai5NiHqWhf9b0Z0T7gHmvMgrSswLoss8lsLp11LrsutTCgjdtzAlVCt TPknTuFW26SyVvDZZzYR6f6P6W91ggUR/xJP26rtOp312KTa0IzAK4a8U1TpnnJOnO5r yYH5xrAfLGYbuHKoF6dJf4/ofqseCKCq6XHtnKOnAc6DQcV3+MdRsnd/26n8iWVqYVb0 O/9rCL1i4VJ2PCsueaAvo3xKCfveFuaH52+WuXF3yHJF6tAunQwyB3HoKhAbjfkrC0Cp celg== 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:to:from:subject; bh=8++//MN9hrpYygUcOQJpu8schrFCJXS0jO3/szSTZEo=; b=kxtyG0HQDC002jVUMOTHLAGlA+C3pv3+QLYqxTO8GVWLntiLT/ceFRw5VNuXRbrAKd Q5i8JkSqGP0g4xQeaBXpB1yYwIW0u0rXFBMsMUGFPBfbIX97ZeDnXjxkPElorqiPYNsa zHZZ6eAsHePgBjFsbWh3Xmjn1E5ooODOOOhaHwKxirm37D6oq3qQJh1Kws1Zn2tVMUT4 dVkOZnrLPDhBiaQUdLKOSliAWLVbN1002mNvK5qvWBGAnp18ZSj8aQMrdaqq1X1X49qi Fc3hGQdTLSW0oCPkz99TuqxlvD5YTonZoR6JpyZbK1IXA1hQy6LI83cWNEJ28QXZqUqI wjSQ== 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 d21si2609744edb.180.2019.11.13.14.05.06; Wed, 13 Nov 2019 14:05:31 -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 S1726986AbfKMWCS (ORCPT + 99 others); Wed, 13 Nov 2019 17:02:18 -0500 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:3588 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726528AbfKMWCS (ORCPT ); Wed, 13 Nov 2019 17:02:18 -0500 Received: from pps.filterd (m0098404.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id xADM19Vo032216 for ; Wed, 13 Nov 2019 17:02:17 -0500 Received: from e06smtp04.uk.ibm.com (e06smtp04.uk.ibm.com [195.75.94.100]) by mx0a-001b2d01.pphosted.com with ESMTP id 2w8t8kr1aj-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Wed, 13 Nov 2019 17:02:16 -0500 Received: from localhost by e06smtp04.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 13 Nov 2019 22:02:13 -0000 Received: from b06cxnps4075.portsmouth.uk.ibm.com (9.149.109.197) 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) Wed, 13 Nov 2019 22:02:10 -0000 Received: from d06av23.portsmouth.uk.ibm.com (d06av23.portsmouth.uk.ibm.com [9.149.105.59]) by b06cxnps4075.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id xADM29Vg57475134 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 13 Nov 2019 22:02:09 GMT Received: from d06av23.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 859DEA4053; Wed, 13 Nov 2019 22:02:09 +0000 (GMT) Received: from d06av23.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 8D6B0A4051; Wed, 13 Nov 2019 22:02:08 +0000 (GMT) Received: from dhcp-9-31-103-201.watson.ibm.com (unknown [9.31.103.201]) by d06av23.portsmouth.uk.ibm.com (Postfix) with ESMTP; Wed, 13 Nov 2019 22:02:08 +0000 (GMT) Subject: Re: [PATCH v6 0/3] KEYS: Measure keys when they are created or updated From: Mimi Zohar To: Lakshmi Ramasubramanian , dhowells@redhat.com, matthewgarrett@google.com, sashal@kernel.org, jamorris@linux.microsoft.com, linux-integrity@vger.kernel.org, linux-security-module@vger.kernel.org, keyrings@vger.kernel.org, linux-kernel@vger.kernel.org Date: Wed, 13 Nov 2019 17:02:08 -0500 In-Reply-To: <20191113184658.2862-1-nramas@linux.microsoft.com> References: <20191113184658.2862-1-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: 7bit X-TM-AS-GCONF: 00 x-cbid: 19111322-0016-0000-0000-000002C36A30 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 19111322-0017-0000-0000-000033250878 Message-Id: <1573682528.4793.3.camel@linux.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-11-13_05:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=3 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1910280000 definitions=main-1911130181 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2019-11-13 at 10:46 -0800, Lakshmi Ramasubramanian wrote: > Keys created or updated in the system are currently not measured. > Therefore an attestation service, for instance, would not be able to > attest whether or not the trusted keys keyring(s), for instance, contain > only known good (trusted) keys. > > IMA measures system files, command line arguments passed to kexec, > boot aggregate, etc. It can be used to measure keys as well. > But there is no mechanism available in the kernel for IMA to > know when a key is created or updated. > > This change aims to address measuring keys created or updated > in the system: > > To achieve the above the following changes have been made: > > - Added a new IMA hook namely, ima_post_key_create_or_update, which > measures the key. This IMA hook is called from key_create_or_update > function. The key measurement can be controlled through IMA policy. > > A new IMA policy function KEY_CHECK has been added to measure keys. > > # measure keys loaded onto any keyring > measure func=KEY_CHECK When re-posting this patch set, please include the support for specifying the "keyrings=" policy option, as an additional patch. Mimi