Just setuid etc. doesn't work with that because access cannot be easily
revoked without disturbing other clients.
To handle that you would probably need a "relookup if needed" mechanism
similar to what NFSv4 has, so that you can force other users to relookup
after you revoked a key. That complicates the use a lot though.
Also the model depends on good secure random numbers, which is questionable
in many environments (e.g. a diskless box where the random device effectively
gets no new input)
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/