Project

General

Profile

Bug #284

Beem fails to authenticate - Wireshark analysis - DIGEST-MD5 protocol error?

Added by Anonymous over 14 years ago. Updated about 14 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Frédéric Barthéléry
Category:
-
Target version:
0.1.5
Start date:
07/20/2010
Due date:
% Done:

0%

Estimated time:
Affected version:
0.1.x
Locale:
Close

Description

Hi,

I'm running Jabberd2 2.2.8 on Ubuntu Server 10.04 (Lucid). I'm not using the default port for c2s connections. Beem 0.1.4 fails to authenticate. Disabling TLS on the server (and clients) has no effect.

I'm sure the server is ok because my desktop client (Psi) works fine. So I disabled TLS on the server and did a little work with tcpdump and Wireshark.

There are two main differences between the Psi and Beem conversations. Firstly, Psi opens with '<?xml version="1.0"?>'. Beem leaves this out, but I don't think it is important.

Both clients select DIGEST-MD5 authentication. This appears to involve two challenge-response pairs of stanzas. For both clients, the first challenge-response pair looks good. The second challenge-response pair looks like the problem.

Psi responds to the second challenge with:

<response xmlns="urn:ietf:params:xml:ns:xmpp-sasl"/>

The server returns a 'success' stanza. Beem responds with:

<response xmlns="urn:ietf:params:xml:ns:xmpp-sasl">=</response>

The server returns a 'failure' stanza. You see the difference? An '=' symbol.

I hope this helps as I would like to try Beem. At the moment I'm stuck with Jabiru which won't stay connected. :/

I attach the conversations with the server as text.

Regards,
Adam J Richardson

Files

beem.txt (1.56 KB) beem.txt Anonymous, 07/20/2010 11:55 AM
psi.txt (2.72 KB) psi.txt Anonymous, 07/20/2010 11:55 AM

Also available in: Atom PDF