GOS wrote:Hey guys,
recently I switched to hardened profile and activated GrSecurity's kernel features including Pax. Except some small problems related to python 2.7 my Xfce-desktop works well after exchanging icedtea-java by oracle java.
What do you mean with "icedtea-java by oracle java"? I'm not completely sure, so, pls. did you got rid of icedtea-java and installed Larry Oracle's java?
If so, is like exchanging a good thing with something very doubtful.
However, the only remaining feature I did not activated until now is GrSec's RBAC with gradm.
Learning gradm took me a lot of time. Just keep up. Because
grsec is well worth it. All the wikibook, I'm sure you stumbled upon it, but, OK, I'll find the link:
https://en.wikibooks.org/wiki/Grsecurity
All the wikibook needs to become pretty familiar to you, well, most of it, to successfully deploy
grsec.
And esp. the good news by
spender (the main developer) at:
RBAC startup and shutdown included in policy?
http://forums.grsecurity.net/viewtopic.php?f=5&t=2248
makes me happy. But, for you...
Some questions for me are
1) Why there are different "roles" for gradm (admin, shutdown, masterpassword). Are the mentioned ones all or are there more "password secured roles" for gradm?
2) Why RBAC is activated with "gradm -E" and disbaled with "gradm -D" and not via a daemon? Is there a standard way to start ist during boot and diable it during shutdown?
3) Does RBAC restict also root? If yes, is there a possibility to get "unrestricted root access"? Is this question related to the "admin role" of gradm?
[But, for you...], I must repeat: study the wikibook linked above.
Then you will figure out yourself that the answers are:
2) No starting grsec with init services. Not recommended. I think it's in the
/etc/grsec/learn_config, where it used to read (and does in my install):
# comment them out if you are starting learning before services are started by init
# (a highly non-recommended choice)
But actually you speak of activating it when the learning has already been done. No, I don't know of such a method.
3) Yes, RBAC restricts also root. No. Use the admin role for that.
But, again, study the wikibook linked above. Then you will figure it all out yourself.
Hopefully my questions are not to stupid.
No, not stupid. But, you see, you get NSA-Linux, erhm, I meant SELinux for newbies to install and use foolproof, but, sadly, there is too little dev power in marvelous programs like
grsecurity...
Regardless of that, I can tell that
grsecurity does really good job on my system, and any advanced user (lots of people in Gentoo use it), will tell you that.
Cheers! GOS
PS: Is it (as last resort) possible to exchange GrSec's RBAC by AppArmor or something similar or do one lost here some functionality?
No, not possible, AFAICT. But anyway, going for any other hardening than
grsecurity is like ditching gold for junk.
Regards!