Jabber client SSL regression

Bug #47977 reported by Alex Mauer
8
Affects Status Importance Assigned to Milestone
libio-socket-ssl-perl (Debian)
Invalid
Undecided
Unassigned
libio-socket-ssl-perl (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

this version of libio-socket-ssl-perl doesn't allow jabber's chatbot ( http://jabberstudio.org/recover/projects/chatbot/ ) or ijchain ( http://jabberstudio.org/recover/projects/ijchain/ ) to connect with SSL. The prior version did; replacing it with the package from Debian sarge allows it to work again.

Revision history for this message
Simon Law (sfllaw) wrote :

Could you provide more information about the problem?

What errors do chatbot and ijchain report? Is this an API breakage
in IO::Socket::SSL?

Thanks.

Changed in libio-socket-ssl-perl:
status: Unconfirmed → Needs Info
Revision history for this message
Alex Mauer (hawke) wrote :

ijchain hangs here (shown when I turned debuglevel to 1 in ijchain):

XML::Stream: Send: (<?xml version='1.0'?><stream:stream version='1.0' xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' to='jabber.hawkesnest.net' from='tiberius.hawkesnest.net' xml:lang='en' >)

running with perl -d and breaking when it hangs gives me:

Net::SSLeay::ssl_read_all(blib/lib/Net/SSLeay.pm (autosplit into blib/lib/auto/Net/SSLeay/ssl_read_all.al):1598):
1598: last if $errs = print_errs('SSL_read');

If I continue at this point, it will get further and hang with:
XMPP::Conn: Process: timeout(1)

breaking again indicates that it's hung at the same location as above. The above hang will repeat indefinitely, resuming normally when I break in debug mode and continue.

Downgrading to libio-socket-ssl-perl 0.96-1 from Debian stable allows the program to operate normally.

I can't answer whether it's an API breakage or not.

Revision history for this message
Alex Mauer (hawke) wrote :

Info has been provided.

Changed in libio-socket-ssl-perl:
status: Needs Info → Unconfirmed
Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10 alpha?

Changed in libio-socket-ssl-perl:
status: New → Incomplete
Revision history for this message
Javier Jardón (jjardon) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in libio-socket-ssl-perl:
status: Incomplete → Invalid
Changed in libio-socket-ssl-perl (Debian):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.