Opened at 2010-06-16T19:31:58Z
Closed at 2010-06-23T00:15:24Z
#631 closed enhancement (fixed)
Bitlbee unable to connect to Openfire Jabber servers that use the Client Control plugin
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | BitlBee | Version: | 1.2.7 |
| Keywords: | Cc: | ||
| IRC client+version: | Client-independent | Operating System: | Linux |
| OS version/distro: | Gentoo |
Description
The Openfire Jabber server has a plugin that allows control of which clients can connect. When connecting with Bitlbee, the Openfire server will ouput the following and then disconnect your session:
"You are using an invalid client, and therefore will be disconnected. Please ask your system administrator for client choices."
This can be circumvented by changing the following line (line 67 in version 1.2.7) within protocols/jabber/iq.c:
xt_add_child( reply, xt_new_node( "name", "Bitlbee", NULL ) );
In my case, replacing the string "Bitlbee" with "Pidgin" allowed me to connect to the Openfire server without any errors.
My suggestion is to allow that string to be configurable within bitlbee.conf to easily allow users to change their User Agent string in the event they are confronted with a Client Control plugin such as this.
Attachments (0)
Change History (1)
comment:1 Changed at 2010-06-23T00:15:24Z by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
changeset:devel,596
That's done now. Down with these stupid restrictions. :-)