Wireshark · Wireshark-dev: Re: [Wireshark-dev] [Wireshark-commits] rev 20318: /trunk/epan/dissectors/ /trunk/epan/dissectors/:

[Gerald Combs <gerald@xxxxxxxxxxxxx>]

Joerg Mayer wrote:
> On Sun, Jan 07, 2007 at 10:28:46PM -0800, Gerald Combs wrote:
>>>>  Don't lower-case our SSID and passphrase, otherwise we'll create an
>>>>  incorrect PSK hash.
>>> The code still makes another mistake: The SSID is not a string - it's a
>>> binary object which may even contain 0x00 in the middle. The current
>>> airpcap code doesn't provide for that.
>> True.  The workarounds right now are to either omit the SSID (in which
>> case the passphrase will be matched against every SSID), or to use the
>> PSK hash directly, e.g. "wpa-pwd:MyPassword" or "wpa-psk:01020304...".
>> Is this sufficient, or should we add support for a hexadecimal form of
>> the SSID?
> 
> I'd like to have a binary way of entering them too. Maybe just
> \x53\0x53\x49\x44\x20\x57\x49\x54\x48\0x00\x49\x4e\x53\x49\x44\x45
> would be OK. Of course, the ssid pref handling would still need to
> be fixed.

Would a separate prefix for a text passphrase plus a hex SSID work?
Your example above would be represented as
"wpa-phx:MyPassword:53534944205749544800494e53494445".

BTW, a passphrase containing a colon (:) isn't allowed with the current
wpa-pwd form.  We'll probably want to fix that.