⚝
One Hat Cyber Team
⚝
Your IP:
216.73.216.30
Server IP:
45.79.8.107
Server:
Linux localhost 5.15.0-140-generic #150-Ubuntu SMP Sat Apr 12 06:00:09 UTC 2025 x86_64
Server Software:
nginx/1.18.0
PHP Version:
8.1.2-1ubuntu2.21
Buat File
|
Buat Folder
Eksekusi
Dir :
~
/
lib
/
python3
/
dist-packages
/
cloudinit
/
__pycache__
/
View File Name :
gpg.cpython-310.pyc
o }f @ st d Z ddlZddlZddlZddlZddlZddlmZ ddlm Z m Z ddl m Z e eZdZG dd dZdS ) z0gpg.py - Collection of gpg key related functions N)TemporaryDirectory)DictOptional)subp GNUPGHOMEc @ s e Zd Zdd Zdd Zedeeef fddZdd Z d"d d Z d ede e fddZ d edefddZ d#dedefddZd$d ededd fddZd edd fddZ d%d edede e fd d Zd"d d!Zd S )&GPGc C s d| _ i | _t | _d S )NF) gpg_started_envr temp_dirself r //usr/lib/python3/dist-packages/cloudinit/gpg.py__init__ s z GPG.__init__c C s | S Nr r r r r __enter__ s z GPG.__enter__returnc C s& | j r| j S d| _t| jji| _ | j S )a when this env property gets invoked, set up our temporary directory, and also set gpg_started to tell the cleanup() method whether or not why put this here and not in __init__? pytest seems unhappy and it's not obvious how to work around it T)r r HOMEr namer r r r env" s zGPG.envc C s | d S r )cleanup)r exc_typ exc_value tracebackr r r __exit__1 s z GPG.__exit__Nc C s4 | | jrtj| jjr| j dS dS dS )z0cleanup the gpg temporary directory and kill gpgN)kill_gpgr ospathisdirr r r r r r r 4 s z GPG.cleanupkeyc C sV zt j ddd|gd| jdjW S t jy* } ztd|| W Y d}~dS d}~ww )z*Export gpg key, armoured key gets returnedgpgz--exportz--armourTcapture update_env&Failed to export armoured key "%s": %sN)r r stdoutProcessExecutionErrorLOGdebugr r errorr r r export_armour: s zGPG.export_armourc C s t j ddg|d| jdjS )zDearmor gpg key, dearmored key gets returned note: man gpg(1) makes no mention of an --armour spelling, only --armor r z --dearmorF)datadecoder# )r r r% )r r r r r dearmorG s z GPG.dearmorFkey_filec C sL g d}|s | d | | tj|| jdd\}}|r$td|| |S )zList keys from a keyring with fingerprints. Default to a stable machine parseable format. @param key_file: a string containing a filepath to a key @param human_output: return output intended for human parsing )r z --no-optionsz--with-fingerprintz--no-default-keyringz --list-keysz --keyringz --with-colonsT)r# r" r$ )appendr r r' warning)r r/ human_outputcmdr% stderrr r r list_keysP s z GPG.list_keys r7 keyserverc C s t d|| d}d}t|pg } |d7 }ztjddd| d |gd| jd t d ||| W dS tjyF } z|}W Y d}~nd}~ww zt|}t d |j| t | W n t yq } z t d ||||f |d}~ww q)a Receive gpg key from the specified keyserver. Retries are done by default because keyservers can be unreliable. Additionally, there is no way to determine the difference between a non-existent key and a failure. In both cases gpg (at least 2.2.4) exits with status 2 and stderr: "keyserver receive failed: No data" It is assumed that a key provided to cloud-init exists on the keyserver so re-trying makes better sense than failing. @param key: a string key fingerprint (as passed to gpg --recv-keys). @param keyserver: the keyserver to request keys from. @param retries: an iterable of sleep lengths for retries. Use None to indicate no retries.z&Importing key '%s' from keyserver '%s'r NTr7 r z--no-ttyz--keyserver=%sz --recv-keysr! z/Imported key '%s' from keyserver '%s' on try %dz6Import failed with exit code %d, will try again in %ssz@Failed to import key '%s' from keyserver '%s' after %d tries: %s) r' r( iterr r r& next exit_codetimesleep StopIteration ValueError) r r r8 retriestrynumr* sleepsenaplenr r r recv_keyj s^ z GPG.recv_keyc C sZ zt j dddd|gd| jd W dS t jy, } ztd|| W Y d}~dS d}~ww ) z0Delete the specified key from the local gpg ringr z--batchz--yesz --delete-keysTr! zFailed delete key "%s": %sN)r r r& r' r1 r) r r r delete_key s zGPG.delete_keykeyserver.ubuntu.comkeyidc C sj | |}|s3z%z| j||d | |}W n ty$ td| w W | | |S | | w |S )z get gpg keyid from keyserver)r8 zFailed to obtain gpg key %s)r+ rE r? r' exceptionrF )r rH r8 armourr r r getkeybyid s zGPG.getkeybyidc C s zK| j sW dS tdrtjg dd| jdj}W dS tjg ddddgd j}td |}d d |D }|r=td | |D ] }t |t j q?W dS tj ye } z td| W Y d}~dS d}~ww )a killing with gpgconf is best practice, but when it isn't available failover is possible GH: 4344 - stop gpg-agent/dirmgr daemons spawned by gpg key imports. Daemons spawned by cloud-config.service on systemd v253 report (running) Ngpgconf)rL z--killallTr! ) psz-ozppid,pid-CkeyboxdrO dirmngrrO z gpg-agentr r7 )r" rcsz (?P<ppid>\d+)\s+(?P<pid>\d+)c S s$ g | ]}|d dkrt |d qS )r 1r7 )int).0pidr r r <listcomp> s z GPG.kill_gpg.<locals>.<listcomp>z&Killing gpg-agent and dirmngr pids: %sz"Failed to clean up gpg process: %s)r r whichr r% refindallr' r( r killsignalSIGKILLr& r1 )r gpg_process_outgpg_pids root_gpg_pidsgpg_pidrC r r r r sF z GPG.kill_gpg)r N)F)r6 )rG )__name__ __module__ __qualname__r r propertyr strr r r r r+ r. r5 rE rF rK r r r r r r s* 7 r )__doc__loggingr rY r\ r< tempfiler typingr r cloudinitr getLoggerrb r' r r r r r r <module> s