Mike,
The small capture file that you attached to your e-mail only one the packet
in it. For Wirshark to be able to dissect the ssl session properly, it needs
to see the whole ssl-negotiation. So we need at least all packets from this
ssl-session up to the packet showing "[malformed]".
Cheers,
Sake
----- Original Message -----
From: "Jaap Keuter" <jaap.keuter@xxxxxxxxx>
To: "Community support list for Wireshark" <wireshark-users@xxxxxxxxxxxxx>
Sent: Wednesday, September 17, 2008 7:25 AM
Subject: Re: [Wireshark-users] Certificate Request doesn'tseem properly
displayed
Hi,
If this is so you should open a bugreport on https://bugs.wireshark.org.
Describe what you see and attach the capture there, so it won't be forgotten
and
a fix can be tested.
Thanx,
Jaap
Guy Harris wrote:
On Sep 16, 2008, at 4:56 PM, Ryerse, Mike (DIS) wrote:
Wireshark 1.0.3 is displaying a specific SSLv3 packet as �Change
Cipher Spec, Encrypted Handshake Message�, while Ethereal 1.1.0
displays it as �Change Cipher Spec, Certificate Request[Malformed
Packet]�.
Normally I would think the newer software is showing it correctly.
I assume that
1) you meant "Wireshark 1.1.0", not "Ethereal 1.1.0" (the last
release that had the name "Ethereal" rather than "Wireshark" was 0.99.1)
and therefore that
2) Wireshark 1.1.0 is the newer software.
Is that the case?
_______________________________________________
Wireshark-users mailing list
Wireshark-users@xxxxxxxxxxxxx
https://wireshark.org/mailman/listinfo/wireshark-users
