All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: Colin Walters <walters@verbum.org>, selinux@tycho.nsa.gov
Subject: Re: libselinux behavior in permissive mode wrt invalid domains
Date: Wed, 15 Apr 2009 09:03:47 -0400	[thread overview]
Message-ID: <1239800627.27560.34.camel@localhost.localdomain> (raw)
In-Reply-To: <49E5CFD8.6060903@redhat.com>

On Wed, 2009-04-15 at 08:15 -0400, Daniel J Walsh wrote:
> On 04/14/2009 02:42 PM, Colin Walters wrote:
> > Hi,
> >
> > I'd like broader input on:
> > http://bugs.freedesktop.org/show_bug.cgi?id=21072
> >
> > Is this something we can do inside libselinux itself?  Or are we
> > planning similar patches around avc_has_perm calls for the X server,
> > libvirt and other userspace programs?
> >
> > --
> > 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.
> 
> So the question is whether the API should return allowed when in 
> permissive mode rather then denied and make every App server code up 
> permissive mode check.
> 
> 
> We have had several bugs where tools have not checked whether the 
> machine is in permissive mode when doing an access check.  One 
> possibility would be to generate the AVC in the check code when in 
> permissive mode or always generat the AVC, there an return allowed.
> 
> If you look at the calling apps point of view it is asking if the user 
> should be allowed the access and in permissive mode he should be allowed 
> the access.

avc_has_perm() already checks for permissive mode internally, unlike
security_compute_av().  However, in this case, the problem is not that
permission was denied but rather that one of the security contexts is no
longer valid.

-- 
Stephen Smalley
National Security Agency


--
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:[~2009-04-15 13:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14 18:42 libselinux behavior in permissive mode wrt invalid domains Colin Walters
2009-04-15 12:15 ` Daniel J Walsh
2009-04-15 13:03   ` Stephen Smalley [this message]
2009-04-17  0:47     ` Eamon Walsh
2009-04-17 12:58       ` Stephen Smalley
2009-04-21 20:32         ` Joshua Brindle
2009-04-21 20:41           ` Stephen Smalley
2009-04-21 23:11             ` Eamon Walsh
2009-04-22 15:19               ` Colin Walters
2009-04-15 12:16 ` Stephen Smalley

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=1239800627.27560.34.camel@localhost.localdomain \
    --to=sds@tycho.nsa.gov \
    --cc=dwalsh@redhat.com \
    --cc=selinux@tycho.nsa.gov \
    --cc=walters@verbum.org \
    /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.