From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: Latest policy diffs, very large
Date: Mon, 09 Jan 2006 12:56:56 -0500 [thread overview]
Message-ID: <1136829416.29815.97.camel@sgc> (raw)
In-Reply-To: <43BAD603.5060209@redhat.com>
On Tue, 2006-01-03 at 14:52 -0500, Daniel J Walsh wrote:
> ftp://people.redhat.com/dwalsh/SELinux/policy-20060103.patch
I've merged most of this in so far, but I have several questions.
> Added selinux policy man pages.
I merged this, but in the long run I think it would be better if we
eventually move the information into the XML documentation, and write a
tool that will generate the man pages from the XML, so that there aren't
any possible synchronization problems between the XML and the man pages.
> Many minor changes...
* why does automount need net_bind_service? it doesn't have any rules
for binding sockets.
* there are comments about readahead in initrc distro_redhat; however,
readahead has a policy now, so why are these rules still needed?
* several daemons added cron_system_entry(), cron, cups, apm, why is
this needed?
* why is dev_read_raw_memory(hald_t) needed?
* why is noatsecure needed for the kernel to run init on an MLS system?
* why does mount_t need to rw all terminals?
--
Chris PeBenito
Tresys Technology, LLC
(410) 290-1411 x150
--
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:[~2006-01-09 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 19:52 Latest policy diffs, very large Daniel J Walsh
2006-01-09 17:56 ` Christopher J. PeBenito [this message]
2006-01-09 20:24 ` Daniel J Walsh
2006-01-11 22:24 ` Daniel J Walsh
2006-01-11 23:47 ` 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=1136829416.29815.97.camel@sgc \
--to=cpebenito@tresys.com \
--cc=dwalsh@redhat.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.