Messages in this thread | | | Date | Sun, 02 Dec 2007 10:28:37 +0900 | From | KaiGai Kohei <> | Subject | Re: [PATCH] capabilities: introduce per-process capability bounding set (v10) |
| |
Serge,
> Is there any reason not to have a separate /etc/login.capbounds > config file, though, so the account can still have a full name? > Did you only use that for convenience of proof of concept, or > is there another reason?
passwd(5) says the fifth field is optional and only used for informational purpose (like ulimit, umask).
However, using any other separate config file is conservative and better. One candidate is "/etc/security/capability.conf" defined as the config file of pam_cap.
Thanks, -- KaiGai Kohei <kaigai@kaigai.gr.jp>
| |