Messages in this thread | | | Date | Wed, 05 Dec 2012 22:12:15 +0200 | From | Markku Savela <> | Subject | Re: [RFC] Capabilities still can't be inherited by normal programs |
| |
On 12/05/2012 09:32 PM, Andy Lutomirski wrote: >> >Anyway, implementing the features you want in a new module is encouraged, >> >so long as the behavior of existing module stays the same. > I'll think about it some more and do it possibly using a sysctl. > Adding this kind of stuff in a module is asking for even worse > incomprehensibility of which capability bit means what.
For what is worth, and just for information. This module approach has been attempted, sort of: I did implement capabilities inheritance in Nokia N9 (Aegis). The capabilities started to inherit when task entered "aegis mode" (a bit in secure bits).
The experience was "interesting". There are many "simplified" articles about running root with less than full capabilities, and we did that. However, it also caused a lot of headache, because many people got hit by this "root is no more omnipotent" thing and complained. It was a pain to manage and find correct required for each task and often end result was to grant all (or at least too much).
| |