1 |
Hi! |
2 |
|
3 |
I'm not sure is this right place to ask… |
4 |
|
5 |
What is current status for filesystem's xattr, acl and caps? |
6 |
|
7 |
I'm usually keep all of this disabled in kernel, because I don't use them |
8 |
and wanna avoid needless complexity. But today consolekit (which I don't |
9 |
use, but which is installed anyway as someone's dependency) asked me to |
10 |
enable CONFIG_TMPFS_POSIX_ACL. And I decide to check all this crap once again. |
11 |
|
12 |
I may be wrong here, but after glance look at it I got this impression: |
13 |
|
14 |
XATTR |
15 |
Needed only if you use ACL or CAPS (or wanna play with custom file |
16 |
attributes). |
17 |
ACL |
18 |
Not sure about consolekit requirement above, but otherwise it looks |
19 |
useless (if you don't need to use complicated file permissions). |
20 |
CAPS |
21 |
Looks promising, it's always good to remove suid bit, BUT: |
22 |
a) looks like only app which uses it now on my workstation is |
23 |
wireshark, even /bin/ping is still installed suid |
24 |
b) pam_cap.so doesn't used by default (not sure why) so you can't change |
25 |
user's default capabilities using /etc/security/capability.conf |
26 |
|
27 |
So, until most/all suid apps in portage get CAPS support for me it looks |
28 |
like it's better to switch off all these things. |
29 |
|
30 |
-- |
31 |
WBR, Alex. |