Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TLS-Fragments #43

Open
GoogleCodeExporter opened this issue Jul 4, 2015 · 0 comments
Open

TLS-Fragments #43

GoogleCodeExporter opened this issue Jul 4, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
Openfire 3.9.3
Debian 7.6
Try to connect to openfire with iksemel.
Openfire seems to send all TLS-encrypted data, spread into two Application-Data 
packets, where -after decrypting- the first one seems to include only the first 
character (usually '<').

What is the expected output? What do you see instead?
Iksemel should read both Application-Data packets, concatenate the included 
parts of the XML and parse the resulting string.
Unfortunately iksemel reads the first packet and tries to parse it's payload, 
which fails ('<'). After that it reads the second packet and tries to parse the 
resulting string, which results in the first XML-Tag missing (because the '<' 
is missing).
If the message contained of an XML with only one Tag, the result is empty.

What version of the product are you using? On what operating system?
iksemel 1.4 (not the Debian-version!)
Debian 7.6

Please provide any additional information below.
Patch for git-HEAD attached (only solves the issue, where the message is 
splitted after the first few characters).

Please consider including the attached patch or find a more complete way of 
fixing this issue

Best Regards,
Markus

Original issue reported on code.google.com by [email protected] on 23 Jul 2014 at 3:48

Attachments:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant