F2j jddlmZddlZddlZddlZddlZddlZddlmZej rddl Z dddZ dS)) annotationsN)UnsupportedOperationctxssl.SSLContextcertdata str | byteskeydatastr | bytes | Nonepassword5typing.Callable[[], str | bytes] | str | bytes | NonereturnNonecF ttdstdt|tr|d}|*t|tr|d}t jd}tj |d}| tj |dnd} tj |tj tj z|,tj |tj tj zd d fd }tj|||fd}|d} |/|-tj|||fd} | ||||| d| | d td  ||fD]*} | & tj| #t&$rY&wxYw+ tj|dS#t&$rYdSwxYw#||fD]*} | & tj| #t&$rY&wxYw+ tj|w#t&$rYwwxYwxYw)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 rc t|d5}||ddddS#1swxYwYdS#t$r }|Yd}~dSd}~wwxYw)Nwb)openwrite BaseException)rrfe writer_excs b/home/thesage/.hermes/hermes-agent/venv/lib/python3.11/site-packages/urllib3/contrib/imcc/_fifo.py _write_fifoz$load_cert_chain.._write_fifo7s $%%"GGDMMM""""""""""""""""""      s2A6 A:A:A A AAT)targetargsdaemon)keyfiler g?)timeoutzPUnable to provide support for in-memory client certificate: FIFO writer failed: )rrrrr r)hasattrosr isinstancerencodetempfilemkdtemprjoinrstatS_IRUSRS_IWUSR threadingThreadstartload_cert_chainunlinkOSErrorrmdir) rrr r tmpdir cert_fifokey_fifor! cert_thread key_threadprs @r r4r4s@$ 2x  " ;   (C  ,??7++z'377..))  _ 5 5 5F V[11I3:3Frw||FJ///DH3 )T\DL8999   Ih t| ; < < <+/        &i%:4    .2  G$7")"(G)rEs""""""  ###### JJJ #'FJ TTTTTTTrD