Info: syncing channel updates for '1.64-x86_64-unknown-linux-gnu'Įrror: could not download file from '' to '/home/ilyagr/.local/app/rustup/tmp/h8sfjn1fqih4kpcr_file'Įrror: could not download file from '' to '/tmp/rustup-updateWTZmyb/release-stable.toml':įailed to make network request: error sending request for url ():Įrror trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1921:
Info: syncing channel updates for 'nightly-x86_64-unknown-linux-gnu'Įrror: could not download file from '' to '/home/ilyagr/.local/app/rustup/tmp/zdes5clkoev1tz5o_file' Info: syncing channel updates for 'beta-x86_64-unknown-linux-gnu'Įrror: could not download file from '' to '/home/ilyagr/.local/app/rustup/tmp/n8ste_t87j1jy11u_file' It should not be as painful as it currently is this is a useability bug, that makes for a very bad user experience when your computer is on a corporate network. I've seen the other issues saying to add certificates to the ca cert folder, but there is no certificate available to add to the cert store.Īdding a command line argument to disable checking certificates is the simplest solution for a user in a restrictive corporate network that just wants a way to get a functional install of rust. Fail because rustup needs to get run (eg rustup install stable) to install a toolchain, and there is no way to bypass the SSL certificate check.Īdd a command line argument that bypasses the SSL certificate check. Fail because rustup checks the certificate.
Try rustup-init.sh with curl and wget commands modified to not check executable.Find a company that intercepts SSL connections.I've tried adding -no-check-certificate and -insecure to the curl/wget commands in the "easy" rustup-init.sh script, but then the rustup command fails due to the same SSL certificate validation errors.
The place I work at has networking hardware in place that basically breaks SSL. Rustup has no option to disable certificate checking.
0 kommentar(er)
