Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 3303] Problem with fragmentation at the SSL record layer

Date: Fri, 26 Mar 2010 19:40:40 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3303

Bruce Zikmund <bzikmund@xxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bzikmund@xxxxxxxxx
            Version|1.1.x (Experimental)        |1.3.x (Experimental)

--- Comment #13 from Bruce Zikmund <bzikmund@xxxxxxxxx> 2010-03-26 19:40:35 PDT ---
I also have the same problem.  The Server Hello is split into two tcp frames
because we are using a private CA.  I tried both 1.2.6 (stable) and 1.3.1
(development), and they both have the same problem:

dissect_ssl enter frame #235 (first time)
  conversation = 0656F5D0, ssl_session = 0656F964
  record: offset = 0, reported_length_remaining = 2036
dissect_ssl3_record found version 0x0300 -> state 0x11
dissect_ssl3_record: content_type 22
decrypt_ssl3_record: app_data len 2031 ssl, state 0x11
packet_from_server: is from server - TRUE
decrypt_ssl3_record: using server decoder
decrypt_ssl3_record: no decoder available
dissect_ssl3_handshake iteration 1 type 2 offset 5 length 70 bytes, remaining
2036 
dissect_ssl3_hnd_hello_common found SERVER RANDOM -> state 0x13
dissect_ssl3_hnd_srv_hello found CIPHER 0x0005 -> state 0x17
dissect_ssl3_hnd_srv_hello trying to generate keys
ssl_generate_keyring_material not enough data to generate key (0x17 required
0x37 or 0x57)
dissect_ssl3_hnd_srv_hello can't generate keyring material
dissect_ssl3_handshake iteration 0 type 11 offset 79 length 1949 bytes,
remaining 2036 
dissect_ssl3_handshake iteration 0 type 14 offset 2032 length 0 bytes,
remaining 2036

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