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

cargo: problem with CA certificates #8872

Closed
flosse opened this issue Jul 18, 2015 · 9 comments
Closed

cargo: problem with CA certificates #8872

flosse opened this issue Jul 18, 2015 · 9 comments

Comments

@flosse
Copy link
Contributor

flosse commented Jul 18, 2015

using 15.06pre65267.6ad8fab (Dingo) and cargo 0.3.0 (a2dd2ac 2015-06-24) (built 2015-07-17) leads to this error:

cargo test --verbose                                                                                        
 Downloading libc v0.1.8
Unable to get packages from source

Caused by:
  Failed to download package `libc v0.1.8` from https://crates.io/api/v1/crates/libc/0.1.8/download

Caused by:
  Peer certificate cannot be authenticated with given CA certificates

What can I do?

@vcunat
Copy link
Member

vcunat commented Jul 18, 2015

Find how it searches for certificates. Curl with our CA accepts the URL.

@flosse
Copy link
Contributor Author

flosse commented Jul 18, 2015

I see. It seems to be related to rust-lang/cargo#976.
@sjmackenzie & @telotortium are you able to run cargo v0.3.0 with rustc v1.1.0?

@flosse
Copy link
Contributor Author

flosse commented Jul 18, 2015

using cargo 0.3.0-nightly (14e8ed9 2015-06-15) (built 2015-06-16) works fine.
But I still have no idea if this problem is nixos or cargo related :-\

@vcunat
Copy link
Member

vcunat commented Jul 18, 2015

A "simple" fix would be to rebuild cargo against openssl 1.0.2b or superior.

This might be another work around. We do have that version in nixpkgs, only it isn't the default one yet.

@flosse
Copy link
Contributor Author

flosse commented Jul 18, 2015

We do have that version in nixpkgs, only it isn't the default one yet.

so we cold write this:

  cargo = callPackage ../development/tools/build-managers/cargo {
    rustPlatform = rustCargoPlatform;
    openssl = openssl_1_0_2;
  };

Or what would be the problem with that?

@vcunat
Copy link
Member

vcunat commented Jul 18, 2015

None that I know of.

@telotortium
Copy link
Contributor

A preliminary run of git bisect between git bisect start 6eab106 71c1644 (6eab106 was the master as of yesterday, 71c1644 is the merge commit for #8668) found 333f145 to possibly be the first bad commit (I ran git bisect run sh -c "nix-env -f $PWD -qa 'cargo-0.3.0' >/dev/null 2>&1 || exit 125; nix-build $PWD -A cargo" to attempt building cargo at each commit while skipping commits for which cargo hadn't been updated to 0.3.0, which was merged from #8668).

@globin
Copy link
Member

globin commented Dec 28, 2015

I haven't experienced this for quite a while, can be closed.

@vcunat
Copy link
Member

vcunat commented Dec 28, 2015

Reopen if you experience it again.

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

4 participants