Bug#770447: use of ssl.PROTOCOL_SSLv3 which we don't support anymore
Thomas Goirand
zigo at debian.org
Sun Nov 23 09:27:50 UTC 2014
On 11/22/2014 03:28 AM, Matteo F. Vescovi wrote:
> Hi!
>
> On Nov 21, 2014 7:51 PM, "Thomas Goirand" <zigo at debian.org
> <mailto:zigo at debian.org>> wrote:
>> Thanks for taking the time to investigat it (which I didn't have time
>> yet, but still wanted to push the bug before I had to go out of
> $workplace).
>
> Now, given that the SSLv3 feature is disabled by default, could this bug
> be closed? Thomas, is it ok for you?
>
> Cheers.
Hi,
I'm not sure you get the point of me opening this bug. The point is, if
you have an instance of ssl.PROTOCOL_SSLv3, then when the Python parser
will try to execute the code, it will crash (stack dump).
For this reason, I've done something like this in my packages:
http://anonscm.debian.org/cgit/openstack/oslo.messaging.git/commit/?id=6e39d2c1fad7be373651abd709feea9c3b56977c
Maybe your package needs that too?
Cheers,
Thomas Goirand (zigo)
More information about the pkg-multimedia-maintainers
mailing list