From: Paul Howarth <paul@city-fan.org>
To: Chris PeBenito <pebenito@gentoo.org>
Cc: Dominick Grift <domg472@gmail.com>, selinux@tycho.nsa.gov
Subject: Re: [REFPOLICY PATCH] Added policy module for the oident daemon.
Date: Wed, 13 Aug 2008 15:25:39 +0100 [thread overview]
Message-ID: <48A2EEE3.1020909@city-fan.org> (raw)
In-Reply-To: <1218632939.5144.10.camel@defiant.pebenito.net>
Chris PeBenito wrote:
> On Sat, 2008-07-26 at 15:07 +0200, Dominick Grift wrote:
>> Signed-off-by: Dominick Grift <domg472@gmail.com>
>
> The patch looks line-wrapped. Also a couple comments inline.
...
>> +tunable_policy(`oidentd_read_unprivileged_user_home_content_files', `
>> + # ~/.oidentd.conf
>> + userdom_read_unpriv_users_home_content_files(oidentd_t)
>> +')
>
> Why is this last bit needed? Why would a system service be reading a
> conf file from a user's home dir?
It's reading ~/.oidentd.conf, which allows a user great control over the
responses the daemon returns when queried about connections related to
that user.
http://linux.die.net/man/5/oidentd.conf
Paul.
--
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:[~2008-08-13 14:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-26 13:07 [REFPOLICY PATCH] Added policy module for the oident daemon Dominick Grift
2008-08-13 13:08 ` Chris PeBenito
2008-08-13 14:25 ` Paul Howarth [this message]
2008-08-13 16:46 ` Dominick Grift
2008-08-13 16:50 ` Dominick Grift
2008-08-13 17:17 ` Dominick Grift
2008-08-13 17:35 ` Dominick Grift
2008-08-13 17:52 ` Dominick Grift
2008-08-14 11:37 ` Dominick Grift
2008-08-14 12:36 ` Dominick Grift
2008-08-14 13:28 ` Dominick Grift
2008-08-21 13:09 ` [refpolicy] " Christopher J. PeBenito
2008-08-21 14:55 ` Dominick Grift
2008-08-21 15:39 ` Dominick Grift
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=48A2EEE3.1020909@city-fan.org \
--to=paul@city-fan.org \
--cc=domg472@gmail.com \
--cc=pebenito@gentoo.org \
--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.