From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752340AbdGXA7T (ORCPT ); Sun, 23 Jul 2017 20:59:19 -0400 Received: from nm3-vm5.bullet.mail.ne1.yahoo.com ([98.138.91.225]:56488 "EHLO nm3-vm5.bullet.mail.ne1.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751789AbdGXA7J (ORCPT ); Sun, 23 Jul 2017 20:59:09 -0400 X-Yahoo-Newman-Id: 959996.92781.bm@smtp220.mail.ne1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 2BvFH3EVM1nfRjDR3LAqsOwqcXNcKPeMy4VtH.HpK9w.lwe wMm7pqniWB9Q1GeM8DYhUEXud9KYsNcyvnEvtddgs4VFHMBZz4uYjYnrh5BA qTIE7xmq9IUknmjl6EAEzCozbbpbN8Fk7_mwNunly2cgMMTWiCy37hGuSFjY ycx4EbY017qM1dv.jdg_Hhbkg9LXhE.w1oZ3Ry.uwyHdaPWIRC86Vl04S4ab 879QInkxtpnUSTbnaKJohelpOAiJbZCfXrPoC3o0osaDjqSJvI7O7MiqsPFM W1fXuAzKiaSCj0QW5Eh0fYdYWvFQ0uq6HAx7d.iyz0TqhtzCG62AK8mVkHHf _6ltOiUHDKApyyYIeC60YyyGmSNBDFfVnx4uPoTJiZtclYwX4K8R92J2qpeg NFUyToqrN.TSLsTos_GQPZbzipTqcsalSSyJ85P.424.ZBin1SQs6YoU9KUX rAdGqxSUDJZeZjJH5V3WH0oV.XALqzSMEpdGz6RCRLmozdUBD4MRKM7fRUFK rpTcy8U8izwZ.sH2Kpj1Xf4KEiex3NvX9ZSq26Db7ymNdQm5hd3eZQjptBQ- - X-Yahoo-SMTP: OIJXglSswBDfgLtXluJ6wiAYv6_cnw-- Subject: Re: [kernel-hardening] [PATCH 00/11] S.A.R.A. a new stacked LSM To: "Serge E. Hallyn" , Mimi Zohar Cc: Matt Brown , Salvatore Mesoraca , =?UTF-8?Q?Micka=c3=abl_Sala=c3=bcn?= , kernel list , linux-security-module , Kernel Hardening , Brad Spengler , PaX Team , Kees Cook , James Morris References: <1497286620-15027-1-git-send-email-s.mesoraca16@gmail.com> <53a2d710-b0f0-cdf9-e7ad-cd8d03fc835a@digikod.net> <69ff2195-d0e1-8a0f-b80e-5d8d55947907@nmatt.com> <1499801476.6034.265.camel@linux.vnet.ibm.com> <988555a2-bed9-234c-843c-0bb68dc60d3f@nmatt.com> <1499959179.4220.45.camel@linux.vnet.ibm.com> <20170713195106.GD4895@mail.hallyn.com> From: Casey Schaufler Message-ID: <6be222da-79b3-b406-53c9-10ee691bb9c6@schaufler-ca.com> Date: Sun, 23 Jul 2017 17:58:56 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20170713195106.GD4895@mail.hallyn.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 7/13/2017 12:51 PM, Serge E. Hallyn wrote: > Quoting Mimi Zohar (zohar@linux.vnet.ibm.com): >> On Thu, 2017-07-13 at 08:39 -0400, Matt Brown wrote: >> The question is really from a security perspective which is better? >> Obviously, as v2 of the patch set changed from using pathnames to >> inodes, it's pretty clear that I think inodes would be better. Kees, >> Serge, Casey any comments? > Yes, inode seems clearly better. Paths are too easily worked around. An inode identifies the object, while a pathname identifies the intent. Using the inode will be easier to code and easier to model. Using the pathname will be much more likely to reflect what the human means to accomplish, provided all the idiosyncrasies of the Linux filesystem namespace are taken into account. Ever since the link count on an inode was allowed to exceed 1* this has been difficult to accomplish. ---- * The link count has always been allowed to exceed 1. Then there are symlinks, mount points, overlay filesystems and all manner of other slick features that make the filesystem namespace difficult to deal with from the security standpoint. > -- > To unsubscribe from this list: send the line "unsubscribe linux-security-module" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >