If not such nasty errors can also happen.
Post by Scott Haddin
Thanks for the response. Unfortunately we only receive a generic unknown SSL Error
*/requests/adapters.py", line 497, in send raise SSLError(e,
*requests.exceptions.SSLError: unknown error (_ssl.c:2941)*
Implementing a workaround for requests
/requests/adapters.py", line 440, in send timeout=timeout
pyOpenSSL-16.2.0-py2.7.egg/OpenSSL/_util.py", line 48, in
exception_from_error_queue OpenSSL.SSL.Error: 
It appears as though multiple packaged libraries/modules cannot deal with the SSL error.
We believe it is probably something to do with the strengthening of SSL
certificates in the past couple of years. Iâm still trying to get
confirmation but it looks like this current packaged version of requests
does not like TLSv1/SSLv3 encryption.
The (Asana) client api that we are trying to integrate with even states
that it has a minimum version requirement of requests 2.14.0. Looking at
the changes to Requests for version 2.14.0+ there were also an update with
the bundles urllib3 so it could be possible that the underlying cause also
stems from urllib3 components.
Iâll provide some feedback to the developers and hopefully the modules can be updated.
*Sent:* Tuesday, 12 June 2018 6:25 PM
*Subject:* Re: [Check_mk (english)] [bug] Python requests version outdated
this is more question for the developers in Munich. But from my side I had
no problem until now with this included requests version.
How does your SSL problem looks like?
Upon attempting to create a ticketing engine to integrate with the Asana
API it was discovered the packaged version of python is using an outdated
version of requests [2.13] module, the old version of requests is creating
issues with SSLerrors.
Is it possible to have ârequestsâ module updated to 2.18 or is there a
requirement to use v2.13?
checkmk-en mailing list
Manage your subscription or unsubscribe