All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Colin Walters <walters@verbum.org>
Cc: Lennart Poettering <lennart@poettering.net>,
	russell@coker.com.au, Eric Paris <eparis@redhat.com>,
	selinux@tycho.nsa.gov, sds@tycho.nsa.gov
Subject: Re: A filename to label translation daemon
Date: Mon, 13 Aug 2012 14:06:43 -0400	[thread overview]
Message-ID: <50294233.9070008@redhat.com> (raw)
In-Reply-To: <1344880524.16306.15.camel@lenny>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/13/2012 01:55 PM, Colin Walters wrote:
> On Mon, 2012-08-13 at 13:36 -0400, Daniel J Walsh wrote:
> 
>> This seems like the best solution?  If upstream will accept it.  We
>> could rebuild the regex data when semanage modifies the file context.
> 
> One thing that will make me mildly sad about this is that now in GNOME 
> processes we'll have *three* regexp libraries linked in: libc, glib's PCRE
> fork (it's ancient history now), and PCRE via libselinux.
> 
> I wonder how hard it would be to get a pcre_precompile equivalent into 
> libc.
> 
> Really though in the big picture, while the file context regexps were 
> probably an OK solution way back when SELinux was a "proof of concept" 
> prototype, the current policy generating 5000 of them is just crazy...
> 
> One other possibility - I bet one could get a huge speedup in some cases by
> splitting up the regexp set based on common prefixes.  For example, if
> you're trying to match /tmp/krb5cc, there's no reason to run over all 2000
> regexps which start with /usr.  This solution is kind of an intermediate
> step between "run 5000 regexps serially" and "write custom code to compile
> 5000 regexps into a DFA that returns a context".
> 
> 
> 
> 
> 
> -- 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.
> 

We have had a solution for this using prefixes and were trying to add some
intelligence to the library, but we are now thinking this is not a good
solution since we are running into potential problems with substitutions.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlApQjMACgkQrlYvE4MpobNznACgxFNRIS8PmrgKjSLI+sKisyNn
elEAoJ7qx9TI7c9lCllt5UOGmMxOEFZ9
=36+R
-----END PGP SIGNATURE-----

--
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-13 18:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08 19:31 A filename to label translation daemon Eric Paris
2012-08-08 20:05 ` Stephen Smalley
2012-08-08 20:52   ` Daniel J Walsh
2012-08-08 20:55   ` Eric Paris
2012-08-08 21:26 ` Colin Walters
2012-08-09 14:37   ` Russell Coker
2012-08-09 17:06     ` Daniel J Walsh
2012-08-09 17:51       ` Colin Walters
     [not found]         ` <20120810141101.GC32076@tango.0pointer.de>
     [not found]           ` <20120810141747.GA909@tango.0pointer.de>
2012-08-13 17:36             ` Daniel J Walsh
2012-08-13 17:55               ` Colin Walters
2012-08-13 18:06                 ` Daniel J Walsh [this message]
2012-08-14 11:18                 ` Russell Coker
2012-08-14 12:38                   ` Eric Paris
2012-08-14 14:01                     ` Eric Paris
2012-08-14 16:48                       ` Stephen Smalley
2012-08-14 17:21                         ` Eric Paris
2012-08-14 22:34                         ` Russell Coker
2012-08-15  5:56                     ` Russell Coker
2012-08-15 13:22                       ` Eric Paris
2012-08-16 23:51                         ` Eric Paris
2012-08-10  2:28       ` Russell Coker
2012-08-10 12:39         ` Daniel J Walsh
2012-08-10 13:35           ` Russell Coker
2012-08-12 11:02             ` Daniel J Walsh
     [not found]           ` <20120810140503.GB32076@tango.0pointer.de>
2012-08-12 11:03             ` Daniel J Walsh
     [not found]               ` <20120813151821.GB4861@redhat.com>
2012-08-13 16:37                 ` Daniel J Walsh

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=50294233.9070008@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=eparis@redhat.com \
    --cc=lennart@poettering.net \
    --cc=russell@coker.com.au \
    --cc=sds@tycho.nsa.gov \
    --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.