Bug#770447: use of ssl.PROTOCOL_SSLv3 which we don't support anymore

[Matteo F. Vescovi]

Control: tag -1 fixed-upstream

Hi!

On 2014-11-23 at 09:27 (CET), Thomas Goirand wrote:
> 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?

I asked upstream developers to check their code and they confirmed that
they're going to change it directly there as you adviced (v3 => v23).

Once I'll be sure the change has become part of the upstream source
code, I could prepare a patch to fix this issue in the package actually
in unstable/testing.

Cheers.


-- 
Matteo F. Vescovi || Debian Developer
GnuPG KeyID: 4096R/0x8062398983B2CF7A
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 956 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20141124/16c95e82/attachment.sig>