Export-CertBundle
1.0
In many enterprise environments, Netskope inspects HTTPS traffic by decrypting and re-signing
connections with an enterprise certificate. Windows usually trusts that certificate because it
is in the OS certificate store.
The problem: many developer tools (Python, Node.js, curl, Git, containerized apps) do not
always use the Windows certificate store directly. They of
connections with an enterprise certificate. Windows usually trusts that certificate because it
is in the OS certificate store.
The problem: many developer tools (Python, Node.js, curl, Git, containerized apps) do not
always use the Windows certificate store directly. They of
In many enterprise environments, Netskope inspects HTTPS traffic by decrypting and re-signing
connections with an enterprise certificate. Windows usually trusts that certificate because it
is in the OS certificate store.
The problem: many developer tools (Python, Node.js, curl, Git, containerized apps) do not
always use the Windows certificate store directly. They often expect a PEM certificate bundle.
That mismatch causes TLS errors even when your browser works.
See: https://community.netskope.com/next-gen-swg-2/configuring-developer-tools-with-netskope-ssl-inspection-8493
This script exports trusted CA certificates from Windows stores and writes them into one PEM
bundle file (default: corp_certs.pem). You can point tools to this file to mitigate TLS trust
failures caused by interception.
Show more
connections with an enterprise certificate. Windows usually trusts that certificate because it
is in the OS certificate store.
The problem: many developer tools (Python, Node.js, curl, Git, containerized apps) do not
always use the Windows certificate store directly. They often expect a PEM certificate bundle.
That mismatch causes TLS errors even when your browser works.
See: https://community.netskope.com/next-gen-swg-2/configuring-developer-tools-with-netskope-ssl-inspection-8493
This script exports trusted CA certificates from Windows stores and writes them into one PEM
bundle file (default: corp_certs.pem). You can point tools to this file to mitigate TLS trust
failures caused by interception.
Installation Options
Owners
Package Details
Author(s)
- david.ramos@hotmail.com
Tags
Certificate PEM TLS SSL Netskope Proxy WSL Docker TrustStore CorporateNetwork DevTools HTTPS
Dependencies
This script has no dependencies.
FileList
- Export-CertBundle.nuspec
- Export-CertBundle.ps1
Version History
| Version | Downloads | Last updated |
|---|---|---|
| 1.0 (current version) | 6 | 4/17/2026 |