libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Crunkleton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LIBCLOUD-804) Flaky SSL issues: _ssl.c:515 EOF occurred in violation of protocol.
Date Thu, 03 Mar 2016 22:38:18 GMT

    [ https://issues.apache.org/jira/browse/LIBCLOUD-804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178742#comment-15178742
] 

Scott Crunkleton commented on LIBCLOUD-804:
-------------------------------------------

This error depends on the environment you're running in, but should we consider allowing backported
ssl?
By default, we are running PROTOCOL_TLSv1, but backports.ssl, Python 2.7.9+, and Python 3.2+
all have PROTOCOL_TLSv1_1 and PROTOCOL_TLSv1_2.

https://pypi.python.org/pypi/backports.ssl

> Flaky SSL issues: _ssl.c:515 EOF occurred in violation of protocol.
> -------------------------------------------------------------------
>
>                 Key: LIBCLOUD-804
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-804
>             Project: Libcloud
>          Issue Type: Bug
>            Reporter: Scott Crunkleton
>
> I've been seeing some SSL flakes: "_ssl.c:515 EOF occurred in violation of protocol".
On searching, I see others have had the same issue (e.g. https://github.com/segmentio/analytics-python/issues/23
and http://stackoverflow.com/questions/14102416/python-requests-requests-exceptions-sslerror-errno-8-ssl-c504-eof-occurred).
A proposed solution is to monkey patch ssl sockets to use TLSv1 (https://docs.python.org/2.7/library/ssl.html#ssl.PROTOCOL_TLSv1).
I haven't tried this yet.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message