Pidgin 2.5.2 failed to connect

[Stefan X]

I did not found the location to file a bug report.
It would be great to get this fixed anyway! Thanks.

stefan

Stefan X schrieb:
> Hi Stu!
> 
> Stu Tomlinson schrieb:
>> On Tue, 2008-10-21 at 15:13 +0200, Stefan X wrote:
>>> I was happy to tryout Pdigin 2.5.2 which should fix the ticket #1435
>>> ("server handshake failes due to cipher spec mismatch"). Unfortunately
>>> connecting to my Jabber account (ejabberd) through port 5222 (new TLS
>>> protocol) still fails. Connecting with old SSL to port 5223 is still
>>> possible. Here is the debug log when connection to port 5222:
>>> (15:01:50) jabber: Recv (365): <stream:stream xmlns='jabber:client'
>>> xmlns:stream='http://etherx.jabber.org/streams' id='287236560'
>>> from='example.com' version='1.0'
>>> xml:lang='en'><stream:features><mechanisms
>>> xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>DIGEST-MD5</mechanism><mechanism>PLAIN</mechanism></mechanisms><register
>>> xmlns='http://jabber.org/features/iq-register'/></stream:features>
>>> (15:01:50) account: Disconnecting account 00CD9708
>>> (15:01:50) connection: Disconnecting connection 03728510
>>> (15:01:50) jabber: XML parser error for JabberStream 036BBA00: Domain 1,
>>> code 5, level 3: Extra content at the end of the document
>>>
>>> (15:01:50) jabber: jabber_actions: have pep: NO
>>> (15:01:50) connection: Destroying connection 03728510
>>> Any ideas what may be the cause of this problem?
>> Your server is not configured to offer starttls to "upgrade" a
>> connection to SSL/TLS on port 5222. 
> 
> As I understand you, it would be a better option of my server to offer
> starttls "upgrade".
> 
> In case you know about ejabberd configuration. The appropriate lines
> look like the following.
> 
>  [{5222, ejabberd_c2s,     [{access, c2s},
>                             {max_stanza_size, 65536},
>                             starttls_required, {certfile,
> "/etc/ssl/private/mycert.pem"},
>                             {shaper, c2s_shaper}]},
> 
> Anyone knows how to adapt it?
> 
>> Pidgin should report this in a
>> better way than "cipher spec mismatch", if that is really how it is
>> reporting it.
> 
> Should I file a bug report?
> 
> Regards
> Stefan
> 
> 
>> Regards,
>>
>>
>> Stu.
>>
> 
> _______________________________________________
> Support mailing list
> Support at pidgin.im
> http://pidgin.im/cgi-bin/mailman/listinfo/support
>