Okay, so I'm trying to teach myself the SELinux policy language, but I've come up against a couple of questions.

It is possible to assign permission to execute without giving permission to read. What would happen if you tried to execute something that you were allowed to execute but not read? Would you be unable, since you need to read to execute?

Also, what permission is it that is needed to load a shared library? Is it execute, read, or both?

And finally, does any documentation of this language exist? I'm trying to learn on my feet from the reference policy, but it uses so many macros that I find myself completely unsure what is SELinux policy and what is a macro. I'm trying to use a tutorial written by Stephen Smalley, but it's a tutorial, not a comprehensive reference. Does any such documentation exist hidden away?

Thanks for all your help.

A file (the program) would have to be read in order for it to execute.

Actually, it is my understanding that execute permission is distinct from read so that you can set up a program as a "black box." But don't quote me on that.