From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932343AbdJWO5B (ORCPT ); Mon, 23 Oct 2017 10:57:01 -0400 Received: from mx1.redhat.com ([209.132.183.28]:33568 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932274AbdJWO5A (ORCPT ); Mon, 23 Oct 2017 10:57:00 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com F058134336E Authentication-Results: ext-mx05.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx05.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: References: <150842463163.7923.11081723749106843698.stgit@warthog.procyon.org.uk> <150842482228.7923.9630520914833154257.stgit@warthog.procyon.org.uk> To: James Morris 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 25/27] Lock down /proc/kcore MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <22789.1508770617.1@warthog.procyon.org.uk> Date: Mon, 23 Oct 2017 15:56:57 +0100 Message-ID: <22790.1508770617@warthog.procyon.org.uk> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Mon, 23 Oct 2017 14:57:00 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org James Morris wrote: > I have to wonder, though, after everything is locked down, how easy will > it be for new things to slip in which need to be included in the lockdown, > but are not. That's always a possibility, and short of reviewing every change, particularly in the drivers, I'm not sure how to prevent it. David From mboxrd@z Thu Jan 1 00:00:00 1970 From: dhowells@redhat.com (David Howells) Date: Mon, 23 Oct 2017 15:56:57 +0100 Subject: [PATCH 25/27] Lock down /proc/kcore In-Reply-To: References: <150842463163.7923.11081723749106843698.stgit@warthog.procyon.org.uk> <150842482228.7923.9630520914833154257.stgit@warthog.procyon.org.uk> Message-ID: <22790.1508770617@warthog.procyon.org.uk> To: linux-security-module@vger.kernel.org List-Id: linux-security-module.vger.kernel.org James Morris wrote: > I have to wonder, though, after everything is locked down, how easy will > it be for new things to slip in which need to be included in the lockdown, > but are not. That's always a possibility, and short of reviewing every change, particularly in the drivers, I'm not sure how to prevent it. David -- To unsubscribe from this list: send the line "unsubscribe linux-security-module" in the body of a message to majordomo at vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html