Received: by 2002:ac0:8c9a:0:0:0:0:0 with SMTP id r26csp5260367ima; Tue, 5 Feb 2019 08:49:35 -0800 (PST) X-Google-Smtp-Source: AHgI3IYNLtSqii2FFYfPZ+reirFOYvilOJ9LSRC9M4Jjs49l7dRDZnDJTZkc20hAMbqhduvEJ9yp X-Received: by 2002:a62:9f11:: with SMTP id g17mr5902860pfe.222.1549385375588; Tue, 05 Feb 2019 08:49:35 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549385375; cv=none; d=google.com; s=arc-20160816; b=mBFr6rghabS43DxJZHrk/9m4JEhKEHR0CPOVbvXN9kScvFFGRF5fLXE3riUWpMgp/b vJ9hSbP98kE0+D+QmeD62JVkbaVxKSd8Js4VhkDbP+sTdrR99XE6r1yHX2aI+3wZfSiO ElZ9qfrlnMae8RQWdBq8VFYONvT3NNDPqIau4Qh0TnxfmOubdCH9NVsL+hwo+qmWkKmy U4d1yyt4Ea9HR8Ow+eobwRRgepJkWOEmb/+oeUliHN6bLYKTvueMtZudbL2FBKM6Yuoh mhAkZPiOayGLl8M4U4zZgFQl3la5/D2YtpaXngUQ1GA8pbBqgvjB2k0a6NYT0WfL0NNo 2JgA== 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=5FnHPu1aQ6169PkPRqBYY3I6Dm8Q1iU+XSFMs3dqBao=; b=RDl9EkNIdPcdZafv1f9IAfJKGiFNT3EVuER9bqgyr5nqYHlr5eLfLX0xAbLv1phvrt MYssFgPHXhIb6OOWAruYRhfunBIi0v2JvyWLLIif8F2FVYOp7xPUd58GqrPoamn+6/bM dRPrXONA+KzKeGPET1yfZHKpEZ9C30CRG57eIVyPo8G5omboQje9RMTGv8K49ukTvwVb YB7xuKku9+To9kP5XHc8Z7gd3RDNofzmU8sQFWsgZzp7NDoW7TbQoDPGn9HZJqQvte97 7iNVHkNJAeFK0KVqiCAdL8j/JcIOVmNXmfxFR6uJf+pjaXIiXSyOKhhiDyPuAx1OZi0O 8NvA== 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 b60si2646937plc.95.2019.02.05.08.49.19; Tue, 05 Feb 2019 08:49:35 -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 S1729632AbfBEQrp (ORCPT + 99 others); Tue, 5 Feb 2019 11:47:45 -0500 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:53572 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728445AbfBEQro (ORCPT ); Tue, 5 Feb 2019 11:47:44 -0500 Received: from pps.filterd (m0098399.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x15Gjb8C045822 for ; Tue, 5 Feb 2019 11:47:43 -0500 Received: from e06smtp07.uk.ibm.com (e06smtp07.uk.ibm.com [195.75.94.103]) by mx0a-001b2d01.pphosted.com with ESMTP id 2qfe9p03g3-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 05 Feb 2019 11:47:43 -0500 Received: from localhost by e06smtp07.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 5 Feb 2019 16:47:41 -0000 Received: from b06cxnps3075.portsmouth.uk.ibm.com (9.149.109.195) by e06smtp07.uk.ibm.com (192.168.101.137) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Tue, 5 Feb 2019 16:47:37 -0000 Received: from d06av22.portsmouth.uk.ibm.com (d06av22.portsmouth.uk.ibm.com [9.149.105.58]) by b06cxnps3075.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id x15GlaXp49873032 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Tue, 5 Feb 2019 16:47:36 GMT Received: from d06av22.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 98B174C058; Tue, 5 Feb 2019 16:47:36 +0000 (GMT) Received: from d06av22.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 8BBB04C046; Tue, 5 Feb 2019 16:47:35 +0000 (GMT) Received: from localhost.localdomain (unknown [9.80.107.43]) by d06av22.portsmouth.uk.ibm.com (Postfix) with ESMTP; Tue, 5 Feb 2019 16:47:35 +0000 (GMT) Subject: Re: [PATCH] x86/ima: require signed kernel modules From: Mimi Zohar To: Seth Forshee Cc: linux-integrity@vger.kernel.org, linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, Jessica Yu , Luis Chamberlain , David Howells , Justin Forbes , Matthew Garrett Date: Tue, 05 Feb 2019 11:47:24 -0500 In-Reply-To: <20190205151859.GD16362@ubuntu-xps13> References: <1548962339-10681-1-git-send-email-zohar@linux.ibm.com> <1548962339-10681-2-git-send-email-zohar@linux.ibm.com> <20190205151859.GD16362@ubuntu-xps13> 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: 19020516-0028-0000-0000-00000344895B X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 19020516-0029-0000-0000-00002402933B Message-Id: <1549385244.4146.148.camel@linux.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-02-05_07:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 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-1810050000 definitions=main-1902050128 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Seth, On Tue, 2019-02-05 at 09:18 -0600, Seth Forshee wrote: > On Thu, Jan 31, 2019 at 02:18:59PM -0500, Mimi Zohar wrote: > > Require signed kernel modules on systems with secure boot mode enabled. > > > > To coordinate between appended kernel module signatures and IMA > > signatures, only define an IMA MODULE_CHECK policy rule if > > CONFIG_MODULE_SIG is not enabled. > > > > This patch defines a function named set_module_sig_required() and renames > > is_module_sig_enforced() to is_module_sig_enforced_or_required(). The > > call to set_module_sig_required() is dependent on CONFIG_IMA_ARCH_POLICY > > being enabled. > > > > Signed-off-by: Mimi Zohar > > With respect to interactions with the kernel lockdown patches, this > looks better than the patches I saw previously. I don't feel like I know > enough about what's going on with IMA to ack the patch, but I feel > confident that it's at least not going to break signature enforcement > for us. Thank you for testing!  Could this be translated into a "tested-by" "(for w/lockdown patches)"? Mimi