policy "bloat" ?
One question for understanding: There are tons of files and rules in the example policy that are unnecessary for my install. So I've started to remove them, mostly in order to reduce the complexity and make everything easier to understand.
Is there any risk or noticeable performance impact from having unnecessary rules, e.g. dhcp stuff on a system that has neither client nor server installed?
If so, would it make sense to include a 2nd, "minimal" example policy?
Signature · 8 lines
http://web.lemuria.org/pubkey.html pub 1024D/D88D35A6 2001-11-14 Tom Vogt <[email protected]> Key fingerprint = 276B B7BB E4D8 FCCE DB8F F965 310B 811A D88D 35A6 -- You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.
Quoted 4 lines · Tom
One question for understanding: There are tons of files and rules in the example policy that are unnecessary for my install. So I've started to remove them, mostly in order to reduce the complexity and make everything easier to understand.
Good plan. Take what you need from the sample policy and dump the rest.
Quoted 3 lines
Is there any risk or noticeable performance impact from having unnecessary rules, e.g. dhcp stuff on a system that has neither client nor server installed?
Potentially a mistake in the policy could open a security hole in your system. Therefore the smaller policy the safer you will be. Also if you have a small policy then you can read through it all to make sure it does things you desire.
One issue is at the moment we have a single file_contexts file which has contexts for all files in the system, if you remove a file from the sample policy you will need to make a matching change to file_contexts. But that will be solved in the next major release.
Quoted 1 line
If so, would it make sense to include a 2nd, "minimal" example policy?
It does not make sense to have another policy which is the same thing but with a few files removed.
It does make sense to have another policy with another approach to securing a system. When I get the main sample policy working to my satisfaction I plan to produce some other sample policies. One I plan to produce is for the same sort of chroot environments as GR Security, another for LOMAC type security.
PS Today I released a new version of my Debian packages.
Signature · 9 lines
If you send email to me or to a mailing list that I use which has >4 lines of legalistic junk at the end then you are specifically authorizing me to do whatever I wish with the message and all other messages from your domain, by posting the message you agree that your long legalistic sig is void. -- You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.
Quoted 1 line · Russell Coker
Good plan. Take what you need from the sample policy and dump the rest.
doing that. I've removed about a third of the files from domains/program.
Quoted 4 lines
Quoted 1 line
If so, would it make sense to include a 2nd, "minimal" example policy?
It does not make sense to have another policy which is the same thing but with a few files removed.
Removing is some work, so I thought for people who'd rather build their policy from the ground up, a minimal config may be a better starting place. Just an idea.
Quoted 1 line
PS Today I released a new version of my Debian packages.
You are evil. That means I have to update again on monday. :)
Signature · 8 lines
http://web.lemuria.org/pubkey.html pub 1024D/D88D35A6 2001-11-14 Tom Vogt <[email protected]> Key fingerprint = 276B B7BB E4D8 FCCE DB8F F965 310B 811A D88D 35A6 -- You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.
Quoted 8 lines · Tom
Quoted 4 lines
Quoted 1 line
If so, would it make sense to include a 2nd, "minimal" example policy?
It does not make sense to have another policy which is the same thing but with a few files removed.
Removing is some work, so I thought for people who'd rather build their policy from the ground up, a minimal config may be a better starting place. Just an idea.
Removing is much easier than adding, unless you add wildly permissive domains.
Quoted 3 lines
Quoted 1 line
PS Today I released a new version of my Debian packages.
You are evil. That means I have to update again on monday. :)
I've just released a new version, and I'll probably have another before Monday.
Signature · 9 lines
If you send email to me or to a mailing list that I use which has >4 lines of legalistic junk at the end then you are specifically authorizing me to do whatever I wish with the message and all other messages from your domain, by posting the message you agree that your long legalistic sig is void. -- You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.