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

MbedTLS had build errors in julia 0.4 #102

Closed
yfractal opened this issue Apr 30, 2017 · 11 comments
Closed

MbedTLS had build errors in julia 0.4 #102

yfractal opened this issue Apr 30, 2017 · 11 comments

Comments

@yfractal
Copy link

yfractal commented Apr 30, 2017

Mux.jl depends MbedTLS.jl and it run tests in julia 0.4 by CI.
But the CI fails because of MbedTLS had build errors.

Does MbedTLS support julia 0.4 now?

@tkelman
Copy link
Contributor

tkelman commented Apr 30, 2017

Prior versions did, master does not. That's a cache server failure, cc @staticfloat

@staticfloat
Copy link
Sponsor Member

staticfloat commented Apr 30, 2017

It's failing on the second download; e.g. the fastly/AWS server connection. Steps to reproduce:

$ docker run -ti quay.io/travisci/travis-ruby /bin/bash
root@1b0d11fe155c:/# curl -v -L -o /dev/null 'https://julialangcache-s3.julialang.org/'
* About to connect() to julialangcache-s3.julialang.org port 443 (#0)
*   Trying 151.101.54.49...   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0connected
* successfully set certificate verify locations:
*   CAfile: none
  CApath: /etc/ssl/certs
* SSLv3, TLS handshake, Client hello (1):
} [data not shown]
* SSLv3, TLS alert, Server hello (2):
{ [data not shown]
* error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version
* Closing connection #0
curl: (35) error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version

Connecting directly to S3 works however:

root@1b0d11fe155c:/# curl -v -L -o /dev/null 'https://julialangcache.s3.amazonaws.com/'
... Lots of happy output ....

This is due to the fact that Fastly only supports TLS (and, starting today, only TLS version 1.2+) and the curl that comes with the precise images of Travis are too old to support this; they only support TLS 1.0.

@tkelman
Copy link
Contributor

tkelman commented May 1, 2017

Good digging. Guess we could maybe do checksum verification but disable certificate checking in the curl call, would that help?

@staticfloat
Copy link
Sponsor Member

We can also run this:

$ sudo apt-get update && sudo apt-get upgrade -y libssl1.0.0

That is sufficient to get libssl1.0.0 updated to the point that it'll talk to our servers.

@tkelman
Copy link
Contributor

tkelman commented May 1, 2017

oh, ubuntu backported that? could try using the apt addon https://docs.travis-ci.com/user/installing-dependencies/#Adding-APT-Packages to avoid needing platform conditionals around it

@staticfloat
Copy link
Sponsor Member

Yes, and that is also supposed to work when you don't have sudo access I think.

@tkelman
Copy link
Contributor

tkelman commented May 1, 2017

right. and sooner or later travis may change their default to 14.04, though I wonder whether people on centos 6 or other similarly old distros may have issues here. python was complaining at me about something related a while back, I forget the exact details though.

@yfractal
Copy link
Author

yfractal commented May 1, 2017

@tkelman
Hi, thanks for your reply.
I guess 0.3.0 is the newest version which supports Julia 0.4, is that right?

@staticfloat
Copy link
Sponsor Member

staticfloat commented May 1, 2017

I wonder whether people on centos 6 or other similarly old distros may have issues here.

If I docker run -ti centos:6, I can curl just fine, so I think it's just a matter of people upgrading their outdated distros with the backported libssl packages. centos:5 doesn't work though, and I can't yum update to see if it's been backported because it looks like CentOS 5 is officially EOL'ed and the repos are gone.

@tkelman
Copy link
Contributor

tkelman commented May 3, 2017

And the buildbots are indeed hitting this. Not good.

@samoconnor
Copy link
Contributor

@quinnj obsolete issue? should be closed?

@quinnj quinnj closed this as completed Mar 7, 2018
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

5 participants