https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13743
Peter Wu <pe...@lekensteyn.nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED
--- Comment #4 from Peter Wu <pe...@lekensteyn.nl> ---
> 2) When I set the IP to any, port 0 it works for 443, but not for SSL on
> 4444.I have to add an explicit entry for port 4444 in order for it to be
> decrypted.
Port 443 is recognized as port 443 by default, setting "port 0" does not
suddenly result in a match with any port. This was previously meant to match
any connection that is dissected as TLS with a key file, but as matching keys
to certificates is automatic now, the port is useless.
Since Wireshark 2.6 has heuristics to recognize TLS on non-standard ports, I am
closing this issue.
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
