Re: fsdaemon writes files/disks at different levels, Needs write down.

[Daniel J Walsh <dwalsh@redhat.com>]

Christopher J. PeBenito wrote:
> On Mon, 2007-06-11 at 12:50 -0400, Daniel J Walsh wrote:
>   
>> Christopher J. PeBenito wrote:
>>     
>>> On Wed, 2007-05-30 at 10:22 -0400, dwalsh@redhat.com wrote:
>>>   
>>>       
>>>> --- nsaserefpolicy/policy/modules/services/smartmon.te	2007-05-29 14:10:57.000000000 -0400
>>>> +++ serefpolicy-3.0.1/policy/modules/services/smartmon.te	2007-05-30 09:08:15.000000000 -0400
>>>> @@ -60,6 +60,7 @@
>>>>  fs_search_auto_mountpoints(fsdaemon_t)
>>>>  
>>>>  mls_file_read_up(fsdaemon_t)
>>>> +mls_file_write_down(fsdaemon_t)
>>>>  
>>>>  storage_raw_read_fixed_disk(fsdaemon_t)
>>>>  storage_raw_write_fixed_disk(fsdaemon_t)
>>>>     
>>>>         
>>> Looks to me that all of the devices smartmon should care about
>>> (fixed_disk_device_t) are all system high, so I'm not sure why this is
>>> needed.
>>>
>>>   
>>>       
>> Writing its pid file?
>>     
>
> Perhaps the pid file should be systemhigh too.  It might be only the pid
> number in the file, but do we want to trust it write down when it has
> raw disk access?
>
>   
This is why I hate MLS :^(

The only files in /var/run that are SystemHigh right now are.

/var/run/setrans(/.*)?       
gen_context(system_u:object_r:setrans_var_run_t,mls_systemhigh)




--
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.