https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5486
--- Comment #9 from Sake <sake@xxxxxxxxxx> 2010-12-18 01:10:54 PST ---
(In reply to comment #8)
> > 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).
As a test, I changed the protocol registration on my system to use "SSL/TLS" as
abbreviated protocol name. However, to me it does not enhance things. You are
still not able to type TLS in "Decode As..." or anywhere else. If you use
"expression" to build a filter it will now show "SSL/TLS Secure Sockets
layer", which is also confusing, but adding "Transport Layer Security" there
would be a lot of text.
In the end, I think people should be aware that it's all SSL implemented in
different versions.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
