On 7/10/2015 06:18, Dominik Erdmann wrote:
> Am 05.10.2015 um 00:07 schrieb Ryan Kelly:
>>> [Sat Oct 03 16:26:35 2015] [error]
>>> /PATH_TO_SYNC_SERVER/local/lib/python2.7/site-packages/requests/packages/urllib3/util/ssl_.py:90:
>>>
>>> InsecurePlatformWarning: A true SSLContext object is not available. This
>>> prevents urllib3 from configuring SSL appropriately and may cause
>>> certain SSL connections to fail. For more information, see
>>> https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
>>>
>>>
>>> [Sat Oct 03 16:26:35 2015] [error] InsecurePlatformWarning
>>>
>>> Does someone have experience with this message and know how to use
>>> pyOpenSSL as described?
>>
>> I've never had to enable this myself, but IIUC it should work without
>> too much hassle. I've pushed an update to the syncserver codebase to
>> enable it when PyOpenSSL is installed:
>>
>>
>> https://github.com/mozilla-services/syncserver/commit/a521aed39fa279c10b685ff8359057793fde0e98
>>
>>
>> So you could try updating syncserver, installing, pyopenssl, and see if
>> that makes a difference:
>>
>>
>> $> git pull
>> $> make build
>> $> ./local/bin/pip install pyopenssl ndg-httpsclient pyasn1
>
> After I installed the package libffi-dev I could successfully install
> pyopenssl & Co. But it seems to do not work with local pip. I installed
> the system-wide packages with
>
> /usr/bin/pip install pyopenssl ndg-httpsclient pyasn1
>
> Now I don't get any error message. Does make it sense to use system-wide
> pip? (By the way, I'm using Apache + mod_wsgi).
It's a bit odd, but it should be fine a long as it seems that the app is
picking it up and working properly.
Cheers,
Ryan
_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev
