KGRKJGETMRETU895U-589TY5MIGM5JGB5SDFESFREWTGR54TY
Server : Apache/2.2.17 (Unix) mod_ssl/2.2.17 OpenSSL/0.9.8e-fips-rhel5 DAV/2 PHP/5.2.17
System : Linux localhost 2.6.18-419.el5 #1 SMP Fri Feb 24 22:47:42 UTC 2017 x86_64
User : nobody ( 99)
PHP Version : 5.2.17
Disable Function : NONE
Directory :  /proc/21573/root/usr/share/setroubleshoot/plugins/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Current File : //proc/21573/root/usr/share/setroubleshoot/plugins/mislabeled_file.pyo
mò

¡8Hc@sRdkZeidddeƒiZdkTdklZdefd„ƒYZdS(Nssetroubleshoot-pluginss/usr/share/localetfallback(t*(sPlugintplugincBsDtZedƒZedƒZedƒZdZd„Zd„ZRS(Ns`
    SELinux is preventing $SOURCE ($SOURCE_TYPE) "$ACCESS" to $TARGET_PATH ($TARGET_TYPE).
    sã
    SELinux is preventing $SOURCE ($SOURCE_TYPE) "$ACCESS" to $TARGET_PATH ($TARGET_TYPE).
    The SELinux type $TARGET_TYPE, is a generic type for all files in the directory and very few processes (SELinux Domains) are allowed to write to this SELinux type.  This type of denial usual indicates a mislabeled file.  By default a file created in a directory has the gets the context of the parent directory, but SELinux policy has rules about the creation of directories, that say if a process running in one SELinux Domain (D1) creates a file in a directory with a particular SELinux File Context (F1) the file gets a different File Context (F2).  The policy usually allows the SELinux Domain (D1) the ability to write, unlink, and append on (F2).  But if for some reason a file ($TARGET_PATH) was created with the wrong context, this domain will be denied.  The usual solution to this problem is to reset the file context on the target file, restorecon -v '$TARGET_PATH'.  If the file context does not change from $TARGET_TYPE, then this is probably a bug in policy.  Please file a <a href="http://bugzilla.redhat.com/bugzilla/enter_bug.cgi">bug report</a> against the selinux-policy package.
If it does change, you can try your application again to see if it works.  The file context could have been mislabeled by editing the file or moving the file from a different directory, if the file keeps getting mislabeled, check the init scripts to see if they are doing something to mislabel the file.  
 
    sW
    You can attempt to fix file context by executing restorecon -v '$TARGET_PATH'
    srestorecon '$TARGET_PATH'cCs!ti|tƒ|idƒdS(Ni7(tPlugint__init__tselft__name__tset_priority(R((t4/usr/share/setroubleshoot/plugins/mislabeled_file.pyR+scCsšddddg}|iddddd	d
dgƒo[|idd
dgƒoB|i|ƒo2|i|tdƒ|i|i	|i
|iƒSndSdS(Ntdirtfiletlnk_filet	sock_filet	var_log_tt	var_lib_ttetc_ttroot_tt
var_lock_tt	var_run_ttvar_spool_ttwritetappendtunlinks
File Label(
trestorecon_filestavctmatches_target_typestall_accesses_are_int
has_tclass_inRtreportt_tsummarytproblem_descriptiontfix_descriptiontfix_cmdtNone(RRR((Rtanalyze/sN(	Rt
__module__RRRR R!RR#(((RRs	(	tgettextttranslationtTruetlgettextRtsetroubleshoot.utiltsetroubleshoot.PluginRR(RRR%R((Rt?s	


Anon7 - 2021