-
Notifications
You must be signed in to change notification settings - Fork 10.4k
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
TLS handshake failure #2717
Comments
|
My hypothesis is that the server rejects TLS client hello because of some specified ciphers: Wireshark displays me this response from the server: It comes immediately after TLS client hello message. |
|
@redapple is the man who knows everything about such issues, but have you tried setting a different DOWNLOADER_CLIENT_TLS_METHOD option value? |
|
Unfortunately, changing TLS version does not help. |
|
I think you're on the right track with cipher suites.
Did you compare ClientHello requests for success and failure cases?
I cannot reproduce it with that URL but I have an older openssl.
I'll try and use a more recent one tomorrow.
Le 25 avr. 2017 22:03, "Povilas Balciunas" <notifications@github.com> a
écrit :
… Unfortunately, changing TLS version does not help.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2717 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AA2GGE9OGAcs4VwCcJR3gcgt_vJO1Qepks5rzlGsgaJpZM4NHuwX>
.
|
|
How do you make scrapy/python to choose specific openssl version? |
|
I haven't tried it yet myself but I believe you can use https://cryptography.io/en/latest/installation/#static-wheels I was planning on using an Debian 9 Sid docker image. |
|
Alright, I just tried #2717 (comment) |
|
For the record, I've collected .pcap files and expanded ClientHello message for Scrapy and OpenSSL client 1.0.2g and 1.1.0e in https://github.com/redapple/scrapy-issues/tree/master/2717 I'm leaning towards something to do with Elliptic Curves. |
|
Yeah, it looks like an EC thing:
made the connection to 'https://www.skelbiu.lt/' work for me. Now, I'll have a look at how to properly configure this with Twisted Agent. |
|
From what I see on https://www.ssllabs.com/ssltest/analyze.html?d=www.skelbiu.lt&s=92.62.130.22&hideResults=on, the website indeed requires (at least?) "secp384r1", which I tested in #2717 (comment) By default, openssl 1.1.0e client sends: but Scrapy1.3.3/Twisted 17.1 with OpenSSL 1.1.0e only sends: The code in Twisted using A couple of (non-exclusive) options :
|
|
fyi, I've sent a message on Twisted Web mailing list: https://twistedmatrix.com/pipermail/twisted-web/2017-April/005293.html |
|
I just tested with Twisted 17.5.0rc2 and this does NOT look fixed. |
|
For me the issue is https://bugs.python.org/issue29697 The patch date is after all python stable versions and it causes the same error for |
|
Twisted bug: https://twistedmatrix.com/trac/ticket/9210 |
|
I'm having the same issue with following versions: Is there a workaround? |
|
@werdlv , I don't know any workaround. |
|
@redapple sure. At least these are giving SSL error: Here are some that are working without errors: |
|
Thanks @werdlv . |
|
also error site https://www.teplodvor.ru/ |
|
see also #2944 |
|
Right @tonal . https://www.teplodvor.ru/ does not look compatible with OpenSSL 1.1 (some weak ciphers were removed). |
|
@redapple I have run pip install --upgrade 'cryptography<2', but not work url: https://www.archdaily.com Scrapy : 1.4.0 <GET https://www.archdaily.com> |
|
@sulangsss seems that you are still using OpenSSL 1.1.0. |
|
I just installed Twisted==18.4.0rc1 and www.skelbiu.lt seem to work for me. |
|
Closing since this has been fixed in Twisted 18.4.0. |
|
I'm experiencing this in Ubuntu 18.04 (Twisted 17.9.0, OpenSSL 1.1.1). I cannot update to newer packages, but I do control my entire application. I've made this workaround in my main file, after imports: This should probably be used only as a last resort if libraries cannot be updated. |
Its working for the version 1.4.0. |
I have this simple spider:
On debian 9 it fails with:
On debian 8 it works well.
And "https://www.skelbiu.lt" is the only target I can reproduce the problem.
Some more context:
Any ideas what I should look for? :)
The text was updated successfully, but these errors were encountered: