From: Daniel J Walsh <dwalsh@redhat.com>
To: "Christopher J. PeBenito" <cpebenito@tresys.com>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Latest policy
Date: Thu, 30 Mar 2006 11:37:20 -0500 [thread overview]
Message-ID: <442C0940.5050800@redhat.com> (raw)
In-Reply-To: <1143734415.13732.51.camel@sgc>
Christopher J. PeBenito wrote:
> On Wed, 2006-03-29 at 15:32 -0500, Daniel J Walsh wrote:
>
>> Added restorecond policy
>> fixed samba_selinux man page
>> logwatch looks for mounted files system on /mnt
>> file context for yumex
>> groupadd and useradd need to read nsswitch
>> hplib_port_t needed for 9100
>> add 6000 as valid xserver port
>> pam console needs to getattr/setattr usb_dev
>> bluetooth tools want to read resolver
>> hplib_t fixes to work with additional devices (Usb printers
>> dovecot wants to talk to postgresql and use inotify
>> hal needs to comunicate with ntp
>> pegasus needs to connect to random non reserved ports
>> privoxy wants to use nscd and communicate with tor
>> xfs needs to read fonts in usr_t
>> fstools need to be able to work with blk devices. (fsck)
>> libmpg123 is moving
>> mount using some certificates stored in usr_t
>>
>
> Merged.
>
>
>> setfiles needs trans_lock
>>
>
> I dropped this; I'm pretty sure its related to the leaked file
> descriptors in semodule t
>
I have the leak code fixed, but am still seeing this. I will try it
again without this code.
--
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-03-30 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 20:32 Latest policy Daniel J Walsh
2006-03-30 16:00 ` Christopher J. PeBenito
2006-03-30 16:37 ` Daniel J Walsh [this message]
2006-03-30 17:04 ` Stephen Smalley
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 5:27 Daniel J Walsh
2005-03-10 21:23 ` James Carter
2005-03-10 22:06 ` Thomas Bleher
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=442C0940.5050800@redhat.com \
--to=dwalsh@redhat.com \
--cc=cpebenito@tresys.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.