licq: unknown sign on error 0x1c

[edwin]

I cannot connect to ICQ with licq anymore (since a couple of hours), neither with pidgin. If I insist on connecting, I get a rate limit error.

I was able to connect by hacking the client version build in the sources, I changed this value randomly incrementing it: buffer->PackUnsignedShortBE(0x0BB8);

However that is probably not a good solution, what should the correct value for the ver. be now?

[flynd]

It seems ICQ servers started to reject old clients.

Version has been updated as of r6387 to allow log on to work again.

For users of Licq 1.3.5 a patch is available here: Login patch for Licq 1.3.5

[human]

Also, for those of you lazy guys, you can just edit licq binary with your favourite hexeditor. As of licq 1.3.5 (i'm using debian package, version 1.3.5-6), the locations are 0x3e331 and 0x3e6f1. Just change "A" to "B".

As for other versions, the location easily found when searching binary for surrounding values (see original patch and not forget about indianess)

Happy licqing ;)

regards,
if, zeylie_at_gmail_dot_com

[human]

Just as an idea for future versions for licq - it would be great to have these values stored in a config file so users can change it more easily - just as e.g. Kopete does (see http://bugs.kde.org/show_bug.cgi?id=165502#c26, pasted below):

---

I can connect again with 0.12.7 after simply adding the default ICQ version from trunk to ~/.kde/share/config/kopeterc:

[ICQVersion] Build=0x17AB ClientId?=0x010A ClientString?=ICQ Client Country=us Lang=en Major=0x0006 Minor=0x0000 Other=0x00007535 Point=0x0000