From: Joshua Brindle <method@manicmethod.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: James Morris <jmorris@namei.org>, Eric Paris <eparis@redhat.com>,
selinux@tycho.nsa.gov, dwalsh@redhat.com
Subject: Re: [PATCH] selinuxfs to globally disable dontaudit rules
Date: Thu, 16 Aug 2007 15:30:34 -0400 [thread overview]
Message-ID: <46C4A5DA.7030709@manicmethod.com> (raw)
In-Reply-To: <1187291884.909.103.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
>> Some of Dan's policycoreutils patches are trivial or simple bug fixes.
>> Others are less clear to me.
>>
>> I was going to test the libsemanage genhomedircon patches, but haven't
>> done so yet. I don't have a problem with them conceptually. Have you
>> verified that they yield no change in output under -targeted and -strict
>> policy? And run them under valgrind?
>>
>
> Oh, and what to do about the fact that it won't build anywhere but
> rawhide (ustr dependency)?
>
>
We can pull the parts of ustr we need into the library, it is designed
to do used that way. This is also trunk though, and we don't guarantee
ABI stability in trunk right? The sepolgen dependency of python 2.5
causes similar problems AFAIK.
>> Eric's handle unknown patches are still outstanding. Dan, if we merged
>> that support, would you use it in building future policies?
>>
>> Karl's sepolgen bug fix looks fine to merge.
>>
>> I (or someone) have to rework libsepol in stable and trunk to avoid
>> unaligned accesses (as per the wrong magic number thread). Already did
>> it once for the kernel. Sigh.
>>
>>
--
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-08-16 19:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 21:58 [PATCH] selinuxfs to globally disable dontaudit rules Eric Paris
2007-08-09 22:28 ` James Morris
2007-08-10 0:14 ` Joshua Brindle
2007-08-10 1:22 ` Joshua Brindle
2007-08-10 12:01 ` Stephen Smalley
2007-08-10 15:29 ` Daniel J Walsh
2007-08-10 15:58 ` Joshua Brindle
2007-08-10 18:16 ` Daniel J Walsh
2007-08-13 23:27 ` Joshua Brindle
2007-08-16 17:28 ` Stephen Smalley
2007-08-16 17:45 ` Joshua Brindle
2007-08-16 17:47 ` Stephen Smalley
2007-08-16 17:53 ` Joshua Brindle
2007-08-16 18:04 ` Stephen Smalley
2007-08-16 19:18 ` Stephen Smalley
2007-08-16 19:30 ` Joshua Brindle [this message]
2007-08-16 19:33 ` Stephen Smalley
2007-08-16 19:26 ` Joshua Brindle
2007-08-21 20:41 ` Daniel J Walsh
2007-08-21 23:41 ` Joshua Brindle
2007-08-22 15:32 ` Daniel J Walsh
2007-08-23 15:07 ` 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=46C4A5DA.7030709@manicmethod.com \
--to=method@manicmethod.com \
--cc=dwalsh@redhat.com \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--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.