Control: severity -1 serious
Control: retitle -1 Connection to TLS-enabled servers is broken: Error in
SSLSocket
Hi,
anonym wrote (19 Mar 2015 11:03:49 GMT) :
> Next, here's a small test case to for triggering the bug:
> import xmpp
> xmpp.Client("jabber.ccc.de").connect()
This bug seems RC to me, as: 1. it's a regression from Wheezy; 2. most
popular XMPP servers offer TLS these days, so it seems to be that this
bug breaks break the most common use-case of this library; and also 3.
python-xmpp has quite a few reverse-deps that might be affected (I
didn't check, though).
=> bumping severity. Alexey, what do you think?
(Now, I don't see any reply from Alexey to the open bugs on this
package, some of them dating back to 2010. Last upload by Alexey was
in 2008, and there have been 2 NMUs since then, none of them
acknowledged => I won't hold my breath too long.)
> With the patch supplied by Vladimir Osintsev, the problem is indeed
> fixed.
I'll try to come up with a minimal patch that satisfies the freeze
policy (introducing the quilt machinery is definitely not an option at
this stage of the freeze). And then I'll prepare a NMU.
> There are, however, other issues with xmpppy, so the python-xmpp
> package is in a pretty poor state [...]
Indeed, it would be good if something could be done about it during
the Stretch cycle. python-xmpp has quite a few reverse-dependencies,
so perhaps a couple of their upstream or Debian maintainers will want
to adopt xmpppy upstream. Let's say it's off-topic here, though: the
discussion that was started on #592010 feels like a better place to
discuss future plans.
Cheers!
--
intrigeri
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
