File: //usr/share/setroubleshoot/plugins/filesystem_associate.pyo
�
c�L]c @ s^ d d l Z e j d d e �Z e j Z d d l Td d l m Z d e f d � � YZ d S( i����Ns setroubleshoot-pluginst fallback( t *( t Plugint pluginc B sb e Z e d � Z e d � Z e d � Z e d � Z e d � Z e d � Z d � Z d � Z
RS( sq
SELinux is preventing $SOURCE_PATH from creating a file with a context of $SOURCE_TYPE on a filesystem.
s
SELinux is preventing $SOURCE from creating a file with a context of $SOURCE_TYPE on a filesystem.
Usually this happens when you ask the cp command to maintain the context of a file when
copying between file systems, "cp -a" for example. Not all file contexts should be maintained
between the file systems. For example, a read-only file type like iso9660_t should not be placed
on a r/w system. "cp -p" might be a better solution, as this will adopt the default file context
for the destination.
sX
Use a command like "cp -p" to preserve all permissions except SELinux context.
sT If you believe $SOURCE_BASE_PATH should be allowed to create $TARGET_BASE_PATH filesss you need to use a different command. You are not allowed to preserve the SELinux context on the target file system.sN use a command like "cp -p" to preserve all permissions except SELinux context.c C s! t j | t � | j d � d S( Nid ( R t __init__t __name__t set_priority( t self( ( s9 /usr/share/setroubleshoot/plugins/filesystem_associate.pyR 0 s c C sZ | j d g � rR | j d g � rR | j j t k rR | j d g � rR | j � Sd Sd S( Ns .*fs_tt associatet
filesystem( t matches_target_typest all_accesses_are_int tcontextt typet
file_typest
has_tclass_int reportt None( R t avc( ( s9 /usr/share/setroubleshoot/plugins/filesystem_associate.pyt analyze4 s
( R t
__module__t _t summaryt problem_descriptiont fix_descriptiont if_textt then_textt do_textR R ( ( ( s9 /usr/share/setroubleshoot/plugins/filesystem_associate.pyR s ( t gettextt translationt TrueR t setroubleshoot.utilt setroubleshoot.PluginR R ( ( ( s9 /usr/share/setroubleshoot/plugins/filesystem_associate.pyt <module> s