You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Restkit does not validate TLS which means it's HTTPS handling is broken and insecure.
>>>fromrestkitimportrequest>>>r=request("https://tv.eurosport.com/")
>>>r.body_string()
'<HTML><HEAD><TITLE>Error</TITLE></HEAD><BODY>\nAn error occurred while processing your request.<p>\nReference #102.34e74217.1426170776.e615a32\n</BODY></HTML>\n'
@dstufft if you pass cert_reqs=ssl.CERT_REQUIRED to the request that will force validation. But as far as I can see there is no way to validate the hostname, so the job's only half done. (server_hostname is not a ssl.wrap_socket argument)
Activity
tdsmith commentedon Aug 4, 2015
This was assigned CVE-2015-2674. http://seclists.org/oss-sec/2015/q1/962
macropin commentedon Aug 7, 2015
Since Restkit just wraps the Python ssl socket library, this PEP is relevant https://www.python.org/dev/peps/pep-0476/ (and shows the scope of the issue).
@dstufft if you pass
cert_reqs=ssl.CERT_REQUIREDto the request that will force validation. But as far as I can see there is no way to validate the hostname, so the job's only half done. (server_hostnameis not assl.wrap_socketargument)andreasstieger commentedon May 26, 2017
Ping?
carnil commentedon Oct 3, 2017
Any news?