Hi Raul,
I'm not sure if we are on the same page about SELinux.
SELinux is not there to prevent from buffer overflow or such exploits,
If you run a process in some kind of Role or Context, you confine it to
the limitations you defined in that context (using SELinux Policies),
How effective SELinux would be, depends on your policies actually.
The effectiveness of SELinux has nothing to do with exploits, unless of
course you meant attacking SELinux code or kernel LSM or Kernel itself.
Testing SELinux is easy, simply assign whatever role or policy you want
to a process and user or group, the ultimate exploit of a process gives
total control of that role or policy to that user. So the attackers
become as privileged as the role or user or context of the policy.
Sincerely,
Patrick K.
On 8/28/2012 10:50 PM, Raul da Silva {Sp4wn} wrote:
hi guys,
I know that we have a lot of ways to prove how effective is SELinux as
cgi, perl, shell scripts and I know that is effective but I'd like to
know if someone already tested some kind of exploit of buffer overflow
attack as demo to show how effective could be SELinux.
Any information I really appreciate
Thanks
Raul Leite
sp4wn.root@xxxxxxxxx <mailto:sp4wn.root@xxxxxxxxx>
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with
the words "unsubscribe selinux" without quotes as the message.
