Open arvid-norlander opened 10 months ago
Hm. It looks like, to the extent of, cargo-update talking to the network, it did work – polling the registry completed, this output matches reality.
The step that failed is the updating step, i.e. fork()/exec("cargo", "[b]install", ...) – all the logs since INFO
are from either cargo or cargo-binstall.
Given the formatting and them containing three 2kB blobs, I'd assume cargo-binstall, especially since you say cargo install cargo-binstall
works – how about cargo binstall cargo-binstall
?
Hmmm it seems that cargo-binstall has problem dealing with your transparent proxy setup.
Would you please open a ticket in cargo-binstall and gives us the info required to reproduce/fix this?
Thanks!
I don't believe it is cargo-bininstall. It seems to apply to all packages I build via "cargo install-update" as opposed to "cargo install". Cargo-bininstall was just the example I pasted above.
cargo install-update
would use cargo-binstall
whenever it is available.
Can you try using cargo-binstall
directly?
Oh, didn't know that. I can try when I get back to the office. Right now it is hard to try: 1) everything is up-to-date 2) I'm working remotely today rather than at the office (and it only happens when in the office for some reason).
But I do find the line error sending request for url (https://index.crates.io/config.json): error trying to connect: invalid peer certificate: UnknownIssuer
rather telling. Since the proxy performs a MITM attack basically you need to have the HTTPS certificate installed into your trust store. It is installed in the trust store of Ubuntu (/etc/ca-certificates
) as well as of Firefox and Chrome. For some reason it seems cargo-bininstall doesn't pick up that certificate then.
You can use cargo binstall --force cargo-binstall
to force it to install it again.
P.S. it's cargo-binstall
, not cargo-bininstall
.
It is installed in the trust store of Ubuntu (/etc/ca-certificates) as well as of Firefox and Chrome. For some reason it seems cargo-bininstall doesn't pick up that certificate then.
Could you please open an issue in cargo-binstall
?
I will investigate in it
Actually I already have a hint on what went wrong.
Would open a PR tomorrow
Opened https://github.com/cargo-bins/cargo-binstall/pull/1589 for this, it should fix the issue for you.
Thanks I will check it out today when I'm at the office.
I had nothing that needed updating, but cargo auditable install-update -f cargo-about
worked and was able to use cargo-binstall with the new version, so I suspect this is working properly now.
I'm behind a corporate transparent HTTPS proxy. The required SSL certificate has been installed in /etc/ca-certificates and works as expected for plain
cargo install
. However:As I said above, running a plain
cargo install cargo-binstall
works perfectly. It seems cargo-update does not respect the system certificate store.System & environment info: