Your IP : 216.73.217.2

Current Path : /usr/share/setroubleshoot/plugins/__pycache__/
Upload File :
Current File : //usr/share/setroubleshoot/plugins/__pycache__/allow_execstack.cpython-36.pyc

3

nm�a��@sdddlZejddd�ZejZddlTddlmZddlZddlZdd�Zd	d
�Z	Gdd�de�Z
dS)
�Nzsetroubleshoot-pluginsT)Zfallback)�*)�Pluginc
CsD|ddkrdSytjdd|gdd�j�}Wn
dS|ddkS)	Nr�/F�	execstackz-qT)�universal_newlines�X)�
subprocess�check_output�split)�path�x�r
�4/usr/share/setroubleshoot/plugins/allow_execstack.py�is_execstacksrcCs�g}ytjd|gdd�j�}Wn
|Sx&|D]}t|�r0||kr0|j|�q0WyPtd|d�}x<|j�D]0}x*|j�D]}t|�rz||krz|j|�qzWqlWWntk
r�YnX|S)NZlddT)rz
/proc/%s/maps�r)rr	r
r�append�open�	readlines�IOError)Zexe�pidZ
execstacklist�pathsr�fdZrecr
r
r�find_execstack's"
rc@sheZdZed�Zed�Zed�ZdZed�Zed�Z	ed�Z
dd	�Zd
d�Zdd
�Z
dd�Zdd�ZdS)�pluginzV
    SELinux is preventing $SOURCE_PATH from making the program stack executable.
    a#
    The $SOURCE application attempted to make its stack
    executable.  This is a potential security problem.  This should
    never ever be necessary. Stack memory is not executable on most
    OSes these days and this will not change. Executable stack memory
    is one of the biggest security problems. An execstack error might
    in fact be most likely raised by malicious code. Applications are
    sometimes coded incorrectly and request this permission.  The
    <a href="http://people.redhat.com/drepper/selinux-mem.html">SELinux Memory Protection Tests</a>
    web page explains how to remove this requirement.  If $SOURCE does not
    work and you need it to work, you can configure SELinux
    temporarily to allow this access until the application is fixed. Please
file a bug report.
    a6
    Sometimes a library is accidentally marked with the execstack flag,
    if you find a library with this flag you can clear it with the
    execstack -c LIBRARY_PATH.  Then retry your application.  If the
    app continues to not work, you can turn the flag back on with
    execstack -s LIBRARY_PATH.
    �zfIf you do not think $SOURCE_PATH should need to map stack memory that is both writable and executable.zByou need to report a bug. 
This is a potentially dangerous access.z:Contact your security administrator and report this issue.c	Cs0y|d}|s|jStd�|S|jSdS)Nrz4If you believe that 
%s
should not require execstack)�if_text�_)�self�avc�argsrr
r
r�get_if_text]szplugin.get_if_textc	Cs0y|d}|s|jStd�|S|jSdS)Nrz�you should clear the execstack flag and see if $SOURCE_PATH works correctly.
Report this as a bug on %s.
You can clear the exestack flag by executing:)�	then_textr)rrrrr
r
r�
get_then_textgszplugin.get_then_textc	Cs0y|d}|s|jStd�|S|jSdS)Nrzexecstack -c %s)�do_textr)rrrrr
r
r�get_do_textpszplugin.get_do_textcCstj|t�dS)N)r�__init__�__name__)rr
r
rr%zszplugin.__init__cCsr|jdddddg�rj|jdg�rjg}x*t|j|j�D]}|j|j||f��q4Wt|�dkr`|S|jd�SdSdS)	NZunconfined_tZstaff_tZuser_tZguest_tZxguest_trr)NN)Zmatches_source_typesZhas_any_access_inrZspathrrZreport�len)rrZreports�ir
r
r�analyze}s
zplugin.analyzeN)r&�
__module__�__qualname__rZsummaryZproblem_descriptionZfix_descriptionZfix_cmdrr!r#r r"r$r%r)r
r
r
rr;s

	
r)�gettextZtranslationrZsetroubleshoot.utilZsetroubleshoot.Pluginrr�sysrrrr
r
r
r�<module>s