Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upCertificate errors on five of the twelve blessed links #11929
Comments
|
This seems to be #10550 |
|
@jonathandturner I don't disagree about the message, but it is poking fun at the site that fails not at the user. It's probably time to be slightly less flippant in our error messages considering it's not just us reading them now. |
|
@jonathandturner What is the output of |
|
IRC chat: http://logs.glob.uno/?c=mozilla%23servo&s=29+Jun+2016&e=29+Jun+2016#c466167 TL;DR: on a machine which doesn't have the problem:
|
|
|
@jonathandturner Could you run |
|
@jdm - I don't get anything when I run the command |
|
@jdm @jonathandturner it looks quite likely to be sha256 that's causing the problem. |
|
I get the Zoidberg error page and my OpenSSL has SHA256 stuffs:
On a side note, https://servo.org supports ciphersuites that use SHA1, not just SHA256: https://dev.ssllabs.com/ssltest/analyze.html?d=servo.org&s=104.31.74.227&hideResults=on&latest |
|
SHA256 compatibility: https://support.globalsign.com/customer/portal/articles/1499561-sha-256-compatibility In particular, SHA256 is only supported in OS X 10.5 and above. @jonathandturner are you on |
|
@frewsxcv your openssl may be picking up a different version of the library than servo :( |
|
@asajeffrey - I'm on OS X 10.11.5 |
|
#11932 proposes a more useful SSL error page; unfortunately as long as we use the stock system OpenSSL that's available, we may end up in cases like this one where OpenSSL 0.9.8 simply cannot connect to some sites (see the simulated handshake list at https://dev.ssllabs.com/ssltest/analyze.html?d=servo.org&s=104.31.74.227). |
|
I think #11932 is about as good as we'll get right now, so I'll remove the P1 label. |
|
Something that's also interesting: I can only get the TLS errors when using release mode. The pages load fine for me in |
|
Using this Servo patch, I was able to switch the TLS backend for Hyper to be Security Framework (ignore some of the changes in there about the |
|
Is this issue still relevant? |
|
Is there another issue tracking improvements to TLS errors? |
When I click on any of these:
I get a certificate error:
Incidentally, telling someone they should feel bad for helping to test your product is... an odd choice. Perhaps a more helpful message would be appropriate?