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

SSL connect error #2797

Closed
hh9527 opened this issue Jun 21, 2016 · 3 comments
Closed

SSL connect error #2797

hh9527 opened this issue Jun 21, 2016 · 3 comments

Comments

@hh9527
Copy link

hh9527 commented Jun 21, 2016

Is this problem related to ca certification verify?
Is there something I can do to disable verify certification?

I am running in WINDOWS 7 behind my company's proxy. with a cntlm as local proxy.

Here is my config:

# .cargo/config

[http]
proxy = "http://127.0.0.1:10922/"

And this is what I got when execute cargo build

C:\home\dws\learn\lrust\r1>cargo --version
cargo 0.10.0-nightly (10ddd7d 2016-04-08)

C:\home\dws\learn\lrust\r1>rustc --version
rustc 1.9.0 (e4e8b6668 2016-05-18)

C:\home\dws\learn\lrust\r1>cargo build --verbose
    Updating registry `https://github.com/rust-lang/crates.io-index`
error: Unable to update registry https://github.com/rust-lang/crates.io-index

Caused by:
  failed to fetch `https://github.com/rust-lang/crates.io-index`

Caused by:
  [12/-2] SSL connect error
@alexcrichton
Copy link
Member

Disabling SSL verification is the topic of #1180, but maybe this is just a misconfigured proxy or a bug in the proxy handling code somewhere?

@hh9527
Copy link
Author

hh9527 commented Jun 22, 2016

My npm (node package manager) works well with same proxy configuration, but it needs to config strict-ssl = false, so I think it maybe related to ssl verification.

My company proxy use has a self-signed cert. but it is still use legacy algorithm(SHA-1). And I can not import it to chrome/firefox.

@alexcrichton
Copy link
Member

Ah ok, in that case I'm gonna close this in favor of #1180 as it sounds like it's a case of correctly rejecting an SSL cert and then it's just otherwise difficult to customize the root certs and such.

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