Received: by 2002:ac0:8c9a:0:0:0:0:0 with SMTP id r26csp4967274ima; Tue, 5 Feb 2019 04:27:12 -0800 (PST) X-Google-Smtp-Source: AHgI3IaD7SK/cpeHAGMLd1cDlzfSgUe9J0pTZxAD0fguPgD6/RDWNJmGNF1VFdehSdHBh5pUwHwR X-Received: by 2002:a63:f552:: with SMTP id e18mr4348693pgk.239.1549369631949; Tue, 05 Feb 2019 04:27:11 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549369631; cv=none; d=google.com; s=arc-20160816; b=oX+TPQtmclJNlMSXLg+73wmVwAEiq+dNoF1BlCPqA8pBZwlhLAewMvNeFUIkXBZsAd jNxgilchMMj6u/0d79ftVboTsxyuPAy7VLyoQYP6rjpyCl0o/wGy5o3O8CWnmcvv8GQK XDWciHI4NqXUmZw7C1L5lDlLB9PnIfq7jEjntr/hDk5uSWeoVEbQwowJQAQ/yuMcAUdx sxvVWZteq9+KxA7UKknjCyqv4wuf4xJVfLQUMHStuLe8eBKGrX0upjocJ8vnL02KBV10 ATF5LJBUKSObpLQUiI8XlIG7X+PvFROxHh6bUdd3Z6PtfEfI11qU11oJbDbFrGsQg0YE xeQQ== 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=jbzIyOMM9SpASsb6aGPr6g6U9V3I+HoKNpoj/w7J4T0=; b=qYH9dtcipHM5cfhIhQB13qW5DiXLbSYLUzhxprqJ4s6kuaA/eINcU9IzoRKrobbHKy 0w3C/Gd9kX2NiBYcVYHhDPIsNVqW3uDW9/7oElHk+kCDqYPMNhFe0onMLNSlSgOU6Dto JigsmctnKQgQRhWPFnXEyN2RbL4XrkJDWvjzIAhQD5yDSang5PdOj4Rg4rPg+C9uzWDb uQX//PFj0FVqj90gik8c78xTn2IBzpU43MKInJ9+qEMz9PFA6U4FRl6MeIMkS9mW/DOv xN5IrqxAy/sEPcuFj05yQOdhLKVzib40vOwk4zZDa74xknfBEUVmz82kf+Zf0QpOeI4X Dszw== 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 b2si2946539pgh.475.2019.02.05.04.26.56; Tue, 05 Feb 2019 04:27:11 -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 S1728867AbfBEMY6 (ORCPT + 99 others); Tue, 5 Feb 2019 07:24:58 -0500 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:55722 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728809AbfBEMY6 (ORCPT ); Tue, 5 Feb 2019 07:24:58 -0500 Received: from pps.filterd (m0098393.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x15CNcl8141153 for ; Tue, 5 Feb 2019 07:24:57 -0500 Received: from e06smtp07.uk.ibm.com (e06smtp07.uk.ibm.com [195.75.94.103]) by mx0a-001b2d01.pphosted.com with ESMTP id 2qf8q3dep9-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 05 Feb 2019 07:24:57 -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 12:24:54 -0000 Received: from b06cxnps4074.portsmouth.uk.ibm.com (9.149.109.196) 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 12:24:51 -0000 Received: from d06av23.portsmouth.uk.ibm.com (d06av23.portsmouth.uk.ibm.com [9.149.105.59]) by b06cxnps4074.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id x15COpx651970254 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Tue, 5 Feb 2019 12:24:51 GMT Received: from d06av23.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id DCD89A4055; Tue, 5 Feb 2019 12:24:50 +0000 (GMT) Received: from d06av23.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id BE1E0A405D; Tue, 5 Feb 2019 12:24:49 +0000 (GMT) Received: from localhost.localdomain (unknown [9.80.107.43]) by d06av23.portsmouth.uk.ibm.com (Postfix) with ESMTP; Tue, 5 Feb 2019 12:24:49 +0000 (GMT) Subject: Re: [PATCH] x86/ima: require signed kernel modules From: Mimi Zohar To: Luis Chamberlain Cc: linux-integrity@vger.kernel.org, linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, Jessica Yu , David Howells , Seth Forshee , Justin Forbes , Matthew Garrett Date: Tue, 05 Feb 2019 07:24:39 -0500 In-Reply-To: <20190204223026.GR11489@garbanzo.do-not-panic.com> References: <1548962339-10681-1-git-send-email-zohar@linux.ibm.com> <1548962339-10681-2-git-send-email-zohar@linux.ibm.com> <20190204203850.GP11489@garbanzo.do-not-panic.com> <1549317910.4146.124.camel@linux.ibm.com> <20190204223026.GR11489@garbanzo.do-not-panic.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: 19020512-0028-0000-0000-000003446B75 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 19020512-0029-0000-0000-000024027421 Message-Id: <1549369479.4146.142.camel@linux.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-02-05_05:,, 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-1902050098 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2019-02-04 at 14:30 -0800, Luis Chamberlain wrote: > On Mon, Feb 04, 2019 at 05:05:10PM -0500, Mimi Zohar wrote: > > On Mon, 2019-02-04 at 12:38 -0800, Luis Chamberlain wrote: > > I don't see a need for an additional LSM just for verifying kernel > > module signatures. > > But it is one, module signing was just spawned pre the boom of LSMs. > > I do believe that treating the code as such would help with its reading > and long term maintenance. > > Anyway, I had to try to convince you. Perhaps, after IMA supports appended signatures (for kernel modules), I could see making the existing kernel module appended signature verification an LSM. For now, other than updating the comment, would you be willing to add your Review/Ack to this patch? Mimi