diff options
author | Serge E. Hallyn <serue@us.ibm.com> | 2008-12-03 14:17:33 -0500 |
---|---|---|
committer | James Morris <jmorris@namei.org> | 2008-12-07 17:16:27 -0500 |
commit | 7657d90497f98426af17f0ac633a9b335bb7a8fb (patch) | |
tree | 6344dc4715a85383f6492a4102ae406c6b86d79d /kernel/user.c | |
parent | c37bbb0fdcc01610fd55604eb6927210a1d20044 (diff) |
user namespaces: require cap_set{ug}id for CLONE_NEWUSER
While ideally CLONE_NEWUSER will eventually require no
privilege, the required permission checks are currently
not there. As a result, CLONE_NEWUSER has the same effect
as a setuid(0)+setgroups(1,"0"). While we already require
CAP_SYS_ADMIN, requiring CAP_SETUID and CAP_SETGID seems
appropriate.
Signed-off-by: Serge E. Hallyn <serue@us.ibm.com>
Acked-by: "Eric W. Biederman" <ebiederm@xmission.com>
Signed-off-by: James Morris <jmorris@namei.org>
Diffstat (limited to 'kernel/user.c')
0 files changed, 0 insertions, 0 deletions