All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: David Hampton <hampton-rh@rainbolthampton.net>
Cc: fedora-selinux-list@redhat.com, selinux@tycho.nsa.gov
Subject: Re: New policy for yam
Date: Thu, 17 Mar 2005 14:30:31 -0500	[thread overview]
Message-ID: <4239DAD7.8030803@redhat.com> (raw)
In-Reply-To: <1110912692.14212.29.camel@hampton-pc.rainbolthampton.net>

David Hampton wrote:

>On Tue, 2005-03-15 at 09:20 -0500, Daniel J Walsh wrote:
>
>  
>
>>Why did you create a yam_crond_t?  Why not just transition to yam_t from 
>>crond?
>>    
>>
>
>When I first started working on the policy I was trying to be as
>restrictive as possible and differentiate between what peripheral files
>could be opened when running yam from the command line vs. when running
>from cron.  For example, the cron version requires less access to the
>terminal and no access to a ssh file descriptor.  The two instances also
>try reading their dot files from different directories.
>
>I wrote this policy just after writing an exim policy that distinguished
>between user, sysadm, and system invocations of the program.  Perhaps I
>went overboard here.
>
>David
>
>P.S. I'm still tweaking the exim policy.  I'll probably post it in a
>week or so.
>
>
>  
>
I was just question almost doubling of rules and increase in complexity 
for little gain in security.

Dan


-- 



--
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-03-17 19:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-12 23:50 New policy for yam David Hampton
2005-03-15 14:20 ` Daniel J Walsh
2005-03-15 18:51   ` David Hampton
2005-03-17 19:30     ` Daniel J Walsh [this message]

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=4239DAD7.8030803@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=fedora-selinux-list@redhat.com \
    --cc=hampton-rh@rainbolthampton.net \
    --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.