Actually, I believe the bug is simply that 'realstart' is not assigned
at the beginning of the function. If it is set to zero, the check
correctly detects that it wasn't assigned, and things are (moderately)
happy:
--- gaim-encryption-2.38/keys.c 2005-06-11 13:40:33.000000000 -0400
+++ gaim-encryption-2.39/keys.c 2006-09-16 23:10:07.000000000 -0400
@@ -184,7 +184,7 @@
crypt_proto* proto=0;
unsigned char* key_len_msg=0;
unsigned int length;
- int realstart;
+ int realstart=0;
gchar** after_key;
gchar* resend_msg_id = 0;
Fixing this, and firing that test message again, the code will hit a bug
that was already fixed in the 3.0 branch, which will cause the plugin to
hang. So... I'm releasing a 2.39 tonight with a complete fix, and a few
other fixes backported from 3.0, and a few memory leak fixes just
reported today (Hi Max!).
Thanks all for the diligence reporting this and tracking it down,
-Bill
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
