o .j @sbddlmZddlZddlZddlZddlZddlZddlmZej r'ddl Z  ddddZ dS)) annotationsN)UnsupportedOperationctxssl.SSLContextcertdata str | byteskeydatastr | bytes | Nonepassword5typing.Callable[[], str | bytes] | str | bytes | NonereturnNonec sttds tdt|tr|d}|dur!t|tr!|d}tjdd}tj |d}|dur9tj |dnd}zt |t j t j B|durTt |t j t j Bddfdd }tj|||fdd}|d} |dur|durtj|||fdd} | |j|||d|j dd| dur| j dddurtdW||fD]} | durzt| WqtyYqwqzt|WdStyYdSw||fD]} | durzt| WqtyYqwqzt|WwtyYww)aLoad cert chain using named pipes (FIFOs) instead of shm (linux). Creates temporary FIFOs, feeds PEM data through background threads, and lets ssl.SSLContext.load_cert_chain read from them. Data flows through kernel pipe buffers without ever touching disk. A single FIFO would deadlock on the second open. The idea came from https://github.com/jawah/urllib3.future/issues/325#issuecomment-4069433443 :raise UnsupportedOperation: If anything goes wrong in the process. mkfifozhUnable to provide support for in-memory client certificate: os.mkfifo is not available on this platform.asciiN urllib3_imcc_)prefixz cert.fifozkey.fifopathstrdatabytesr r c sjzt|d}||WdWdS1swYWdSty4}z |WYd}~dSd}~ww)Nwb)openwrite BaseException)rrfe writer_excV/home/thesage/.local/lib/python3.10/site-packages/urllib3_future/contrib/imcc/_fifo.py _write_fifo7s  &z$load_cert_chain.._write_fifoT)targetargsdaemon)keyfiler g?)timeoutzPUnable to provide support for in-memory client certificate: FIFO writer failed: )rrrrr r )hasattrosr isinstancerencodetempfilemkdtemprjoinrstatS_IRUSRS_IWUSR threadingThreadstartload_cert_chainunlinkOSErrorrmdir) rrrr tmpdir cert_fifokey_fifor cert_thread key_threadprrrr3s              r3)NN) rrrrrr r r r r ) __future__rr'r-r*r0typingior TYPE_CHECKINGsslr3rrrrs