Timeline for How can I tell if Wireshark has sucessfully decrypted a capture
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 7, 2014 at 21:40 | comment | added | user164970 | "Reading more into this, the file format generated by Network Monitor 3.4 appears to be incompatible enough to be causing the problem." Please file a bug on this on the Wireshark bugzilla, with the capture attached. | |
| Jul 25, 2014 at 7:52 | comment | added | rob | There appears to be problems with Wireshark being able to decrypt Network Monitor 3.4 captured WPA2 traffic. I was able to do another capture with kismet on a Raspberry pi on the same network and was able decrypt the session without issue(so not my wierd key). Reading more into this, the file format generated by Network Monitor 3.4 appears to be incompatible enough to be causing the problem. | |
| Jul 25, 2014 at 7:45 | vote | accept | rob | ||
| Jul 22, 2014 at 0:56 | history | answered | Spiff | CC BY-SA 3.0 |