Wireshark-bugs: [Wireshark-bugs] [Bug 5486] SSL but not TLS appear in 'Enabled Protocols' and as
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5486
--- Comment #8 from Sake <sake@xxxxxxxxxx> 2010-12-15 01:23:54 PST ---
Back to SSL/TLS :-)
(Lets continue the BOOTP/DHCP discussion on the dev-list)
(In reply to comment #1)
> I'm tempted to completely rename the SSL dissector to TLS, given that SSLv3 is
> from 1996 (draft-freier-ssl-version3-02.txt) and TLS 1.0 came out way back in
> 1999 (RFC 2246) :)
Even though the name of the protocol has changed, it is still widely referred
to as SSL. Nobody is requesting a TLS certificate at the certificate
authorities. There is no httpt protocol nor ftpt protocol. They all are
referred to as xxx over SSL.
> The dissector does already populate the protocol column with the current
> protocol version being used (SSL or TLS), but as you stated, it shows up as
> "SSL" and "Secure Socket Layer" elsewhere.
I think that everybody who is analyzing TLS packets should know that it's
family name is actually SSL.
So either we keep things as they are now and maybe use SSL/TLS in the "Decode
As.." dialog (if that is at all possible without changing the name in other
places).
Or we should split the dissection into SSLv2, SSLv3, TLSv1.0, TLSv1.1 and
TLSv1.2. But then a user might be confused by seeing a SSLv2 client hello that
is answered with a TLSv1.1 ServerHello. Not seeing the ServerHello when
filtering on ssl.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
