http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=54908
User: guy
Date: 2014/01/22 08:05 PM
Log:
At least according to
http://web.archive.org/web/20080308233204/http://dev.aol.com/aim/oscar/#SNAC
"In general strings are not NULL terminated and are encoded using UTF8."
It also says
Authentication
Over the years, the AIM backend has supported several different
methods for authentication. ...
When a client collects the loginId and password for the user it
should not normalize them in any manner. It also should not
prevent the user from entering certain characters as the AIM
name space is constantly changing. For example, currently the
AIM name space is ASCII based, but in the future that may
change. In general, the client should not perform input
checking and instead allow the backend to reject bad values.
which also suggests not assuming ASCII.
So use ENC_UTF_8 in most cases.
For actual messages, it says:
An IM can be encoded in the following different forms:
Name Value Notes
ASCII 0 ANSI ASCII -- ISO 646
UNICODE 2 ISO 10646.USC-2 Unicode
LATIN_1 3 ISO 8859-1
so, if that's the case, the dissector should choose beween
ENC_ASCII|ENC_NA, ENC_UCS_2|ENC_appropriate_ENDIAN, and
ENC_ISO_8859_1|ENC_NA.
Use tvb_get_string_enc() with an encoding rather than tvb_get_string().
Directory: /trunk/epan/dissectors/
Changes Path Action
+2 -2 packet-aim-location.c Modified
+1 -1 packet-aim-messaging.c Modified
+1 -1 packet-aim-signon.c Modified
+5 -5 packet-aim-ssi.c Modified
+1 -1 packet-aim-userlookup.c Modified
+4 -4 packet-aim.c Modified