[OTR-dev] Testing with wine rather than native windows (questions in-line)

[Ian Goldberg]

On Thu, Aug 23, 2012 at 02:12:51AM +0000, Jacob Appelbaum wrote:
> Now you'll want to enable the pidgin-otr plugin. This is done by
> checking a box in the plugins window for it.
> 
> Is there a way to flip this bit when we install the pidgin-otr plugin?
> If so, it would be *really* nice.

I don't know of a reasonable way to do this.  ("Find the user's
prefs.xml file, and parse and edit the xml to add a child element to the
loaded plugins list" is not reasonable, in my opinion.)

> I created a test account and tested it against an older OTR enabled
> client. It seemed to work well. Keys automatically generated after I
> started to chat with my other client. It took a few full round trips
> before the OTR chat picked things up - is that a result of solving the
> OTR-wars? Seems better than an OTR-war if so...

I'm not sure what you mean here.  It's certainly not intentional.  I did
notice this morning that the Windows 4.0.0-rc1 installer was built
without -O2 for libgpg-error and libgcrypt, and that it was noticeably
slow in doing asymmetric crypto.  Perhaps that's what happened?  Rebuild
according to the (amended) instructions and try that?  (Or let me know,
and I'll send you a new installer.)

> I noticed a few pidgin debug log errors. These four lines appear when
> double clicking on the OTR plugin in the plugins window:
> 
> (18:18:12) Gtk: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET
> (widget)' failed
> (18:18:12) Gtk: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET
> (widget)' failed
> (18:18:12) Gtk: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET
> (widget)' failed
> (18:18:12) Gtk: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET
> (widget)' failed

Fixed, thanks!

> I noticed a seemingly unintended consequence of the anti-logging,
> pro-privacy feature. This was in my log files after I started a chat:
> 
> (06:15:24 PM) pidgin-otr-testing at jabber.ccc.de/pidgin-wine-otr: hello
> (06:15:36 PM) xxx at jabber.ccc.de: hello
> (06:16:21 PM) xxx at jabber.ccc.de: how are you?
> (06:16:31 PM) xxx at jabber.ccc.de has not been authenticated yet.  You
> should authenticate this buddy.
> 
> Certainly an improvement but perhaps not the right balance?

This is just because OTR hadn't started yet, so logging was not yet off,
I'd think?

> I tried to SMP auth with a Q&A - when my old pidgin client canceled, the
> new one was told "An error occurred during authentication." I think that
> isn't strictly correct but perhaps that's desired?

Perhaps the error message could be improved, but not for 4.0.0.

> When I start the SMP Q&A auth process on my OTR 4.0.0-rc client, I have
> the following debug log errors:
> 
> (18:27:58) Gtk: gtk_box_pack: assertion `child->parent == NULL' failed
> (18:27:58) Gtk: gtk_box_pack: assertion `child->parent == NULL' failed
> (18:27:58) Gtk: gtk_box_pack: assertion `child->parent == NULL' failed
> 
> When I start it from my older client, my new OTR client has these debug
> log errors:
> 
> (18:29:30) Gtk: gtk_box_pack: assertion `child->parent == NULL' failed
> (18:29:30) Gtk: gtk_box_pack: assertion `child->parent == NULL' failed

Both fixed, thanks!

> When I start a new conversation from my old client with OTR, I get this
> debug log errors:
> 
> (18:33:03) g_log: purple_conversation_get_type: assertion `conv != NULL'
> failed

I can't seem to replicate this.  Can you replicate it reliably?

All of the above fixes are in the "master" branch now.

Thanks for your help!

   - Ian