All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Erich Schubert <erich@debian.org>
Cc: Alex Ackerman <alex@darkhonor.com>,
	fedora-selinux-list@redhat.com, selinux@tycho.nsa.gov,
	ackermal@jmu.edu
Subject: Re: SELinux Testing Software/Scripts
Date: Sun, 17 Oct 2004 15:04:20 +0100	[thread overview]
Message-ID: <20041017140420.GE19398@lkcl.net> (raw)
In-Reply-To: <1097974915.21919.5.camel@wintermute.xmldesign.de>

On Sun, Oct 17, 2004 at 03:01:54AM +0200, Erich Schubert wrote:
> Hi,
> 
> >  as i understand it, there is no "escalation" present in SE/Linux,
> >  only that assigned in the minds of us humans.
> [...]
> >  that's a bit different from "escalating privilege" because that implies
> >  hierarchy, which SE/Linux doesn't have, per-se.
> 
> As long as you have roles with certain higher privileges (for example
> writing to configuration files, binding to arbitrary ports, loading a
> new policy...) there is privilege escalation.

 
> Privilege escalation just means getting more rights than you were
> supposed to get. 

 ohright, okay: then my statement is incorrect and it is more that
 policy writers need to get their policies right, by not allowing more
 than is needed!


> You usually don't care about losing access rights,
> because you could have done things there earlier. Its only about getting
> a privilege you want to have.

 my point is that selinux allows that [to go from one domain to the
 next, losing all previous rights of the prior domain and gaining those
 of the next domain].

 which is not a "normal" security system so to speak: i'd consider
 "normal" to be that you get given more privileges by going to a
 "higher" privileged state [but i'm not saying "normal" is "good"].

 l.
 

-- 
--
Truth, honesty and respect are rare commodities that all spring from
the same well: Love.  If you love yourself and everyone and everything
around you, funnily and coincidentally enough, life gets a lot better.
--
<a href="http://lkcl.net">      lkcl.net      </a> <br />
<a href="mailto:lkcl@lkcl.net"> lkcl@lkcl.net </a> <br />


--
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:[~2004-10-17 13:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-16 13:56 SELinux Testing Software/Scripts Alex Ackerman
2004-10-16 14:41 ` Daniel J Walsh
2004-10-16 18:04 ` Luke Kenneth Casson Leighton
2004-10-17  1:01   ` Erich Schubert
2004-10-17 14:04     ` Luke Kenneth Casson Leighton [this message]

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=20041017140420.GE19398@lkcl.net \
    --to=lkcl@lkcl.net \
    --cc=ackermal@jmu.edu \
    --cc=alex@darkhonor.com \
    --cc=erich@debian.org \
    --cc=fedora-selinux-list@redhat.com \
    --cc=selinux@tycho.nsa.gov \
    /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.