From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932493AbdJZOvt (ORCPT ); Thu, 26 Oct 2017 10:51:49 -0400 Received: from mx1.redhat.com ([209.132.183.28]:59446 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932275AbdJZOvq (ORCPT ); Thu, 26 Oct 2017 10:51:46 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 603A6356C0 Authentication-Results: ext-mx06.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx06.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=dhowells@redhat.com Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: <1508774083.3639.124.camel@linux.vnet.ibm.com> References: <1508774083.3639.124.camel@linux.vnet.ibm.com> <150842463163.7923.11081723749106843698.stgit@warthog.procyon.org.uk> <150842468754.7923.10037578333644594134.stgit@warthog.procyon.org.uk> To: Mimi Zohar Cc: dhowells@redhat.com, linux-security-module@vger.kernel.org, gnomes@lxorguk.ukuu.org.uk, linux-efi@vger.kernel.org, gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, jforbes@redhat.com Subject: Re: [PATCH 07/27] kexec_file: Disable at runtime if securelevel has been set MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <25996.1509029504.1@warthog.procyon.org.uk> Date: Thu, 26 Oct 2017 15:51:44 +0100 Message-ID: <25997.1509029504@warthog.procyon.org.uk> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Thu, 26 Oct 2017 14:51:46 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Mimi Zohar wrote: > The patch title and description needs to be updated to refer to > lockdown, not securelevel. Fixed, thanks. > An additional patch could force these rules to be added to the custom > policy, if lockdown is enabled. I'll have a look at your patch, though at this point I'm leaning towards passing the current series to James for security/next and then passing your patch along afterwards, if that's okay with you. It should still get in the next merge window if that's the case. David