From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Tgtd policy
Date: Wed, 28 Oct 2009 09:59:57 -0400 [thread overview]
Message-ID: <4AE84E5D.4000201@redhat.com> (raw)
In-Reply-To: <1256737769.20466.2.camel@home.localdomain>
On 10/28/2009 09:49 AM, Matthew Ife wrote:
> On Wed, 2009-10-28 at 09:43 -0400, Daniel J Walsh wrote:
>> On 10/28/2009 09:28 AM, Matthew Ife wrote:
>>> Tgtd is a iscsi target daemon for linux. Its eventually going to also do
>>> FCoE but currently doesnt.
>>>
>>> Heres my policy for it. It needs some cleanup and i've not tested it
>>> with proper fixed disk devices. I assume the kernel actually does most
>>> of the read/write of the devices itself so the block device access i've
>>> given the daemon is minimal.
>>>
>>> Any feedback appreciated.
>>>
>>>
>>>
>>>
>>>
>>> --
>>> fedora-selinux-list mailing list
>>> fedora-selinux-list at redhat.com
>>> https://www.redhat.com/mailman/listinfo/fedora-selinux-list
>> Better off sending policy to the refpolicy list
>
> Done
>
> --
> fedora-selinux-list mailing list
> fedora-selinux-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-selinux-list
>
>
Here is my fixes for your policy.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: tgtd.fc
Url: http://oss.tresys.com/pipermail/refpolicy/attachments/20091028/4c33929b/attachment.pl
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: tgtd.if
Url: http://oss.tresys.com/pipermail/refpolicy/attachments/20091028/4c33929b/attachment-0001.pl
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: tgtd.te
Url: http://oss.tresys.com/pipermail/refpolicy/attachments/20091028/4c33929b/attachment-0002.pl
parent reply other threads:[~2009-10-28 13:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1256737769.20466.2.camel@home.localdomain>]
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=4AE84E5D.4000201@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.