Recent Features
| |||||||||||||
SELinux and AppArmorSELinux and AppArmorPosted Oct 17, 2009 3:19 UTC (Sat) by dlang (✭ supporter ✭, #313)In reply to: SELinux and AppArmor by rahulsundaram Parent article: Walsh: Google Chrome Policy
I don't object to valid technical criticism.
however when that becomes 'it doesn't handle this case that SELinux does, so it must be worthless', that stops being valid technical criticism, and the objections have frequently gotten to that stage (and, no, my memory is not good enough to remember exactly who made which objections)
(Log in to post comments)
SELinux and AppArmor Posted Oct 17, 2009 3:44 UTC (Sat) by rahulsundaram (subscriber, #21946) [Link]
It seems you are badly paraphrasing comments elsewhere. If you point a specific link, it would be useful to know what was actually said. Some of the discussions involved the problem that the goals described the developers while submitting the patchset didn't match the patches.
It is ok for a security solution to address a specific subset of the problems while leaving others as outside the scope but the documentation should explicitly say so. If it doesn't then it makes it harder to merge those patches. Smack did a good job of describing the scope of the problem it was trying to address.
|
|||||||||||||