"·T`d ã@s{dZddlmZddlmZddlZejeƒZdd„Z ddd „Z d d „Z d d d„Z dS)z0gpg.py - Collection of gpg key related functionsé)Úlog)ÚsubpNcCssy+tjddd|gddƒ\}}WnAtjk rn}ztjd||ƒd}WYdd}~XnX|S)z*Export gpg key, armoured key gets returnedÚgpgz--exportz--armourÚcaptureTz&Failed to export armoured key "%s": %sN)rÚProcessExecutionErrorÚLOGÚdebug)ÚkeyÚarmourÚ_Úerror©r ú//usr/lib/python3/dist-packages/cloudinit/gpg.pyÚ export_armoursréc CsGtjd||ƒddd|d|g}|dkr>g}d}d}t|ƒ}xê|d7}y1tj|d d ƒtjd |||ƒdSWn.tjk rÄ}z |}WYdd}~XnXy3t|ƒ}tjd |j|ƒtj|ƒWqYt k r>}z$t d ||||fƒ|‚WYdd}~XqYXqYWdS)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-existant 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'rz--no-ttyz--keyserver=%sz --recv-keysNrrrTz/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) rrÚiterrrÚnextZ exit_codeÚtimeZsleepÚ StopIterationÚ ValueError) r Ú keyserverZretriesÚcmdZtrynumr ZsleepsÚeZnaplenr r rÚrecv_keys6       rcCshy&tjdddd|gddƒWn;tjk rc}ztjd||ƒWYdd}~XnXdS) z0Delete the specified key from the local gpg ringrz--batchz--yesz --delete-keysrTzFailed delete key "%s": %sN)rrrZwarning)r r r r rÚ delete_keyIs  rzkeyserver.ubuntu.comcCspt|ƒ}|slzLy t|d|ƒt|ƒ}Wn%tk r\tjd|ƒ‚YnXWdt|ƒX|S)zget gpg keyid from keyserverrzFailed to obtain gpg key %sN)rrrrZ exceptionr)Zkeyidrr r r rÚ getkeybyidRs    r)rr) Ú__doc__Z cloudinitrZloggingrrZ getLoggerÚ__name__rrrrrr r r rÚs  +