I-proxy ye-HTTPS ye-Git ingase idinge isitifiketi sekhasimende sayo

Hlela i-TLS CA yeproxy, isitifiketi sekhasimende kanye nokhiye wangasese ngokuhlukile kuzilungiselelo ze-TLS ne-HTTP zokungena kurepository.

Amanye amaproxy e-HTTPS adlulisayo acela isitifiketi sekhasimende ngesikhathi sokuxhumana kwe-TLS kusuka ku-Git kuye kuproxy. Lokho kuwukushintshana kokuqinisekisa okuhlukile ekungeneni kurepository.

Nge-backend ye-TLS ye-Git/libcurl ehambisanayo esebenzisa amafayela e-PEM, ukuhlelwa okuhlobene kunale fomu:

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

Sebenzisa amafayela angempela anikezwe ukuhlelwa kwe-TLS kweproxy. Sebenzisa ukuhlelwa endaweni ye-Git ehlosiwe; ukuhlelwa kwezinga lerepository ingagcina le ndlela ilinganiselwe kuleyo checkout.

IsilungiseleloIndima
proxySSLCAInfoIbhandela le-CA elisetshenziselwa ukuqinisekisa iproxy ye-HTTPS
proxySSLCertIsitifiketi sekhasimende esethulwa kuleyo proxy
proxySSLKeyUkhiye wangasese ohambisana nesitifiketi sekhasimende
proxySSLCertPasswordProtectedIvumela isikhuthazo sephasiwedi se-Git sempahla evikelwe yesitifiketi nokhiye weproxy

I-URL yeproxy ye-https:// ibalulekile kulokhu kushintshana kwe-TLS. Iproxy evamile ye-HTTP ethwala i-CONNECT eya kurepository ye-HTTPS ayenzi ngalokho ukuqinisekiswa kwesitifiketi sekhasimende se-TLS kusilaleli sayo.

Ukwethembela kwezitifiketi zerepository nanoma isiphi isitifiketi sekhasimende serepository kunezilungiselelo zaso ze-ssl. Ngokufanayo, inselele yeproxy ye-HTTP esebenzisa i-Proxy-Authenticate ingenye indlela yokuqinisekisa.

Lapho unakekela lokhu kulungiselelwa, hlola inguqulo ye-libcurl exhunyiwe, i-backend ye-TLS kanye nefomethi yesitifiketi esekelwayo. Indlela eya kwisitifiketi se-PEM ayiyona indawo yokufaka engena kuyo yonke i-interface yesitolo sezitifiketi yeplathifomu.

Izihloko ezihlobene