Wireshark-bugs: [Wireshark-bugs] [Bug 10296] Encoded WPA-PSK key exceeds 64 byte limit blocking
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 11 Mar 2015 19:02:20 +0000

changed bug 10296


What Removed Added
CC   peter@lekensteyn.nl

Comment # 7 on bug 10296 from 
(In reply to Ben from comment #4)
> Created attachment 13313 [details]
> Sample capture with a 63 character key
> 
> Enable the ARUBA_ERM protocol on UDP 5555 to see the 802.11 frames.
> 
> Key is:
> Av&OA*UwX:BIy\P8^tR2!5Wk.\ugKm8Z$m!3JXc`0Oo#rvy1QfWQ4'A3AW=QV+U

This password throws an error because the colon (:) is interpreted as a
separator. Therefore the BIy\P8... part is seen as SSID and since it is longer
than 32 chars, it throws an error.

Using wpa_passphrase from wpa_supplicant, you can calculate the 256-bit key:

$ wpa_passphrase Broadcast "$pass"
c758608746090e11f7037052a474cfefdfea962cc145fc617b57b4dda9fb822e
$ wpa_passphrase AU-Voice "$pass"
86ec8ce42a642c0bc0bd9d64fd9923927eaa0d73d557198b81aa36b1d3c1f64c

However with this the capture can still not be decrypted because the EAPOL
packet has been cut short (see frame 2760 for example or use the "eapol"
display filter).

You are receiving this mail because:
  • You are watching all bug changes.