Messages in this thread | ![/](/images/icornerl.gif) | | Date | Wed, 23 Apr 2003 19:45:01 +0100 | From | Christoph Hellwig <> | Subject | Re: [PATCH] Extended Attributes for Security Modules against 2.5.68 |
| |
On Wed, Apr 23, 2003 at 11:25:49AM -0700, Chris Wright wrote: > It's really a namespace issue for user apps trying to deal with xattrs.
Yes.
> Being able to display the xattrs associated with a file in sane way, > like getxattr(path, "system.security", ...). Otherwise something like > listxattr() then gettxttr(... "system.security.[blah]" ...). Total > freeform naming is a headache for userspace to deal with. Esp. since we > don't want to teach all userland tools about each individual module/policy.
Randomly userland shouldn't deal with these xattrs. Remember you are talking about the ondisk represenation of your labelling - nothing but the labelling tools should ever touch it.
> There were a couple proposals to use common root like "system.security." > (or the trusted namespace which was discussed in earlier threads). > > Would you still prefer module specific naming?
Personally I give a damn about the actual naming. Just make sure that each name has a unique meaning associated with it.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| ![\](/images/icornerr.gif) |