I'm not sure I understand. Capabilities shouldn't just be set. We
already have the PF_SUPERPRIV flag which is set whenever a process
_uses_ root privileges. It would be more natural to define a PF_RAWIO
flag similar to PF_SUPERPRIV (or if needed, a complete set of 'have
used CAP_xxx' flags). In the PF_RAWIO case, you probably want to make
sure that you handle inherited open file-descriptors as well.
Remember, you can have rawio access without having CAP_RAW_IO if you
inherit a file descriptor. Actually, all normal svgalib-application
have rawio access without having CAP_RAW_IO since they normally do a
setuid() after a short initialization sequence.
Another point, a bit unrelated to the discussion is that a capability
called CAP_SIGMASK exists in the draft standard. It allows a program
to mask unmaskable signals. It isn't in the vanilla kernel yet.
astor
-- Alexander Kjeldaas, Guardian Networks AS, Trondheim, Norway http://www.guardian.no/- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu