All of lore.kernel.org
 help / color / mirror / Atom feed
From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] services_smartmon.patch
Date: Mon, 23 Mar 2009 14:14:24 -0400	[thread overview]
Message-ID: <49C7D180.90506@redhat.com> (raw)
In-Reply-To: <1237821858.6079.10.camel@gorn.columbia.tresys.com>

On 03/23/2009 11:24 AM, Christopher J. PeBenito wrote:
> On Thu, 2009-03-05 at 13:03 -0400, Daniel J Walsh wrote:
>> http://people.fedoraproject.org/~dwalsh/SELinux/F11/services_smartmon.patch
>>
>> smartmon needs to be ranged.
>>
>> Has the ability to create files with the correct context
>
> Why is this managing fixed disks?  I thought it was only monitoring
> disks.
>
Search for this line in the os_linux.cpp file

/* This function will setup and fix device nodes for a 3ware controller. */


We have had to add SELinux inteligence to make sure the device nodes are 
labelled correctly.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: os_linux.cpp
Url: http://oss.tresys.com/pipermail/refpolicy/attachments/20090323/ce909b78/attachment-0001.pl 

  reply	other threads:[~2009-03-23 18:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-05 17:03 [refpolicy] services_smartmon.patch Daniel J Walsh
2009-03-23 15:24 ` Christopher J. PeBenito
2009-03-23 18:14   ` Daniel J Walsh [this message]
2009-03-23 19:00     ` Christopher J. PeBenito
  -- strict thread matches above, loose matches on Subject: below --
2010-08-26 22:20 Daniel J Walsh
2009-11-12 22:00 Daniel J Walsh
2009-12-18 15:48 ` Christopher J. PeBenito
2009-06-09  1:08 Daniel J Walsh
2009-07-20 18:32 ` Christopher J. PeBenito
2008-09-24 20:00 Daniel J Walsh
2008-10-08 20:07 ` Christopher J. PeBenito
2008-10-09  0:53   ` Daniel J Walsh
2008-10-10 17:20     ` Christopher J. PeBenito
2008-10-14 15:04       ` Daniel J Walsh

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=49C7D180.90506@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=refpolicy@oss.tresys.com \
    /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.