All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ole Kliemann <ole@plastictree.net>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: selinux@tycho.nsa.gov
Subject: Re: Possible bug in finding default context?
Date: Fri, 10 Aug 2012 10:58:40 +0200	[thread overview]
Message-ID: <20120810085840.GA2296@telvanni> (raw)
In-Reply-To: <1344534512.1175.17.camel@moss-pluto.epoch.ncsc.mil>

[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]

On Thu, Aug 09, 2012 at 01:48:32PM -0400, Stephen Smalley wrote:
> On Thu, 2012-08-09 at 19:45 +0200, Ole Kliemann wrote:
> > BTW, the exact number seems 194. 194 types associated with one 
> > role works. 195 and it's broken.
> > 
> > I'm doing this on Ubuntu 12.04, so it could be the crappily 
> > maintained selinux userland here.
> 
> We'd like to rip out all usage of security_compute_user()
> aka /sys/fs/selinux/user and everything that calls it.  Previously
> discussed on the list, although not your specific problem (presumably
> we're hitting the selinuxfs limit on size of response for /selinux/user
> transactions).  Take all of that logic to userspace and greatly simplify
> it.

Since I seem to be inclined to do strange things noone really did 
before, I have to ask this:

This is strictly a problem only for the userspace, right? The LSM 
can handled what ever I throw at it and will always enforce the 
policy by the letter, no matter how many types/roles/user or 
other strange constructs whatsoever I use?

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-08-10  8:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-09 17:45 Possible bug in finding default context? Ole Kliemann
2012-08-09 17:48 ` Stephen Smalley
2012-08-10  8:58   ` Ole Kliemann [this message]
2012-08-10 12:55     ` Stephen Smalley
2012-08-10  9:13 ` Russell Coker
2012-08-10 10:37   ` Ole Kliemann
2012-08-10 17:21     ` Ole Kliemann
2012-08-10 11:06 ` Ole Kliemann

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=20120810085840.GA2296@telvanni \
    --to=ole@plastictree.net \
    --cc=sds@tycho.nsa.gov \
    --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.