From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755358AbdKMULZ (ORCPT ); Mon, 13 Nov 2017 15:11:25 -0500 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:44902 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755109AbdKMULW (ORCPT ); Mon, 13 Nov 2017 15:11:22 -0500 Subject: Re: [RFC PATCH v2] fw_lockdown: new micro LSM module to prevent loading unsigned firmware From: Mimi Zohar To: "Luis R. Rodriguez" Cc: David Howells , linux-integrity , linux-fsdevel , linux-kernel , Andy Lutomirski , James Bottomley , David Woodhouse , Kyle McMartin , Ben Hutchings , Alan Cox , Greg Kroah-Hartman , Linus Torvalds , Kees Cook , "AKASHI, Takahiro" Date: Mon, 13 Nov 2017 15:11:12 -0500 In-Reply-To: <20171113195154.GE22894@wotan.suse.de> References: <1510573414.3404.109.camel@linux.vnet.ibm.com> <20171113190505.GC22894@wotan.suse.de> <1510601807.3711.16.camel@linux.vnet.ibm.com> <20171113195154.GE22894@wotan.suse.de> 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: 17111320-0020-0000-0000-000003CBD469 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17111320-0021-0000-0000-000042610141 Message-Id: <1510603872.3711.36.camel@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-11-13_11:,, 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 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1711130278 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2017-11-13 at 20:51 +0100, Luis R. Rodriguez wrote: > On Mon, Nov 13, 2017 at 02:36:47PM -0500, Mimi Zohar wrote: > > Huh, I kind of lost you here.  What does "it" refer to in the above > > sentence?  IMA is in the kernel.  So, who does what checks in > > userspace? > > Sorry I thought some checks were done in userspace, given that is clarified, > what I meant is that say a device driver has a signing specification written > out in the driver, should/can IMA use that on the LSM to verify the detached > signature file for the firmware? IMA-appraisal currently supports file signatures as extended attributes.  Thiago Bauermann posted patches for including appended signature support to IMA-appraisal.  If someone is interested in adding detached signature support, they're welcome to do so. > If it can be all done in kernel, it has me wondering if perhaps one option for > IMA might be to do only vetting for these types of checks, where the info and > description to appraise files is all in-kernel. IMA would not be required > for other files. We probably can defer this discussion until it is applicable. Mimi