All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junji Kanemaru <linux@linuon.com>
To: SE Linux <selinux@tycho.nsa.gov>
Subject: dhcpd policy settings
Date: Tue, 12 Apr 2005 14:48:23 +0900	[thread overview]
Message-ID: <425B6127.3060808@linuon.com> (raw)

Hi,

I have problem with dhcpd that it seems some recent policy update
has affected dhcpd runtime environment.
dhcpd gets avc permission error when dhcpd accesses to 
/var/lib/dhcpd.leases.  The dmesg says:

audit(1113209633.019:0): avc:  denied  { search } for  
pid=5585 exe=/usr/sbin/dhcpd name=lib dev=dm-0 ino=1409026 
scontext=root:system_r:dhcpd_t tcontext=system_u:object_r:home_root_t
tclass=dir

So I quick looked into policy setting and found there's a type setting
in /etc/selinux/targeted/src/policy/file_contexts/file_contexts that
/var/lib is set to 'system_u:object_r:home_root_t' but 'dhcpd.te' doesn't
have permission to traverse 'home_root_t:dir'...
I added permission 'allow dhcpd_t home_root_t:dir { getattr search };' to
'dhcpd.te', the error has gone. 
But I'm not really sure if I did right thing or not, I'd like to hear from 
SELinux gurus if it is OK with this fix or there's some security exploit with
my fix, or there's complete fix...
Please enlighten me.

Thanks,

-- Junji

-- 
Junji Kanemaru
Linuon Inc.
Tokyo Japan

--
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.

             reply	other threads:[~2005-04-12  5:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-12  5:48 Junji Kanemaru [this message]
2005-04-12  7:26 ` dhcpd policy settings Junji Kanemaru
2005-04-12 12:25   ` Stephen Smalley
2005-04-12 13:41 ` Daniel J Walsh
2005-04-14 10:21   ` 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=425B6127.3060808@linuon.com \
    --to=linux@linuon.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.