From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>, SE Linux <selinux@tycho.nsa.gov>
Subject: Re: policycoreutils patch
Date: Thu, 26 Apr 2007 15:18:54 -0400 [thread overview]
Message-ID: <1177615134.3405.43.camel@localhost.localdomain> (raw)
In-Reply-To: <4630C59F.1070106@redhat.com>
On Thu, 2007-04-26 at 11:30 -0400, Daniel J Walsh wrote:
> This patch moves audit2why to /usr/bin to match audit2allow, since both
> can be used from userspace. Also moves sepolgen-ifget to /usr/sbin,
> since this is not to be run by normal users.
>
sepolgen-ifgen can be run by a normal user and the output saved to an
arbitrary file. audit2allow also has flags for reading the interface
information from a non-default flag. So I think it should stay
in /usr/bin.
I merged the audit2why change to trunk, stable, and policyrep.
Karl
--
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:[~2007-04-26 19:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 15:30 policycoreutils patch Daniel J Walsh
2007-04-26 19:18 ` Karl MacMillan [this message]
2007-04-27 12:50 ` Daniel J Walsh
2007-04-27 14:30 ` Karl MacMillan
2007-04-27 15:10 ` Stephen Smalley
-- strict thread matches above, loose matches on Subject: below --
2008-10-23 17:15 Daniel J Walsh
2008-11-10 15:52 ` Joshua Brindle
2008-08-01 11:43 Daniel J Walsh
2008-08-05 13:44 ` Stephen Smalley
2008-08-05 13:57 ` Stephen Smalley
2008-08-05 14:20 ` Daniel J Walsh
2008-01-11 21:15 Daniel J Walsh
2008-01-23 21:01 ` Stephen Smalley
2007-12-06 18:34 Daniel J Walsh
2007-12-07 20:19 ` Stephen Smalley
2007-06-01 14:32 Daniel J Walsh
2007-06-05 14:05 ` Stephen Smalley
[not found] <45DB0AB8.3070803@redhat.com>
2007-02-21 17:22 ` Stephen Smalley
2006-03-29 15:19 Daniel J Walsh
2003-11-19 3:40 Russell Coker
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=1177615134.3405.43.camel@localhost.localdomain \
--to=kmacmillan@mentalrootkit.com \
--cc=dwalsh@redhat.com \
--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.