ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 1058] New: ESP Protocol Preferences refuses to accept 192

Date: Fri, 25 Aug 2006 20:48:32 +0000 (GMT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1058

           Summary: ESP Protocol Preferences refuses to accept 192 bit key
                    for 3DES
           Product: Wireshark
           Version: 0.99.2
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Blocker
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: jharvell@xxxxxxxxxx


I am trying to decode an ESP Security Association that I have captured.  I have
both the encryption and authentication keys.

The problem is that when I enter the following hexadecimal representation

28823e68b9818acd83b909f5901ee7e58abbf4cff4dfc1d6

of the 3DES encryption key in the 'Encryption Key #1:' text field, Wireshark
spits the following to the terminal and doesn't decrypt the payload:

<ESP Preferences> Error in Encryption Algorithm 3DES-CBC : Bad Keylen (384
Bits)

I played around with different inputs to that text field, and it seems that no
matter what character I enter, Wireshark thinks it represents 8 bits of the
key.  I am assuming it is not expecting a base-256 number; I wouldn't know what
symbols to use :).

The yellow help box that comes up when you put the pointer over that text field
should indicate what format it wants the key in (e.g., hex digits without the
0x, no spaces).  Also, it should accept the 192 bit key it claims to support.


-- 
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.