<br><br><div><span class="gmail_quote">On 2/24/06, <b class="gmail_sendername">Ron Yorston</b> <<a href="mailto:rmy@tigress.co.uk">rmy@tigress.co.uk</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Davide Bolcioni wrote:<br>>I think we might be aiming at the wrong target, especially in<br>>the case of corporate admins. Target application developers,<br>>not admins: applications must work without requiring any modification
<br>>to the system and adapt accordingly.<br><br>Application developers? What has SELinux policy got to do with application<br>developers?<br><br>The targeted policy "focuses on locking down specific daemons, especially
<br>ones vulnerable to attack or to devastating a system if broken or<br>compromised". (From the SELinux FAQ on fedora.redhat.com.)<br><br>That's a tiny subset of applications.<br></blockquote></div><br>That was my understanding of SELinux. You could run a crazy program that has root privileges, is hackable, has no SELinux policy, and all that effort was for nigh.
<br><br>Benji<br>