From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 4E4AAC9D for ; Thu, 2 Feb 2017 21:12:38 +0000 (UTC) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id D905C1FD for ; Thu, 2 Feb 2017 21:12:37 +0000 (UTC) From: David Howells In-Reply-To: References: To: Andy Lutomirski MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4705.1486069954.1@warthog.procyon.org.uk> Date: Thu, 02 Feb 2017 21:12:34 +0000 Message-ID: <4706.1486069954@warthog.procyon.org.uk> Cc: Josh Armour , "ksummit-discuss@lists.linuxfoundation.org" , Greg KH , Djalal Harouni Subject: Re: [Ksummit-discuss] security-related TODO items? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Andy Lutomirski wrote: > Here's another one: split up and modernize /proc. Just remember: /proc is part of the user API. It contains system calls that are implemented with open/read/write/close rather than syscall directly. As such, you may not alter functionality that will break userspace[*]. [*] OTOH restricting stuff for security purposes does have merit, so I'm not totally against the idea. David