Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

If not, what would be an example of a non-object permission?

share|improve this question
up vote 2 down vote accepted

IIRC, in Posix systems (of which Linux is one) the dictum "everything is a file" is very much the case. You can do direct memory access with file-access API. So yes, there are permissions attached to all objects.

share|improve this answer
Thanks, already randomly ran across your profile trying to trouble shoot some system errors on SX-meta, and am truly impressed with the depth of knowledge you have. Cheers! – blunders Oct 10 '10 at 22:08
Well, everything is a file, a semaphore, a message queue, a non-FS-attached shared memory segment or a socket (and sockets are pretty darned file-like, except they normally don't live in a file-like namespace). – Vatine Oct 11 '10 at 6:24

Things such as SELinux permissions are not directly attached to the object, and must be inferred from the context attached to the object, the role of the current user, the domain of the current process, and the transitions given within the policy.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.