Wasu proxies na HTTPS na gaba suna neman takardar shaidar abokin ciniki yayin haɗin TLS daga Git zuwa proxy. Wannan musayar tabbaci ce dabam da shiga cikin ajiya.

Don ingantaccen tushen TLS na Git/libcurl da ke amfani da fayilolin PEM, daidaitaccen saitin yana da wannan siffa:

[http]
    proxy = https://proxy.example:8443
    proxySSLCAInfo = /secure/proxy-ca.pem
    proxySSLCert = /secure/proxy-client.pem
    proxySSLKey = /secure/proxy-client.key
    proxySSLCertPasswordProtected = true

Yi amfani da ainihin fayilolin da aka bayar don tsarin TLS na proxy. Yi amfani da saitin a matakin Git da aka nufa; saitin cikin gida na ajiya na iya taƙaita wannan hanyar ga wannan kwafin aiki kawai.

SaitiMatsayi
proxySSLCAInfoKunshin CA da ake amfani da shi don tabbatar da proxy na HTTPS
proxySSLCertTakardar shaidar abokin ciniki da aka gabatar wa wancan proxy
proxySSLKeyMaɓallin sirri da ya dace da takardar shaidar abokin ciniki
proxySSLCertPasswordProtectedYana ba da damar tambayar kalmar sirri ta Git don takardar shaidar proxy da kayan maɓalli masu kariya

URL ɗin proxy na https:// yana da mahimmanci ga wannan musayar TLS. Proxy na HTTP na fili da ke ɗaukar CONNECT zuwa ajiyar HTTPS ba ya yin tabbacin takardar shaidar abokin ciniki ta TLS a kan mai sauraronsa.

Amincewar takardar shaidar ajiya da duk wata takardar shaidar abokin ciniki ta ajiya suna da nasu saitin ssl. Haka nan, ƙalubalen proxy na HTTP ta amfani da Proxy-Authenticate wata hanya ce ta tabbaci.

Duba sigar libcurl da aka haɗa, tushen TLS da tsarin takardar shaidar da ake tallafawa yayin kula da wannan saitin. Hanyar zuwa takardar shaidar PEM ba ita ce madadin mai ɗaukuwa ga mu'amalar ajiyar takardun shaida ta kowace dandamali ba.

Labarai masu alaƙa