-
Notifications
You must be signed in to change notification settings - Fork 393
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
Statically linked musl
binaries built with OpenSSL cannot verify certificates CA
#119
Comments
Workaround for this problem:
courtesy of @jamesmunns AFAIU, the issue here is that we build OpenSSL into the docker images using We definitely would like to provide a better default certificate patch but I can't think of a solution right now. |
Other option is to use https://github.com/alexcrichton/openssl-probe |
More information: cross-rs/cross#119
Consider the following program:
On my system (
x86_64-unknown-linux-gnu
), this works fine as expected:$ cargo build ... snip ... Compiling cross-ssl-error v0.1.0 (file:///home/yongwen/work/scratch/cross-ssl-error) Finished dev [unoptimized + debuginfo] target(s) in 26.5 secs $ target/debug/cross-ssl-error OK
But, if I use
cross
to build forx86_64-unknown-linux-musl
:Not sure what is going on. Seems like the CAs are not linked into the binaries?
The text was updated successfully, but these errors were encountered: