Package: bitlbee
Version: 0.92-1
Authorization failure happens, if trying to use a jabber account with a
password longer than 31 characters.
Applied is a patch against some version that made jabber work for me.
It fixes the problem by changing two structs, allowing 127 chars long
passwords instead.
A more correct fix would probably be to fail or warn the user when a to
long password is added. Or maybe even allocate memory dynamically, but
that might be overkill.
--
/Martin
diff -ur bitlbee-20050825/protocols/nogaim.h
bitlbee-20050825-patched/protocols/nogaim.h
--- bitlbee-20050825/protocols/nogaim.h Sat Oct 30 01:42:07 2004
+++ bitlbee-20050825-patched/protocols/nogaim.h Thu Aug 25 16:53:21 2005
@@ -94,7 +94,7 @@
char username[64];
char displayname[128];
- char password[32];
+ char password[128];
guint keepalive;
/* stuff needed for per-connection idle times */
guint idle_timer;
@@ -148,7 +148,7 @@
struct aim_user {
char username[64];
char alias[SELF_ALIAS_LEN];
- char password[32];
+ char password[128];
char user_info[2048];
int options;
int protocol;
