cargo-binstall doesn't work behind corporate firewall

[scalpel4k]

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 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

[passcod]

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.

[NobodyXu]

I recalled reading from system env somehow breaks our CI?

[scalpel4k]

oh thanks, this actually did the trick. Now that I know reading the command line help would have helped .....

[Boscop]

Btw, why does cargo-binstall trigger Windows 11 Firewall to ask me if I want to allow it on public & private networks?
I declined and it still seemed to work to install a binary, so why is it necessary to allow it through the firewall? 🙂

[passcod]

cargo-binstall isn't the one triggering the firewall; probably better to ask Windows 11 why it's uselessly overzealous

[Boscop]

Hm, weird. Usually that firewall dialog only appears whenever an app tries to listen on a port.

[NobodyXu]

Hm, weird. Usually that firewall dialog only appears whenever an app tries to listen on a port.

Well we definitely don't listen on any port, only connect to port for network requests and DNS.