You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
our pipelines are running behind a corporate firewall with custom TLS certificates. These are part of the certificate store, and curl, cargo and all other programs are working properly.
While cargo install for instance works, cargo binstall doesn't, despite having set SSL_CERT_FILE which was introduced in #774.
And here's the error message that I get when I'm trying to install something with cargo binstall
The text was updated successfully, but these errors were encountered:
Ah, we changed the env var due to some conflict, it's BINSTALL_HTTPS_ROOT_CERTS or using the --root-certificates option on the command line. I'm not sure why we don't read from the system cert store though.
Hi,
our pipelines are running behind a corporate firewall with custom TLS certificates. These are part of the certificate store, and
curl
,cargo
and all other programs are working properly.While
cargo install
for instance works,cargo binstall
doesn't, despite having setSSL_CERT_FILE
which was introduced in #774.And here's the error message that I get when I'm trying to install something with
cargo binstall
The text was updated successfully, but these errors were encountered: