Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp1109823imm; Fri, 1 Jun 2018 15:47:57 -0700 (PDT) X-Google-Smtp-Source: ADUXVKKNIxAc9D7zE3GEiXIuWjmYCQJO/zf1rj1KRT5z6XjvAcRLJnACfvQ7HAkB5zQDreJikIRA X-Received: by 2002:a17:902:6b44:: with SMTP id g4-v6mr12708669plt.390.1527893276985; Fri, 01 Jun 2018 15:47:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527893276; cv=none; d=google.com; s=arc-20160816; b=KMU9/Z4T4s/I4UmQhvzUoJqyEclz0duHNhPcXjG+VEeO6Vj4Zpes//ShDbLI/lwk/M udUN4AAsTkQriiaWE0Kiqt/5oASUDVU5eu2O7jSlvAVUkCX03JXHE6wRPEzNtVROP0Ah iCOZRcqUDu5xlIDW6FXlBJQeKKQu0pkVfMylib/So3HKbjxquIMRv4YJl5eQJ+4ejHcU HnRU2g0pC+dyLCf86RmS4fEbs3cfR1R1so5jFKBMIpte4LNS6mNSbkF1IO1fE+ja5QDo rRgnEeIXvaGiLgSlgAEF/tWdnRvxCzrg65glA1rxASJoPEQqSKs4Y7mJqicDfDA+YHXk yzCg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date :arc-authentication-results; bh=xgw/22+XHP1N+Qa4zJEOMi+25JgHLPED8hB/esXXjJM=; b=UHYE7nDpd7ppn9BDf6I6vSaR+IzHmek/4divziuxKFaHs1uPVRV+65Aey9n3F5woKx A5QQNNd6EpKnhxRIGgo/iMbj/fbKCaJ/exJFz7+2f0CQ1/3hn16E9BFW1GWTjE3HYllH OB5GCBTX9/bJrglfstTXJ5WkWzygfPxiQVNcgCA+E1mQYgc01c/v/GjRex5XUIrJugoy 9mhNo/SrgNMAPkWJ2BBZAmWYbPb+Y1BgCWNGOi1k1j6kV+vHL8yauyfIKDRL5LIz6UsH TpYgoUfKO7LY7gd07gBa3eHT+QKms7qPCTQUY78m/ECX2ykWRmiADFZNJs8ogRSdjmYc X5rA== 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=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x10-v6si32784497pgo.679.2018.06.01.15.47.41; Fri, 01 Jun 2018 15:47:56 -0700 (PDT) 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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751209AbeFAWqU (ORCPT + 99 others); Fri, 1 Jun 2018 18:46:20 -0400 Received: from mx2.suse.de ([195.135.220.15]:57371 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750750AbeFAWqT (ORCPT ); Fri, 1 Jun 2018 18:46:19 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (charybdis-ext-too.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 078C9AB43; Fri, 1 Jun 2018 22:46:18 +0000 (UTC) Date: Sat, 2 Jun 2018 00:46:17 +0200 From: "Luis R. Rodriguez" To: Mimi Zohar Cc: "Luis R. Rodriguez" , linux-integrity@vger.kernel.org, linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, David Howells , Eric Biederman , kexec@lists.infradead.org, Andres Rodriguez , Greg Kroah-Hartman , Ard Biesheuvel , Matthew Garrett Subject: Re: [PATCH v4 5/8] ima: based on policy require signed firmware (sysfs fallback) Message-ID: <20180601224617.GU4511@wotan.suse.de> References: <1527616920-5415-1-git-send-email-zohar@linux.vnet.ibm.com> <1527616920-5415-6-git-send-email-zohar@linux.vnet.ibm.com> <20180601182107.GO4511@wotan.suse.de> <1527892795.13403.26.camel@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1527892795.13403.26.camel@linux.vnet.ibm.com> User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jun 01, 2018 at 06:39:55PM -0400, Mimi Zohar wrote: > On Fri, 2018-06-01 at 20:21 +0200, Luis R. Rodriguez wrote: > > On Tue, May 29, 2018 at 02:01:57PM -0400, Mimi Zohar wrote: > > > Luis, is the security_kernel_post_read_file LSM hook in > > > firmware_loading_store() still needed after this patch? Should it be > > > calling security_kernel_load_data() instead? > > > > That's up to Kees to decide as he added that hook, and knows > > what LSMs may be doing with it. From my perspective it is confusing > > to have that hook there so I think it could be removed now. > > > > Kees? > > Commit?6593d92 ("firmware_class: perform new LSM checks") references > two methods of loading firmware -??filesystem-found firmware and > demand-loaded blobs. ?I assume this call in firmware_loading_store() > is the demand-loaded blobs. ?Does that method still exist? ?Is it > still being used? Yeah its the stupid sysfs interface. So likely loadpin needs porting as you IMA as you did. Luis