From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: selinux@tycho.nsa.gov, SELinux-dev@tresys.com,
Tom London <selinux@gmail.com>,
Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
Subject: Re: matchpathcon_init overhead
Date: Thu, 01 Dec 2005 08:42:11 -0500 [thread overview]
Message-ID: <438EFDB3.3040004@redhat.com> (raw)
In-Reply-To: <1133439793.26593.410.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Wed, 2005-11-30 at 17:12 -0500, Daniel J Walsh wrote:
>
>> Why can't we confirm after the match.
>>
>> IE Match /dev/mydevice, now verify you have a good context.
>>
>> Then allow restorcon/fixfiles ... to do it the old way.
>>
>
> That would avoid the overhead of context canonicalization/validation,
> but wouldn't avoid the overhead of the regex compilation on all of
> file_contexts. We can try that first if you want, but allowing
> applications to select a subset of file_contexts entries for matching
> seems useful.
>
>
I was just thinking of the case of install. If you using install for
installing /usr/share/mypackage/myfile,
I guess you could submit /usr as the device, but you are still going to
get a hell of a lot of matches. Then
there is the case of you installing into /mydir/mypackage, and /mydir
would be submitted and probably match nothing, so
what happens then. May be we want both options. One for udev and one
for apps apps that use matchpathcon like install.
--
--
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.
next prev parent reply other threads:[~2005-12-01 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 21:18 matchpathcon_init overhead Stephen Smalley
2005-11-30 22:12 ` Daniel J Walsh
2005-12-01 12:23 ` Stephen Smalley
2005-12-01 13:42 ` Daniel J Walsh [this message]
2005-12-01 14:24 ` Stephen Smalley
2005-12-01 15:26 ` 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=438EFDB3.3040004@redhat.com \
--to=dwalsh@redhat.com \
--cc=SELinux-dev@tresys.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=sds@tycho.nsa.gov \
--cc=selinux@gmail.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.