Wireshark · Ethereal-dev: Re: [Ethereal-dev] [PATCH] add password hash identifier in packet-aim.c

[Guy Harris <gharris@xxxxxxxxx>]

On Sun, Apr 11, 2004 at 06:40:29PM -0400, Jon Oberheide wrote:
> "Test" as in using the old method of AIM MD5 authentication and
> observing the results in ethereal.  I am not sure if the AIM servers
> would still even support this old method of authentication if I were
> able to test it.

What's to test? Your change, which I checked in, only displays the TLV's
data as hex; it's hard to get that wrong. :-)  Besides, that doesn't
seem to be a reason not to change it to display 0x004c in the same
fashion.

> > > and am not sure of a fitting label for 0x004c.
> > 
> > "Password Hash (New)", as opposed to 0x0025's "Password Hash (Old)"?
> 
> To clarify, 0x0025 will be present as the password hash for BOTH the new
> and old methods.  However, I believe 0x004c is only present in the new
> method and is probably a simple signal to the server that the client is
> using the new method.  I'm only making these assumptions regarding
> 0x004c based on gaim's code so I wouldn't commit to any conclusions.

Then interpret "(Old)" and "(New)" as referring to the version of the
AIM code rather than the version of the password hash. :-)