[Pidgin] #15770: libpurple/OSCAR mishandles multiple IM_TEXT tags

[Pidgin]

#15770: libpurple/OSCAR mishandles multiple IM_TEXT tags
-------------------------------------------------+-------------------------
 Reporter:  Auggie                               |       Owner:
     Type:  patch                                |  MarkDoliner
Milestone:  Patches Needing Review               |      Status:  new
  Version:  2.10.7                               |   Component:  AIM
 Keywords:  IM_DATA  IM_TEXT  ICBM__IM_SECTION   |  Resolution:
  ICBM__IM_DATA_TAGS ICBM__CHANNEL_MSG_TOHOST    |
  ICBM__CHANNEL_MSG_TOCLIENT                     |
-------------------------------------------------+-------------------------

Comment (by Auggie):

 I think the easiest way to test it would be to modify a simple OSCAR-
 speaking client.
 I suggest getting BSF (http://bsflite.sf.net) and changing
 imcomm_im_send_message
 in imcomm/snac.c to build 1 or more additional IM_DATA TLVs.

 The AIM servers seem to preserve the IM_DATA TLVs (rather than combining
 them when
 that is possible), so the receiving client should get exactly what was
 sent.
 You should find that Pidgin (mis)behaves as described in the report, but
 other AIM clients
 (AOL's, Mac OS X Messages) do the right thing.

 If you would like me to make the modifications to BSF that I mentioned, I
 could do
 that and send you a patch for it so you can test.

 Barry

-- 
Ticket URL: <https://developer.pidgin.im/ticket/15770#comment:4>
Pidgin <http://pidgin.im>
Pidgin