From mboxrd@z Thu Jan  1 00:00:00 1970
From: Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: [PATCH 01/11] Security: Add hook to get full maclabel xattr
	name
Date: Thu, 28 Feb 2008 17:00:05 -0800
Message-ID: <1204246805.7363.23.camel@heimdal.trondhjem.org>
References: <746385.69480.qm@web36611.mail.mud.yahoo.com>
	 <1204227035.31790.207.camel@moss-spartans.epoch.ncsc.mil>
	 <20080228234850.GA25829@infradead.org>
	 <1204243497.2715.24.camel@moss-terrapins.epoch.ncsc.mil>
	 <20080229003937.GA16343@infradead.org>
	 <1204246206.7363.13.camel@heimdal.trondhjem.org>
	 <20080229005113.GA24087@infradead.org>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Cc: Dave Quigley <dpquigl@tycho.nsa.gov>,
	Stephen Smalley <sds@tycho.nsa.gov>, casey@schaufler-ca.com,
	viro@ftp.linux.org.uk, bfields@fieldses.org,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	LSM List <linux-security-module@vger.kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Return-path: <linux-security-module-owner@vger.kernel.org>
In-Reply-To: <20080229005113.GA24087@infradead.org>
Sender: linux-security-module-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org


On Thu, 2008-02-28 at 19:51 -0500, Christoph Hellwig wrote:
> On Thu, Feb 28, 2008 at 04:50:06PM -0800, Trond Myklebust wrote:
> > As I've told you several times before: we're _NOT_ putting private
> > ioctl^Hxattrs onto the wire. If the protocol can't be described in an
> > RFC, then it isn't going in no matter what expletive you choose to
> > use...
> 
> It's as unstructured as the named attributes already in.  Or file data
> for that matter.

Describing what is supposed to be a security mechanism in a structured
fashion for use in a protocol should hardly be an impossible task (and
AFAICS, Dave & co are making good progress in doing so). If it is, then
that casts serious doubt on the validity of the security model...

There should be no need for ioctls.