adding certificates using backend ssl context object

[tekjar]

adding certificates using backend ssl context object

[alexcrichton]

Thanks for the report! Right now the intention of the backend module is to mirror that of std::os, which is to say that it provides backend-specific extension traits for the types defined in the futures-tls crate. The intention here is that if you're configuring OpenSSL then you'd also link to the openssl crate itself.

Along those lines, you'd so somethiing like:

extern crate openssl;
extern crate futures_tls;

use futures_tls::backend::openssl::ClientContextExt;
use openssl::x509::X509FileType;

// ...

Does that make sense? Let me know if that doesn't work out!

[tekjar]

Ahhh. I tried that before, Got this error and gave up too soon

native library `openssl` is being linked to by more than one package, and can only be linked to by one package

  openssl-sys v0.7.14
  openssl-sys v0.7.14 (https://github.com/alexcrichton/rust-openssl?branch=tmp#8b988494)

Fixed this by using your fork of openssl now

openssl = {git = "https://github.com/alexcrichton/rust-openssl", branch = "tmp"}

I suppose your changes are going to be merged upstream. Will use your branch till then. Thanks.

[alexcrichton]

Ah yes indeed! Right now actually I've got no extra changes to rust-openssl, there's just a bug in Cargo on stable if a git repository has a workspace Cargo.toml it doesn't work as a dependency. My "fork" just deletes the workspace Cargo.toml so this project can compile on stable Rust.

Note though I'd much prefer to use a crates.io version of rust-openssl, and @sfackler has indicated that a new version is coming soon! As soon as that's out I'll update this so the dependencies are much easier to write down (e.g. everything uses crates.io)

[sfackler]

By soon I mean tonight, btw.