All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: ntp policy
Date: Wed, 07 Sep 2005 09:21:40 -0400	[thread overview]
Message-ID: <1126099300.13223.5.camel@sgc> (raw)
In-Reply-To: <431EDA31.9030502@redhat.com>

On Wed, 2005-09-07 at 08:16 -0400, Daniel J Walsh wrote:
> Christopher J. PeBenito wrote:
> 
> >While converting the ntpd policy over to a reference policy module, I
> >came across a few lines which bring up questions.
[cut]
> >	ifdef(`winbind.te', `
> >	allow ntpd_t winbind_var_run_t:dir r_dir_perms;
> >	allow ntpd_t winbind_var_run_t:sock_file rw_file_perms;
> >	')
> >
> >Generally when using a sock_file, a domain is connecting/sending to
> >another domain over a unix domain socket; however, after doing a few
> >rule searches in apol, I find no evidence that ntpd_t connects/sends to
> >winbind_t.  Is there some other purpose for these rules, or am I missing
> >something?
> >
> Must be from nscd.

I don't understand.  If that is the case, wouldn't it be nscd_var_run_t
instead of winbind_var_run_t?

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

  reply	other threads:[~2005-09-07 13:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-05 14:07 ntp policy Christopher J. PeBenito
2005-09-07 12:16 ` Daniel J Walsh
2005-09-07 13:21   ` Christopher J. PeBenito [this message]
2005-09-07 13:27     ` Daniel J Walsh
  -- strict thread matches above, loose matches on Subject: below --
2002-03-20 14:55 Russell Coker
2002-03-20 21:01 ` Stephen Smalley
2002-03-20 21:06   ` Stephen Smalley
2002-03-20 22:00   ` Russell Coker
2002-03-21 19:15     ` Stephen Smalley
2002-03-21 22:05       ` 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=1126099300.13223.5.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.