Handshake errors with direct connections

[nobody]

Using the latest CVS code as well as all versions 1.0.x, I get handshake errors when connecting to some windows icq users.

12:40:50: [TCP] Requesting auto response from sulfer (#1). 12:40:50: [TCP] Connecting to sulfer (128297115) at 193.190.176.243:7276. 12:40:50: [TCP] Shaking hands with sulfer (128297115) [v6]. 12:40:50: [WRN] Handshake error, remote side closed connection. 12:40:52: [UDP] Pinging Mirabilis (#7228)...

12:43:54: [TCP] Requesting auto response from Jerre (#1). 12:43:54: [TCP] Connecting to Jerre (105902569) at 134.58.56.23:16523. 12:43:54: [TCP] Shaking hands with Jerre (105902569) [v6]. 12:43:54: [TCP] Auto response from Jerre (#1). 12:43:54: [TCP] Ack from Jerre (#1).

[nobody]

Logged In: NO

I have the same problem (and also posted a message after yours with the same thing... =P).

Well, a lot of problems are happening with my licq lately, and I think that all of them are linked to the same thing: licq can't handle the new 10 digit timestamp. Integer overflow, maybe.

But I have this direct connection problem only with clients 2000b v4.65. When I tried to make a direct connection with clients 2000b v.63 or lower, it was OK.

Victor

[nobody]

Logged In: NO

Well, a simple workaround is to ICQ all the Windows 2000b v4.65 or higher users to UNCHECK the checkbox in Icq/Preferences/Security & Privacy/Ignore/ "Do not allow direct connections with previous ICQ versions".

This is what happens: icq2000b by default "sacrifices" compatibility in exchange for "security" (how ridiculous). Anyway, I managed to convince most of them. However the new protocol should be implemented ... there are just way to many problems right now ...

[daywalker]

Logged In: YES user_id=1342

UPGRADE LICQ CVS!!!!! read http://www.rhrk.uni-kl.de/~dmuell/licq/