Skip to contentSkip to conversation

file capabilities: add no_file_caps switch (v2)

PATCH Markku Savela 1 participant 1 message Sep 23, 2008 3 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#3 lore raw
Quoted 5 lines · Andreas Gruenbacher

Sure, that would work as well, except that I think that file capabilities should always default to "on" as they will become a standard security mechanism before long. We just don't have much system management tool support yet, and I would like to give that some more time safely, without putting users at unnecessary risk.

As I've said elsewhere, I consider above a bad move. The "file capabilities" are just setgid/setuid executables in disguise (although with little finer control).

I would prefer two choices for capabilities:

1) file capabilities, for those who think they work

2) no file capabilities, but just normal inheritance. There should be nothing mystical about this. The credential (uid, groups) inherit just fine without problems. Why not capabilities?