⚝
One Hat Cyber Team
⚝
Your IP:
216.73.216.55
Server IP:
97.74.87.16
Server:
Linux 16.87.74.97.host.secureserver.net 5.14.0-503.38.1.el9_5.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Apr 18 08:52:10 EDT 2025 x86_64
Server Software:
Apache
PHP Version:
8.2.28
Buat File
|
Buat Folder
Eksekusi
Dir :
~
/
var
/
opt
/
nydus
/
ops
/
primordial
/
__pycache__
/
View File Name :
fileutils.cpython-39.pyc
a ���g � @ s| d dl Z d dlZd dlZd dlZd dlmZmZmZ zd dlm Z W n e yV Y n0 zd dl m Z W n e yz Y n0 d dl mZ d dlZzd dlZd dlZW n e y� Y n0 d dlmZmZ dZdZe�e�Ze j ed �d d �Z d e eeeef dd �d d�Z e dd�dd�Z e dd�dd�Z e edd�dd�Z!d e eee dd�dd�Z"d e eee ee dd�d d �Z#dS )!� N)�Any�Optional�Tuple)�getpwnam)�getgrnam)�rmtree)�get_file_group� get_file_userg �?� )�in_time�returnc C s t | t�ddd� �� �S )zpReturn integer seconds since epoch. :param in_time: Datetime :returns: Integer seconds since epoch i� � )�int�datetime� total_seconds)r � r �E/opt/nydus/tmp/pip-target-mke_irhy/lib/python/primordial/fileutils.py�datetime_to_epoch_seconds# s r )�filename�timesr c C s: t | d�� t�| |� W d � n1 s,0 Y dS )a0 Set the atime and mtime of a file. .. note:: Linux (MAYBE Windows) ONLY. This does not work on Mac OSX. :param filename: The file to touch :param times: a two-tuple of (atime, mtime) where these are integer seconds since epoch; see os.utimes :raises OSError: if file doesn't exist �aN)�open�os�utime)r r r r r �touch, s r )�pathr c C sD z t | � W n2 ty> } ztd| �|�W Y d}~n d}~0 0 dS )zySimple rmtree wrapper :param path: path to recursively remove :raises: IOError if the path can't be removed �Failed to remove %sN)r �OSError�IOError)r �er r r �rm_path: s r )r r c C sF zt �| � W n2 ty@ } ztd| �|�W Y d}~n d}~0 0 dS )zuSimple remove wrapper :param filename: filename to remove :raises: IOError if the file can't be removed r N)r �remover r )r r r r r �rm_fileF s r" )r �datar c C s> t jtj�| �d�\}}t�|d�}t|�}z�z|�t|�� d�� W nj t y| } z t d| |f �|�W Y d}~n>d}~0 t y� } z t d| |f �|�W Y d}~n d}~0 0 W |� � n |� � 0 t�|�}|j|kr�t d||j|f ��zt�|| � W n8 t �y8 } z t d| |f �|�W Y d}~n d}~0 0 dS )z*A utility helper for the atomic file utils)�dir�wb�utf8z$Failed to write data to path %s (%s)Nz1Unexpectedly failed to write data to path %s (%s)z4Failed to write correct number of bytes (%s, %s, %s))�tempfile�mkstempr r �dirname�fdopen�len�write�str�encoder r � Exception�close�stat�st_size�rename)r r# Zoutfile_handleZ tmpfilename�outfileZdatalenr Z stat_structr r r � _write_fileR s& &* �r5 )r r# �add_all_access_userr c C s� t j�| �rt| � t| |� |dur~t�d|�\}}}t�| tj�}|� � }|� tj t j |� |�d|d� t�| tj|� dS )a4 Safely/atomically write a file on Windows. Write a file in such a way that the data is guaranteed to be complete and not intermixed with that of another process. This implementation will NOT clobber the target file if it exists already; instead, it will fail immediately. This is a windows-specific implementation that has Windows locking semantics for open file handles and rather than changing the file's ownership, setting add_all_access_user will cause the file to have a read-write ACE added to the ACL for the directory/file for the target user. Note that in both this function and atomically_write_file, the fact that the file has locking or not at the OS level is NOT being relied on in e.g. archon's file utilities for leasing or exclusive access. Instead, this implementation uses tmpfile to guarantee uniqueness of the source of information, and then a simple atomic mv to replace the destination. Windows, unlike Linux, could support a true OS level file locking layer for exclusive access, and so a future Windows specific file utility would be feasible for true single-host, global locking for use in e.g. archon. From https://stackoverflow.com/questions/12168110/setting-folder-permissions-in-windows-using-python :param filename: filename to write :param data: data to put in file :param add_all_access_user: the user if any to add a FILE_ALL_ACCESS ACE for :raises pywintypes.error: on failure to modify the file's ACL; pywintypes.error on user not found; pywintypes.error on file not found N� r r )r r �existsr" r5 � win32securityZLookupAccountNameZGetFileSecurityZDACL_SECURITY_INFORMATIONZGetSecurityDescriptorDaclZAddAccessAllowedAceZ ACL_REVISION�conZFILE_ALL_ACCESSZSetSecurityDescriptorDaclZSetFileSecurity)r r# r6 Zuserx�_Zfile_sdZdaclr r r �win_atomically_write_filel s r< )r r# � file_owner� file_groupr c C s\ t | |� d}|pt� }|dur*t|�j}d}|p6t� }|durJt|�j}t�| ||� dS )a Safely/atomically write a file. Write to a tmpfile then do os.rename(); Note that this is for Unix systems only, as the implicit contract is that the destination might exist and will be overwritten. This contract is violated on Windows. Also even on Unix, the file system of the source and dest must be the same; since we're in the same directory for this move, that constraint is satisfied. We use tempfile to make it so that we don't collide on the source tmp write -- different processes or threads will not select the same tmpfile. Last man in wins for the move -- there's no general way to sync this across processes or hosts using a filesystem store. :param filename: filename to ultimately write :param data: data to put in file :param file_owner: If set, will change file to this owner if permission is available :param file_group: If set, will change file to this group if permission is available :raises: IOError on failure; OSError on permission change without appropriate permissions ���N) r5 r r �pw_uidr r �gr_gidr �chown)r r# r= r> �file_uidZfile_group_gidr r r �atomically_write_file� s rD )N)N)NN)$r �loggingr �os.path�typingr r r �pwdr � ImportError�grpr �shutilr r' r9 Z ntsecurityconr: Zprimordial.settingsr r ZDELAY_INCREASE_SECSZ MAX_RETRIES� getLogger�__name__�LOGGERr r r- r r r" r5 r< rD r r r r �<module> sJ & ��