[PATCH 0/3] p9auth fs: introduction
in [Kernel]
|
Prev: [PATCH 2/3] p9auth: add CAP_GRANT_ID to authorize use of /dev/caphash
Next: ftrace: print sample std dev when function profiling
From: Serge E. Hallyn on 27 Apr 2010 16:50 Hi, Here is an updated version of the p9auth setuid capability module, which hopefully addresses all previous feedback. It is now a separate filesystem instead of a device, as per Eric's suggestion. During the last round, Alan Cox made a great suggestion of sending credentials over AF_UNIX sock allowing the recipient to 'become me.' I think that's still an interesting idea, and intend to pursue it as Eric pushes the patches to translate userids across user namespaces. The tradeoffs are worth discussing. On the one hand, p9auth requires a scary CAP_GRANT_ID capability, while a SO_PASSAUTH would be more akin to an extension of CAP_SETUID. Also, SO_PASSAUTH would be usable by any unprivileged app, while one would hope there would be only one p9auth service for the whole system. On the other hand, the p9auth API appears to be pretty well settled and understood, and only provides for a very simple setting of all uids and all gids to one value, plus some auxiliary groups, which is perfect for use by simple login servers. p9auth and SO_PASSAUTH don't appear to be mutually exclusive. I don't know how painful it would be for plan-9 folks to make use of the SO_PASSAUTH feature. (It should definately be possible) But in any case here is the next iteration of p9auth fs for discussion and consideration. thanks, -serge -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |