From ian@cypherpunks.ca Fri Apr 1 02:52:21 2005 From: ian@cypherpunks.ca (Ian Goldberg) Date: Thu, 31 Mar 2005 21:52:21 -0500 Subject: [OTR-dev] Happy Birthday to me. ;-) Message-ID: <20050401025221.GV30200@smtp.paip.net> We just passed 4000 unique IP downloads from the main site. I finally tracked down the problem that was causing some people using otrproxy with Trillian to be unable to connect to the AIM network, sometimes. [For some it was occsaional; for some it was always; for some it was never.] We'll put out 0.3.0 of the proxy with this fix (and additional UI) next week. As I mentioned, the bug was only occasional. Bugs like that are always hard to figure out. Top that off with the fact that I don't run Trillian, or indeed Windows (so all the actual test runs needed to be done by someone else). It turns out the bug is in Trillian, and is this: - When Trillian needs to make a connection to the AIM server via a SOCKS5 proxy, it: - connects to the proxy - sends some SOCKS5 messages back and forth, ending with a message from the proxy to Trillian - sends AIM protocol messages back and forth, starting with a message from the AIM server (via the proxy) to Trillian. (This is exactly as it should be.) - We have verified that if Trillian receives the first AIM message very close in time to the last SOCKS5 message (both are coming from the proxy to Trillian), Trillian never sees the AIM message, and never starts its side of the AIM protocol. I surmise this is the bug (but of course I've never actually touched a running Trillian, so who knows): 1. Trillian's SOCKS5 handler is doing something like: recv(proxysocket, bigbuf, sizeof(bigbuf), 0); 2. It handles the SOCKS5 message received into bigbuf. 3. When it sees the final SOCKS5 message, it starts the AIM protocol. 4. The AIM protocol also does something like: recv(proxysocket, bigbuf, sizeof(bigbuf), 0); So what's the problem? If the first AIM message has *also* arrived before Trillian gets to step 1, bigbuf will contain *both* the final SOCKS5 message, _and_ the first AIM message. But Trillian apparently ignores that fact, and eventually times out waiting for it in step 4. [Or, more likely, in the select() guarding step 4.] Fix: after processing the final SOCKS5 message in bigbuf in step 2, see if there's anything left over, and if so, treat it as a message received in step 4. So we'll submit this bug report to Trillian tomorrow. But what can we do? For now, we just hardcode a 1 second delay before sending the first AIM message from the proxy to the client on Win32. [This fix will be in 0.3.0.] Many thanks to Michael Wright, Shar van Egmond, and Ian Neal for their invaluable debugging assistance! Birthday Bughunting: what a Blast! ;-) - Ian From bfordham@socialistsushi.com Mon Apr 4 15:27:15 2005 From: bfordham@socialistsushi.com (Bryan L. Fordham) Date: Mon, 4 Apr 2005 10:27:15 -0400 Subject: [OTR-dev] Jabber proxy Message-ID: <20050404142715.GD1174@socialistsushi.com> Since my preferred IM client is not gaim, I'm looking into making a general jabber proxy that will allow most any client to use OTR. I didn't see anything in the archives, but thought I'd ask just to be sure: anyone working on something like this already? Thanks --B From ian@cypherpunks.ca Mon Apr 4 15:55:41 2005 From: ian@cypherpunks.ca (Ian Goldberg) Date: Mon, 4 Apr 2005 10:55:41 -0400 Subject: [OTR-dev] Jabber proxy In-Reply-To: <20050404142715.GD1174@socialistsushi.com> References: <20050404142715.GD1174@socialistsushi.com> Message-ID: <20050404145541.GO30200@smtp.paip.net> On Mon, Apr 04, 2005 at 10:27:15AM -0400, Bryan L. Fordham wrote: > Since my preferred IM client is not gaim, I'm looking into making a general > jabber proxy that will allow most any client to use OTR. I didn't see > anything in the archives, but thought I'd ask just to be sure: anyone > working on something like this already? It's part of the future plans for otrproxy, but it's not there yet. If you'd like to add jabber support to otrproxy, that'd be awesome. [Hell, if you want to write your own proxy from scratch, that'd be fine, too. ;-) ] jabber is slated to be the next protocol supported by otrproxy. - Ian From nathanw@MIT.EDU Mon Apr 11 22:29:02 2005 From: nathanw@MIT.EDU (Nathan J. Williams) Date: 11 Apr 2005 17:29:02 -0400 Subject: [OTR-dev] patch to gaim-otr for c89 compliance Message-ID: I recently added libotr and gaim-otr to NetBSD pkgsrc, and a bulk build of pkgsrc on an older machine turned up a bit of code with a declaration after code (legal C++ and C99, but not C89). Here's a patch for this minor issue. - Nathan --- gtk-dialog.c.orig 2005-04-11 11:18:52.000000000 -0400 +++ gtk-dialog.c 2005-04-11 11:19:44.000000000 -0400 @@ -156,6 +156,7 @@ const char *protocol_print; GtkWidget *label; GtkWidget *dialog; + OtrgDialogWaitHandle handle; p = gaim_find_prpl(protocol); protocol_print = (p ? p->info->name : "Unknown"); @@ -166,7 +167,7 @@ dialog = create_dialog(GAIM_NOTIFY_MSG_INFO, title, primary, secondary, 0, &label); - OtrgDialogWaitHandle handle = malloc(sizeof(struct s_OtrgDialogWait)); + handle = malloc(sizeof(struct s_OtrgDialogWait)); handle->dialog = dialog; handle->label = label; From me@nikita.ca Mon Apr 11 22:42:11 2005 From: me@nikita.ca (Nikita Borisov) Date: Mon, 11 Apr 2005 14:42:11 -0700 Subject: [OTR-dev] patch to gaim-otr for c89 compliance In-Reply-To: References: Message-ID: <16f0378d050411144215de888b@mail.gmail.com> ------=_Part_2504_4123447.1113255731608 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Thanks for the patch, Nathan. This will be fixed in the next source release= =20 of gaim-otr. - Nikita ------=_Part_2504_4123447.1113255731608 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Thanks for the patch, Nathan.  This will be fixed in the next source r= elease of gaim-otr.

- Nikita
------=_Part_2504_4123447.1113255731608-- From ian@cypherpunks.ca Tue Apr 12 23:18:48 2005 From: ian@cypherpunks.ca (Ian Goldberg) Date: Tue, 12 Apr 2005 18:18:48 -0400 Subject: [OTR-dev] patch to gaim-otr for c89 compliance In-Reply-To: References: Message-ID: <20050412221848.GQ1071@smtp.paip.net> On Mon, Apr 11, 2005 at 05:29:02PM -0400, Nathan J. Williams wrote: > > I recently added libotr and gaim-otr to NetBSD pkgsrc, and a bulk > build of pkgsrc on an older machine turned up a bit of code with a > declaration after code (legal C++ and C99, but not C89). Here's a > patch for this minor issue. Thanks. This was reported earlier, and is already in CVS for the next version. - Ian From evan.s@dreskin.net Thu Apr 28 21:13:06 2005 From: evan.s@dreskin.net (Evan Schoenberg) Date: Thu, 28 Apr 2005 15:13:06 -0500 Subject: [OTR-dev] OTR over Jabber in Gaim / Adium Message-ID: --Apple-Mail-10--1026967095 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Hey, guys, I've run into a problem that I'm not quite where to begin for fixing it. When attempting to initiate OTR over Jabber in Adium, OTR throws an error that "You are not currently connected to [account you really ARE connected to and having a chat with]/Adium (Jabber)." I think the problem is that the resource -- "/Adium" is making the account lookup fail... but I'm not sure. Any thoughts? I don't have otr-gaim compiled for gaim so can't test it independent of Adium, but as far as I'm aware gaim-otr is responsible for all those lookups so it shouldn't be Adium's fault... not that means it couldn't be. Thanks, Evan www.adiumx.com --Apple-Mail-10--1026967095 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1 Hey, guys,

I've run into a problem = that I'm not quite where to begin for fixing it.=A0 When attempting to = initiate OTR over Jabber in Adium, OTR throws an error = that
"You are not currently connected to [account you really ARE = connected to and having a chat with]/Adium (Jabber)."=A0

I think the problem is = that the resource -- "/Adium" is making the account lookup fail... but = I'm not sure.=A0 Any thoughts?=A0 I don't have otr-gaim compiled for = gaim so can't test it independent of Adium, but as far as I'm aware = gaim-otr is responsible for all those lookups so it shouldn't be Adium's = fault... not that means it couldn't be.

Thanks,
Evan
www.adiumx.com
= --Apple-Mail-10--1026967095-- From ian@cypherpunks.ca Thu Apr 28 23:21:58 2005 From: ian@cypherpunks.ca (Ian Goldberg) Date: Thu, 28 Apr 2005 18:21:58 -0400 Subject: [OTR-dev] OTR over Jabber in Gaim / Adium In-Reply-To: References: Message-ID: <20050428222158.GI1071@smtp.paip.net> On Thu, Apr 28, 2005 at 03:13:06PM -0500, Evan Schoenberg wrote: > Hey, guys, > > I've run into a problem that I'm not quite where to begin for fixing > it. When attempting to initiate OTR over Jabber in Adium, OTR throws > an error that > "You are not currently connected to [account you really ARE connected > to and having a chat with]/Adium (Jabber)." > > I think the problem is that the resource -- "/Adium" is making the > account lookup fail... but I'm not sure. Any thoughts? I don't have > otr-gaim compiled for gaim so can't test it independent of Adium, but > as far as I'm aware gaim-otr is responsible for all those lookups so > it shouldn't be Adium's fault... not that means it couldn't be. It sounds like you're sometimes passing "foo@jabber.org/Adium" as the accountname parameter to libotr, and sometimes just "foo@jabber.org". libotr doesn't care which you use, so long as you're consistent. - Ian From evan.s@dreskin.net Fri Apr 29 07:31:56 2005 From: evan.s@dreskin.net (Evan Schoenberg) Date: Fri, 29 Apr 2005 01:31:56 -0500 Subject: [OTR-dev] OTR over Jabber in Gaim / Adium In-Reply-To: <20050428222158.GI1071@smtp.paip.net> References: <20050428222158.GI1071@smtp.paip.net> Message-ID: <63D8CFDD-FE48-4E05-ADE2-56F396238A01@dreskin.net> Good thinking... while that wasn't the problem, detailed debug logging while looking for where that might happen led me to find it, which was that somehow gaim was getting two different objects for foo@jabber.org/Adium in its hash table of accounts, so gaim_find_account() was returning a different object than the one which was actually connected. Craziness. Fixed now, working great. :) Adium 0.80 is about ready for release... so the number of people using OTR will soon increase significantly. Very exciting to have support built in, thanks for all your help. :) -Evan On Apr 28, 2005, at 5:21 PM, Ian Goldberg wrote: > On Thu, Apr 28, 2005 at 03:13:06PM -0500, Evan Schoenberg wrote: > >> Hey, guys, >> >> I've run into a problem that I'm not quite where to begin for fixing >> it. When attempting to initiate OTR over Jabber in Adium, OTR throws >> an error that >> "You are not currently connected to [account you really ARE connected >> to and having a chat with]/Adium (Jabber)." >> >> I think the problem is that the resource -- "/Adium" is making the >> account lookup fail... but I'm not sure. Any thoughts? I don't have >> otr-gaim compiled for gaim so can't test it independent of Adium, but >> as far as I'm aware gaim-otr is responsible for all those lookups so >> it shouldn't be Adium's fault... not that means it couldn't be. >> > > It sounds like you're sometimes passing "foo@jabber.org/Adium" as the > accountname parameter to libotr, and sometimes just "foo@jabber.org". > libotr doesn't care which you use, so long as you're consistent. > > - Ian > _______________________________________________ > OTR-dev mailing list > OTR-dev@lists.cypherpunks.ca > http://lists.cypherpunks.ca/mailman/listinfo/otr-dev > >