Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rust install through proxy and Artifactory : Bug on SSL certification #3870

Closed
Pierremalle opened this issue Jun 12, 2024 · 4 comments
Closed

Comments

@Pierremalle
Copy link

Hi everyone.
Not really a bug i'm facing but i'm kinda blocked. My company is using an Artifactory repository to mirror to Rust crates.
So i connected my rustup to this repo and it seems to work fine since it's searching on the good place.

However, i can't use rustup to install rust as the internal proxy of the company ruin all SSL certificate.
A senior dev told me the same happened with Conan and they just deactivate SSL check EVERYWHERE.

Is there, today, a way to deactivate it with rustup ?

Thanks a lot.

@djc
Copy link
Contributor

djc commented Jun 12, 2024

Don't you get a company trust root for your internal proxy installed on your machine? That would probably still allow it to work.

@Pierremalle
Copy link
Author

Sadly, i don't think so.
The senior who answered my question well precised that in another project, they put SSL check deactivation everywhere on a Conan similar problem, indicating that even senior dev don't have that type of help.
He insisted on the fact that i must deactivate it from the source which is rustup.

@djc
Copy link
Contributor

djc commented Jun 12, 2024

I would first talk to your infrastructure/IT folks to see if you can get the internal trust root installed. Installing a compiler toolchain without authenticating it seems like an extremely bad idea.

@Pierremalle
Copy link
Author

Well, that's what i also found on this topic :
#1624 (comment)

i'll talk about it to my internship referent. It would be a good solution be will surely take a long time.

Thanks a lot, i'll consider this as close.

@djc djc closed this as not planned Won't fix, can't repro, duplicate, stale Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants