cupsd & targeted....

[Daniel J Walsh]

Daniel J Walsh wrote:

> Tim Waugh wrote:
>
>> On Thu, May 19, 2005 at 07:43:39AM -0700, Tom London wrote:
>>
>>  
>>
>>> Some read/write avcs are for /var/foomatic/printconf.pickle. Is there
>>> an appropriate type for this (other than var_t)?
>>>   
>>
>>
>> The /var/foomatic/printconf.pickle file is just the contents of the
>> /var/foomatic/db directory cached in a format that
>> system-config-printer can read more quickly.
>>
>> It is written (or at least, this is attempted) whenever the foomatic
>> data itself is read -- in other words, whenever the cache file would
>> have been useful.
>>
>>  
>>
> Why is cupsd_config trying to write to it?
>
>> This happens in all users of printconf_conf:
>>
>> * system-config-printer
>> * printconf-backend (cups initscript, RPM %postinstall scriptlets)
>> * updateconf.py (RPM %postinstall scriptlets)
>>
>> Tim.
>> */
>>  
>>
>> ------------------------------------------------------------------------
>>
>> -- 
>> fedora-selinux-list mailing list
>> fedora-selinux-list at redhat.com
>> http://www.redhat.com/mailman/listinfo/fedora-selinux-list
>>
>
>
Anyways should  /var/foomatic/printconf.pickle be marked cupsd_rw_etc_t.

Meaning this is something that is created by cups for use by cups?

And is that the correct directory or should it be /var/cache/...

Dan

--