Bug 26704 - Unable to connect to Jabber server with telepathy-haze
Summary: Unable to connect to Jabber server with telepathy-haze
Status: RESOLVED DUPLICATE of bug 19018
Alias: None
Product: Telepathy
Classification: Unclassified
Component: haze (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-22 10:58 UTC by anand
Modified: 2010-07-19 03:32 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description anand 2010-02-22 10:58:17 UTC
Linux distribution: Fedora 12 (reproducible on Ubuntu 9.04 as well)
telepathy-haze version: telepathy-haze-0.3.1-3

Steps to reproduce bug:

Step-1. Download example from
http://people.collabora.co.uk/~danni/telepathy-book/examples/python_simple_presence/example.py
Step-2. Run the example with jid argument. I used a Jabber server in the local network (not going to the Internet).
   #python example.py <jid>

   The code will prompt for password. Enter the password. It should connect to the Jabber server and perform the function of an "echobot". Reply back the messages sent to it.

Step-3. Replace the gabble connection manager with haze. Change line #108 in the program as follows:
   Change self.cm = cm = reg.GetManager('gabble')
   to     self.cm = cm = reg.GetManager('haze')

Step-4. Repeat Step-2.

Observation: Connection to the Jabber server will not be established. On the screen, the last message printed is "Establishing connection..."
Comment 1 Will Thompson 2010-02-22 12:18:56 UTC
Try passing an additional parameter:

  'require-encryption': False

I bet it's because your local XMPP server has an SSL certificate that libpurple doesn't trust, at which point the whole connection process just hangs: bug #19018.
Comment 2 anand 2010-02-22 15:20:52 UTC
(In reply to comment #1)
> Try passing an additional parameter:
> 
>   'require-encryption': False
> 
> I bet it's because your local XMPP server has an SSL certificate that libpurple
> doesn't trust, at which point the whole connection process just hangs: bug
> #19018.
> 

I tried giving this additional parameter to "RequestConnection" call. But still same behavior.
Comment 3 Will Thompson 2010-02-22 15:32:07 UTC
Upon closer inspection, setting that to false won't prevent the cert verification dialog. So this is indeed more fallout from bug #19018.
Comment 4 anand 2010-02-22 16:33:41 UTC
(In reply to comment #3)
> Upon closer inspection, setting that to false won't prevent the cert
> verification dialog. So this is indeed more fallout from bug #19018.
> 
Can you suggest a workaround?
Comment 5 Will Thompson 2010-02-22 16:44:15 UTC
(In reply to comment #4)
> (In reply to comment #3)
> > Upon closer inspection, setting that to false won't prevent the cert
> > verification dialog. So this is indeed more fallout from bug #19018.
> > 
> Can you suggest a workaround?

Get an SSL certificate libpurple trusts out of the box; install your certificate's CA; turn off SSL on your local server.
Comment 6 Simon McVittie 2010-07-19 03:32:12 UTC

*** This bug has been marked as a duplicate of bug 19018 ***


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.