From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 20 Mar 2008 02:24:53 +1100 (EST) From: James Morris To: Casey Schaufler cc: Stephen Smalley , "David P. Quigley" , chrisw@sous-sol.org, hch@lst.de, viro@zeniv.linux.org.uk, selinux@tycho.nsa.gov, linux-security-module@vger.kernel.org, linux-fsdevel@vger.kernel.org, nfsv4@linux-nfs.org Subject: Re: [RFC]Introduce generalized hooks for getting and setting inode secctx v3 In-Reply-To: <522307.23148.qm@web36604.mail.mud.yahoo.com> Message-ID: References: <522307.23148.qm@web36604.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-selinux@tycho.nsa.gov List-Id: selinux@tycho.nsa.gov On Wed, 19 Mar 2008, Casey Schaufler wrote: > Oh, cut the crap. What part of my explainations don't you understand? > > I understand the functionality. That is not my point. My point is > that inode_notifysecctx() explicitly prohibits the LSM from providing > integrity of the security attributes by introducing a differentiation > between the "in-core" and "on-disk" values, and making it explicit > that the one is set, but not the other. > > Clearly this is the direction you intend to go. Have fun with it. > I've raised the issue, y'all aren't seeing it. Maybe I'm wrong, > it has happened before. Please stop trolling. - James -- James Morris -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with the words "unsubscribe selinux" without quotes as the message. From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Morris Subject: Re: [RFC]Introduce generalized hooks for getting and setting inode secctx v3 Date: Thu, 20 Mar 2008 02:24:53 +1100 (EST) Message-ID: References: <522307.23148.qm@web36604.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: nfsv4@linux-nfs.org, chrisw@sous-sol.org, linux-security-module@vger.kernel.org, viro@zeniv.linux.org.uk, selinux@tycho.nsa.gov, linux-fsdevel@vger.kernel.org, Stephen Smalley , hch@lst.de To: Casey Schaufler Return-path: In-Reply-To: <522307.23148.qm@web36604.mail.mud.yahoo.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: nfsv4-bounces@linux-nfs.org Errors-To: nfsv4-bounces@linux-nfs.org List-Id: linux-fsdevel.vger.kernel.org On Wed, 19 Mar 2008, Casey Schaufler wrote: > Oh, cut the crap. What part of my explainations don't you understand? > > I understand the functionality. That is not my point. My point is > that inode_notifysecctx() explicitly prohibits the LSM from providing > integrity of the security attributes by introducing a differentiation > between the "in-core" and "on-disk" values, and making it explicit > that the one is set, but not the other. > > Clearly this is the direction you intend to go. Have fun with it. > I've raised the issue, y'all aren't seeing it. Maybe I'm wrong, > it has happened before. Please stop trolling. - James -- James Morris