From: dwalsh@redhat.com (Daniel J Walsh)
Date: Wed, 28 Oct 2009 09:59:57 -0400
Subject: [refpolicy] Tgtd policy
In-Reply-To: <1256737769.20466.2.camel@home.localdomain>
References: <1256475709.3640.8.camel@localhost>	<4AE5C2CF.5010307@redhat.com>
	<1256722688.3622.14.camel@localhost>	<4AE83E1C.3040003@redhat.com>	<1256736503.20466.1.camel@home.localdomain>	<4AE84A80.5050001@redhat.com>
	<1256737769.20466.2.camel@home.localdomain>
Message-ID: <4AE84E5D.4000201@redhat.com>
To: refpolicy@oss.tresys.com
List-Id: refpolicy.oss.tresys.com

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