From: Stephen Smalley <sds@tycho.nsa.gov>
To: Joshua Brindle <method@manicmethod.com>
Cc: Daniel J Walsh <dwalsh@redhat.com>,
Chad Sellers <csellers@tresys.com>,
SE Linux <selinux@tycho.nsa.gov>,
Eric Paris <eparis@parisplace.org>,
James Morris <jmorris@namei.org>
Subject: Re: chcat fixes
Date: Mon, 22 Jun 2009 08:29:03 -0400 [thread overview]
Message-ID: <1245673743.3033.114.camel@localhost.localdomain> (raw)
In-Reply-To: <4A3BCB2F.908@manicmethod.com>
On Fri, 2009-06-19 at 13:30 -0400, Joshua Brindle wrote:
> Daniel J Walsh wrote:
> > On 05/20/2009 04:05 PM, Chad Sellers wrote:
> >> On 5/20/09 3:00 PM, "Daniel J Walsh"<dwalsh@redhat.com> wrote:
> >>
> >>> Expansion of categores is still broken. Here is a patch to fix.
> >>>
>
> Its a shame that we are still hard coding the format for categories into tools,
> we might as well have hardcoded the format into the security server.
>
> Stephen - any chance we could get selinuxfs interfaces that export
> level/category data so that tools can use that instead of hardcoding this stuff?
That would be fine with me. Not only level/category data, but also
other policy information (e.g. user data) to allow obsoleting
of /selinux/users.
--
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.
next prev parent reply other threads:[~2009-06-22 12:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C639DAB6.A73D6%csellers@tresys.com>
2009-05-21 12:13 ` chcat fixes Daniel J Walsh
2009-06-19 17:30 ` Joshua Brindle
2009-06-22 12:29 ` Stephen Smalley [this message]
2009-06-23 17:06 ` Joshua Brindle
2009-05-20 19:00 Daniel J Walsh
2009-05-21 10:50 ` Christopher J. PeBenito
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=1245673743.3033.114.camel@localhost.localdomain \
--to=sds@tycho.nsa.gov \
--cc=csellers@tresys.com \
--cc=dwalsh@redhat.com \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--cc=method@manicmethod.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.