- Code: Select all
# Role: root
subject / {
/
/bin xri
*snip*
Having the "i" above there, overrides the next explicitly defined subject:
- Code: Select all
# Role: root
subject /bin/bash o {
/ h
/bin h
It took me a while to figure out why I'd suddenly broken my policy and why things were being logged as the default subject for root, not the /bin/bash subject:
- Code: Select all
grsec: From 202.170.165.25: (root:U:/) denied access to hidden file /lib/i386-linux-gnu/i686/cmov by /bin/bash[bash:2010] uid/euid:0/0 gid/egid:0/0, parent /bin/su[su:2009] uid/euid:1000/0 gid/egid:0/0
So my question is - is this expected behaviour, a less specific subject with an inheritence rule will trump a specific subject rule?
(As soon as I removed the "i" from /bin on my default root subject I fixed my issue)