It should ‘not’ contain any reference to your company. Go to any outside site (like Amazon) and review the sites “Cert” to see who the CA’s are (Certification Path). An interesting CA trust issue.Ĭonfirming this does exist is easy from your browser. No ' whitelisting' needed and not ' VPN' related. This makes VSCode happy again trusting the fake cert chain. It tells VSCode to also trust the CA’s installed on the employees desktop. So the local browsers and other desktop apps trust this faked cert chain - and so do not raise any concerns someone is snooping your secure network traffic (the company does own the network and the device).īy default VSCode is not trusting the installed desktop certs, and so it noticed that the GitHub cert is no longer signed by a trusted public CA authority.Īs Rypox states above, the VSCode extension ‘Win-CA’ ( must be set to ‘append’ mode) solves this issue. Hence the self-signed cert in the cert chain error.įrom any company device (Phones\Laptop) the company CA is already installed as a trusted CA. The cert for the called site is replaced with a fake, and one signed by the company’s own private CA authority. This action leaves behind a fake cert chain as a fingerprint. It all gets logged and reviewed further if need be. Usually automation scrubs the traffic looking for theft of company secrets or IP and raises alerts. This ensures they can inspected any traffic leaving, including your online banking. Most corporate networks have a ‘Man-in-the-middle’ appliance that dynamically breaks open all secure SSL traffic leaving home to enter the internet. Extension activation failed: self-signed certificate in certificate chain” is generally caused using CoPilot behind a Corporate network.
Copilot error: “ GitHub Copilot could not connect to server.
0 kommentar(er)
