Proxy-ga HTTPS ee Git wuxuu u baahan karaa shahaado macmiil u gaar ah

U habee CA-da TLS ee proxy-ga, shahaadda macmiilka iyo furaha gaarka ah si gooni ah uga duwan dejinta TLS iyo gelitaanka HTTP ee kaydka.

Qaar ka mid ah proxy-yada HTTPS ee gudbinta waxay codsadaan shahaad macmiil inta lagu jiro xiriirka TLS ee Git ilaa proxy-ga. Taasi waa is-dhaafsiga aqoonsi oo ka duwan gelitaanka kaydka.

Backend TLS ee Git/libcurl oo ku habboon oo isticmaalaya faylasha PEM, dejinta la xiriirta waxay leedahay qaabkan:

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

Isticmaal faylasha dhabta ah ee loo bixiyay habaynta TLS ee proxy-ga. Ku dabaq dejinta heerka Git ee loogu talagalay; dejin heer kayd ah waxay ku xaddidi kartaa waddadan checkout-kaas.

DejinDoorka
proxySSLCAInfoXirmada CA ee loo isticmaalo xaqiijinta proxy-ga HTTPS
proxySSLCertShahaadda macmiilka ee loo soo bandhigo proxy-gaas
proxySSLKeyFuraha gaarka ah ee u dhigma shahaadda macmiilka
proxySSLCertPasswordProtectedWaxay awood u siinaysaa Git inuu weydiiyo furaha sirta ah ee agabka shahaadda iyo furaha proxy-ga ee la ilaaliyay

URL-ka proxy-ga https:// ayaa lagama maarmaan u ah is-dhaafsigan TLS. Proxy HTTP caadi ah oo CONNECT u qaada kayd HTTPS ma sameeyo sidaas aqoonsiga shahaadda macmiilka TLS ee dhageystaha u gaar ah.

Kalsoonida shahaadaha kaydka iyo shahaad kasta oo macmiilka kaydku waxay leeyihiin dejintooda ssl. Sidoo kale, caqabadda proxy HTTP ee isticmaalaysa Proxy-Authenticate waa hab aqoonsi kale.

Marka aad dayactirto habayntan, hubi nooca libcurl ee ku xiran, backend-ka TLS iyo qaabka shahaadda la taageerayo. Waddada shahaadda PEM maaha beddel la qaadan karo oo loogu talagalay dhammaan is-dhexgalka kaydka shahaadaha ee madal.

Maqaallo la xiriira