How does grsecurity compare to smack?

Discuss usability issues, general maintenance, and general support issues for a grsecurity-enabled system.

How does grsecurity compare to smack?

Postby nwmcsween » Wed Apr 09, 2008 10:19 am

I know grsecurity covers more than what smack does but I like to keep things as simple as possible. How would grsecurity compare to smack? Would using pax and smack be somewhat equivalent to grsecurity and pax? (in a access control sense)
nwmcsween
 
Posts: 4
Joined: Thu May 31, 2007 10:19 pm

Re: How does grsecurity compare to smack?

Postby cormander » Wed Apr 09, 2008 11:42 am

I haven't ever used it, but looks like smack uses LSM. If you haven't already, read the comments here: http://www.grsecurity.net/lsm.php

In particular this item applies to your question: "LSM involves only Access Control. grsecurity performs many other functions than just Access Control."

As far as LSM(smack) + PaX, you're getting closer to grsecurity's functionality, but grsecurity independent of PaX and RBAC does a lot of hardening that LSM can't do, because they require kernel patching.

In a access control sense, smack can probably do everything grsecurity can. I'm not sure about logging, grsecurity has extensive auditing capablity (but if you're going to use LSM anyway, you can just use auditd). Another thing, grsecurity doesn't use filesystem labels. There are pros and cons to this; though I happen to dislike filesystem labels. So in my personal opinion, grsecurity is at least one-up on smack in MAC.
cormander
 
Posts: 154
Joined: Tue Jan 29, 2008 12:51 pm


Return to grsecurity support