Error Updating Record Invalid Key Format
SSID: rasa and Pass:rasadesign. I'm using Wireshark 1.8.1 (with X11) for Mac and I've tried to enter the string created by Wireshark's PSK generator: 1e3d2784c2693c013d5e20f58371b5b25b92ae00389eaf7c525427dd28b2c3ef but all I get is an error: "error updating record: invalid key format" I've also tried wpa-pwd with the format "rasa:rasadesign" and "rasadesign:rasa" with the same effect. I've checked everything I could find on the net about this error, but can't find this problem anywhere. What am I doing wrong? Thanks. wpa-psk format key invalid error asked 16 Aug '12, 10:29 tabula_rasa 1●1●1●1 accept rate: 0% One Answer: oldestnewestmost voted 1 As far as wpa-psk is concerned, there was a bug. I checked in a fix in r44694, which will be scheduled to be backported to the 1.8 branch. For now, if you are running Windows, you can test with any automated build version 44694 or later. If the installer isn't there yet, wait a while until the buildbots have finished creating them. I don't know what the problem is with wpa-pwd. link answered 29 Aug '12, 09:22 cmaynard ♦ 8.3k●7●35●129 accept rate: 20% Your answer toggle preview community wiki Follow this questionBy Email:Once you sign in you will be able to subscribe for any updates hereBy RSS: Answers Answers and Comments Markdown Basics *italic* or _italic_ **bold** or __bold__ link:[text](http://url.com/ "Title") image?![alt text](/path/img.jpg "Title") numbered list: 1. Foo 2. Bar to add a line break simply add two spaces to where you would like the new line to be. basic HTML tags are also supported learn more about Markdown You have a trillion packets. You need to see four of them. Riverbed Technology lets you seamlessly move between packets and flows for comprehensive monitoring, analysis and troubleshooting. Riverbed is Wireshark's primary sponsor and provides our funding. Tags: error ×182 format ×21 key ×18 wpa-psk ×9 invalid ×2 Asked: 16 Aug '12, 10:29 Seen: 5,376 times Last updated: 29 Aug '12, 09:22 Don't have Wireshark? What are you waiting for? It's free! Wireshark documentation and downloads can be found at the Wireshark website. Related questions error updating record: Invalid key format camel.EntityReleased ssl_generate_pre_master_secret: no
Wireshark-dev: Re: [Wireshark-dev] WLAN decryption using a hex PSK key Date Index Thread Index Other Months All Mailing Lists Date Prev Date Next Thread Prev Thread Next From: Sho Amano <[emailprotected]> Date: Sun, 21 Oct 2012 00:33:42 +0900 Okey, I figured out that following quick hack works for me. Now I can seethe decrypted TCP packets.(build running on Ubuntu 12.04 amd64)$ svn diffIndex: epan/dissectors/packet-ieee80211.c=================================================================== --- epan/dissectors/packet-ieee80211.c (revision 45658)+++ epan/dissectors/packet-ieee80211.c (working copy)@@ -17369,7 +17369,7 @@ keys->Keys[keys->nKeys] = key; keys->nKeys++; }- else if(dk->type == https://ask.wireshark.org/questions/13688/error-updating-record-invalid-key-format AIRPDCAP_KEY_TYPE_WPA_PMK)+ else if(dk->type == AIRPDCAP_KEY_TYPE_WPA_PSK) { key.KeyType = AIRPDCAP_KEY_TYPE_WPA_PMK; Thanks. 2012/10/20 Sho Amano <[emailprotected]> 2012/10/20 <[emailprotected]> This was broken and fixed with bug 7661 (https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7661). Perhaps its broken again (and bug needs to be reopened)? It looks different from bug 7661, because when I tried with Wireshark 1.8.3 (whichcontains the fix for the bug) I still could not decrypt the sample file.Wireshark https://www.wireshark.org/lists/wireshark-dev/201210/msg00186.html 1.8.2 (WiresharkPortable-1.8.2.paf.exe) --> Wireshark refuses to set the hex-format key, showing an error dialog which says "error updating record: Invalid key format"Wireshark 1.8.3 (WiresharkPortable-1.8.3.paf.exe)--> I do not get the error dialog and I can set the hex-format key. However I still could not decrypt WLAN frames in the file. So it looks like same situation as latest trunk.Thanks. -----Original Message----- From: Sho Amano <[emailprotected]> To: wireshark-dev <[emailprotected]> Sent: Fri, Oct 19, 2012 3:07 pm Subject: [Wireshark-dev] WLAN decryption using a hex PSK key Hi, This is the first time I send a mail to wireshark-dev. If there are something that I'm doing wrong, just let me know, thanks in advance. Recently I noticed that I can not decrypt WLAN frames that are encrypted with WPA-PSK (or PSK2), 64-digit hex format. The thing is, I could decrypt the same file using an old Wireshark (1.6.11). Is there any extra configuration that I need to run on the latest Wireshark to decrypt WLAN file with a hex key? Here is a sample file I captured using a Ralink dong
Wireshark-bugs: [Wireshark-bugs] [Bug 10296] New: Encoded WPA-PSK key exceeds 64 byte limit bloc https://www.wireshark.org/lists/wireshark-bugs/201407/msg00402.html Date Index Thread Index Other Months All Mailing Lists Date https://www.wireshark.org/lists/wireshark-bugs/201106/msg00045.html Prev Date Next Thread Prev Thread Next From: [emailprotected] Date: Sun, 20 Jul 2014 22:14:51 +0000 Bug ID 10296 Summary Encoded WPA-PSK key exceeds 64 byte limit blocking use Classification Unclassified Product Wireshark Version 1.10.8 Hardware x86 OS Windows 7 error updating Status UNCONFIRMED Severity Blocker Priority Low Component GTK+ UI Assignee [emailprotected] Reporter [emailprotected] Build Information: v1.10.8-2-g52a5244 from master-1.10 (from the windows 32bit download page today 2014/07/14) -- Edit->Preferences->Protocols->IEEE 802.11 Decryption Keys -> Edit -> New "Key type" "wpa-pwd" Paste in correctly URL encoded pass phrase that unencoded was 63 bytes error updating record long, plus the ":SSID". Get message "error updating record:Invalid key format" For some reason using the Wifi Tool bar gets you slightly different results and does not always mirror the above settings. "WPA key size out of range! Valid key size range is 8-63 ascii characters (64-504 bits)." No where can I find what characters must or must not be encoded, my passphrase has upper/lowercase, double quotes and spaces. Without the encoding the captured packets are not decrypted. You are receiving this mail because: You are watching all bug changes. Follow-Ups: [Wireshark-bugs] [Bug 10296] Encoded WPA-PSK key exceeds 64 byte limit blocking use From: bugzilla-daemon [Wireshark-bugs] [Bug 10296] Encoded WPA-PSK key exceeds 64 byte limit blocking use From: bugzilla-daemon [Wireshark-bugs] [Bug 10296] Encoded WPA-PSK key exceeds 64 byte limit blocking use From: bugzilla-daemon [Wireshark-bugs] [Bug 10296] Encoded WPA-PSK key exceeds 64 byte limit blocking use From: bugzilla-daemon Prev
Wireshark-bugs: [Wireshark-bugs] [Bug 5985] New: [IEEE 802.11] "Invalid key format" on any key e Date Index Thread Index Other Months All Mailing Lists Date Prev Date Next Thread Prev Thread Next From: [emailprotected] Date: Thu, 2 Jun 2011 02:21:05 -0700 (PDT) https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5985 Summary: [IEEE 802.11] "Invalid key format" on any key entered Product: Wireshark Version: SVN Platform: x86 OS/Version: Ubuntu Status: NEW Severity: Normal Priority: Low Component: Wireshark AssignedTo: [emailprotected] ReportedBy: [emailprotected] Created an attachment (id=6441) --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=6441) Screenshot Build Information: Version 1.7.0+svn37503 (SVN Rev Unknown from unknown) Compiled (32-bit) with GTK+ 2.24.4, with GLib 2.28.6, with libpcap 1.1.1, with libz 1.2.3.4, with POSIX capabilities (Linux), without libpcre, with SMI 0.4.8, without c-ares, with ADNS, with Lua 5.1, without Python, with GnuTLS 2.8.6, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built Mar 18 2011 15:44:36), without AirPcap. Running on Linux 2.6.38-9-generic, with libpcap version 1.1.1, with libz 1.2.3.4, GnuTLS 2.8.6, Gcrypt 1.4.6. Built using gcc 4.5.2. -- When any key as entered as wpa-pwd, the following error occurs: "error updating record: Invalid key format" The screenshot of the error is attached to the bug report. -- Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. Follow-Ups: [Wireshark-bugs] [Bug 5985] [IEEE 802.11] "Invalid key format" on any key entered From: bugzilla-daemon [Wireshark-bugs] [Bug 5985] [IEEE 802.11] "Invalid key format" on any key entered From: bugzilla-daemon [Wireshark-bugs] [Bug 5985] [IEEE 802.11] "Invalid key format" on any key entered Fro