All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Patrick K., ITF" <cto@itechfrontiers.com>
To: Raul da Silva {Sp4wn} <sp4wn.root@gmail.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: proof selinux
Date: Tue, 28 Aug 2012 23:41:12 -0400	[thread overview]
Message-ID: <503D8F58.3010207@itechfrontiers.com> (raw)
In-Reply-To: <CAE_4iW8xF5NLvjrXKpSExgstbFx8JKfx38F5PBN0YP3VaPFz4Q@mail.gmail.com>

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@gmail.com <mailto:sp4wn.root@gmail.com>
>
>

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2012-08-29  3:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-29  2:50 proof selinux Raul da Silva {Sp4wn}
2012-08-29  3:41 ` Patrick K., ITF [this message]
     [not found]   ` <CAFftDdo1286WZaKfgeJK8xe=N4DE6F3HyQe-X5FM2kpUQD3rxA@mail.gmail.com>
2012-08-29  4:28     ` Patrick K., ITF
2012-08-29  5:57       ` William Roberts
2012-09-04 18:20         ` Daniel J Walsh
2012-08-29  7:28 ` Russell Coker
2012-08-29 18:40   ` David Quigley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=503D8F58.3010207@itechfrontiers.com \
    --to=cto@itechfrontiers.com \
    --cc=selinux@tycho.nsa.gov \
    --cc=sp4wn.root@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.