← Back
Editing: allow_execstack.cpython-312.pyc
� �Z`� � � � d dl Z e j dd�� Zej Zd dl� d dlmZ d dlZd dlZd� Zd� Z G d � d e� Z y) � Nzsetroubleshoot-pluginsT)�fallback)�*)�Pluginc � � | d dk7 ry t j dd| gd�� j � }|d dk( S # Y yxY w) Nr �/F� execstackz-qT��universal_newlines�X)� subprocess� check_output�split)�path�xs �4/usr/share/setroubleshoot/plugins/allow_execstack.py� is_execstackr sR � � �A�w�#�~��� � #� #�[�4��$>�SW� X� ^� ^� `�� �q�T�S�[�����s �(; �?c � � g } t j d| gd�� j � }|D ]$ }t |� s�||vs�|j |� �& t d|z d� }|j � D ]9 }|j � D ]$ }t |� s�||vs�|j |� �& �; |S # |cY S xY w# t $ r Y |S w xY w)N�lddTr z /proc/%s/maps�r)r r r r �append�open� readlines�IOError)�exe�pid� execstacklist�pathsr �fd�recs r �find_execstackr ' s� � ��M� ��'�'��� ��N�T�T�V�� �� �� �$�m�";� � � �� &� � � �/�C�'�#� .���<�<�>�C�� � � �� ��%�$�m�*C�!�(�(��.� $� "� ��� � � �� � � � �� �s* �'B3 �A B< �B< �B< �3B9�< C �C c � � e Zd Z ed� Z ed� Z ed� ZdZ ed� Z ed� Z ed� Z d� Z d � Z d � Z d � Zd � Zy )�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 �l � |d }|s | j S t d� |z S # | j cY S xY w)Nr z4If you believe that %s should not require execstack)�if_text�_��self�avc�argsr s r � get_if_textzplugin.get_if_text] s@ � � ���7�D���|�|�#��M�N�QU�U� U�� ��<�<� �� �# � # �3c �l � |d }|s | j S t d� |z S # | j cY S xY w)Nr z�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& r' s r � get_then_textzplugin.get_then_textg sP � � "���7�D���~�~�%�� p� q� tx� x� x�� "��>�>� !�r, c �l � |d }|s | j S t d� |z S # | j cY S xY w)Nr zexecstack -c %s)�do_textr& r' s r � get_do_textzplugin.get_do_textp s? � � ���7�D���|�|�#��&�'�$�.� .�� ��<�<� �r, c �8 � t j | t � y )N)r �__init__�__name__)r( s r r4 zplugin.__init__z s � �����X�&� c �" � |j g d�� r||j dg� rjg }t |j |j � D ]$ }|j | j ||f� � �& t |� dkD r|S | j d� S y )N)� unconfined_t�staff_t�user_t�guest_t�xguest_tr r )NN)�matches_source_types�has_any_access_inr �spathr r �report�len)r( r) �reports�is r �analyzezplugin.analyze} s} � � � $� $�%a� b� � � �+� � /��G�#�C�I�I�s�w�w�7�����t�{�{�A�c�7� 3�4� 8� �7�|�a� � ���;�;�{�+� +�r6 N)r5 � __module__� __qualname__r& �summary�problem_description�fix_description�fix_cmdr% r. r1 r+ r/ r2 r4 rD � r6 r r" r" ; su � � � � �G� � � �� � � �O� �G��x�y�G��W�X�I��L�M�G� �"� �'� r6 r" ) �gettext� translationr& �setroubleshoot.util�setroubleshoot.Pluginr r �sysr r r" rK r6 r �<module>rQ sN ��& � �G� � � 8�4� H� � ���� !� (� � ���(N�V� Nr6
Save File
Cancel