All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: "Christopher J. PeBenito" <cpebenito@tresys.com>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Application_domain
Date: Tue, 07 Aug 2007 09:47:17 -0400	[thread overview]
Message-ID: <46B877E5.6030002@redhat.com> (raw)
In-Reply-To: <1186491980.18881.15.camel@gorn>

Christopher J. PeBenito wrote:
> On Thu, 2007-08-02 at 11:35 -0400, Daniel J Walsh wrote:
>   
>> My definition of the application domain, is any file that a normal
>> user is expected to execute.   It can either have a  transition or
>> not.  If I define application_domain then it will transition.  If I
>> just define application_executable_file, then logged in users can
>> execute it without a transition.
>>
>> Daemons for the most part should NOT be application_domains.   This
>> way we can dontaudit getattr of daemons that users would/should not be
>> allowed to execute.
>>
>> Some applictions can be in both domains.  For example cvs, rsync can
>> be run without transitioning by users but when run from an initscript
>> they transition.
>>
>> This patch makes changes to the pool to match this.
>>     
>
> If you look back at what you're changing, init_system_domains() are all
> apps, so the call is in that interface.  Your patch undoes this.
>
>   
Ok I guess your right, even though some of these being user executables 
is a little shaky.

Reverting patch in rawhide.

--
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:[~2007-08-07 13:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-02 15:35 Application_domain Daniel J Walsh
2007-08-07 13:06 ` Application_domain Christopher J. PeBenito
2007-08-07 13:47   ` 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=46B877E5.6030002@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.