-
Notifications
You must be signed in to change notification settings - Fork 5
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
not ok 44 - Can connect to a Cro::SSL::Listener with ALPN set up with ALPN from client #1
Comments
What is the version of openssl you use(and OS running)? It seems that it does not support ALPN. You cannot use it if the underlying library does not support it. If it is the reason of your issue, you need to build/get openssl with ALPN support enabled. |
@Altai-man Obviously those without an ALPN-supporting OpenSSL won't be able to use the things that depend on it (that is, HTTP/1.1 vs. HTTP/2 selection), but People having an OpenSSL without ALPN will be sorta common for a while, as it takes time for things to make it into distros, and only a handful of them actually have a new enough OpenSSL. |
@jnthn, for some reason, I've always thought that because of Security OpenSSL updates must be regular for everyone... It seems, not for everyone. I'll look into it today, to do these tests optional in the same manner as |
Should be fixed with croservices/cro-ssl@1c03065 |
I have this is issue on macOS Sierra 10.12.6 with a local OpenSSL as well as the latest from homebrew "openssl 1.0.2l". If the last patch is in master and what is pulled down with zef right now, then its still blocking install. |
@MattOates, can you provide your installation log? |
https://gist.github.com/MattOates/a3cef012a764df43a339e377d36c7a15 there are also a lot more scary looking errors post force installing Cro::SSL |
Let's look on it step by step...
It looks like there is no guards in tests, that were added in croservices/cro-ssl@1c03065
Hmmm. This one should pack http/1.1 for this line.
Looks scary. Maybe @jnthn knows more about this one?
Odd. It was fixed with croservices/cro-http@21e4076 - it totally looks like you are using an old versions of libraries. As for services-related failures - I think it wants a new, separate issue. Can you try Or by hands clone latest repositories in reverse order(i.e. Core -> TLS -> HTTP -> WebSocket -> Cro) and try to install it manually with |
Cloned, did a 'zef install --deps-only .'
Then dies with:
The text was updated successfully, but these errors were encountered: