lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87bowz5w3c.fsf@tucsk.pomaz.szeredi.hu>
Date:	Tue, 12 Jul 2011 17:59:03 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	"Sorin Faibish" <sfaibish@....com>
Cc:	"Ric Wheeler" <ricwheeler@...il.com>,
	"Hans-Peter Jansen" <hpj@...la.net>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	viro@...iv.linux.org.uk, torvalds@...ux-foundation.org,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	apw@...onical.com, nbd@...nwrt.org, neilb@...e.de,
	hramrach@...trum.cz, jordipujolp@...il.com, ezk@....cs.sunysb.edu,
	hooanon05@...oo.co.jp, "James Morris" <jmorris@...hat.com>,
	"Bruce Fields" <bfields@...hat.com>,
	"Steve Dickson" <SteveD@...hat.com>,
	"Trond Myklebust" <Trond.Myklebust@...app.com>
Subject: Re: [PATCH 0/7] overlay filesystem: request for inclusion

"Sorin Faibish" <sfaibish@....com> writes:

> On Sun, 10 Jul 2011 04:23:17 -0400, Ric Wheeler <ricwheeler@...il.com>
> wrote:
>> There is a proposed (at the IETF) standard called "labelled NFS"
>> that would allow the protocol to handle xattrs.
> Will be included in NFSv4.2. And we are already very close to a good I-D.
> Not sure that xattr change mentioned here will be included. You can look
> at the current I-D at:
> http://datatracker.ietf.org/doc/draft-quigley-nfsv4-labeled/

I skimmed the draft, and it looks like being mostly generic enough to
support any xattr, not just security labels.

But the naming and some of the requirements (such as notifying clients
on label change) are very much security label specific, forcing generic
xattr support into this protocol might not be a good idea.

I see that NFSv4 also has named attributes, which are conceptually
similar to linux xattr, but the APIs are not easily synchronized.

Doing xattr as a new protocol extension would be much easier and
cleaner, IMO.

Thanks,
Miklos
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ