2021-06-26 12:43:35 +0000 | received badge | ● Famous Question (source) |
2021-06-26 12:43:35 +0000 | received badge | ● Notable Question (source) |
2021-06-26 12:43:35 +0000 | received badge | ● Popular Question (source) |
2020-01-31 10:37:21 +0000 | commented answer | Wireshark showing some TLS traffic as TCP and some as TLSv1.2 Many thanks. |
2020-01-30 14:20:35 +0000 | commented question | Wireshark showing some TLS traffic as TCP and some as TLSv1.2 Looks like disabling and re-enabling all the protocols seems to have done the trick - with all protocols re-enabled I ca |
2020-01-30 13:53:30 +0000 | commented question | Wireshark showing some TLS traffic as TCP and some as TLSv1.2 Happy to do so - not sure how I post a file here..? Email me and I can send the .pcap.? |
2020-01-30 09:19:28 +0000 | commented question | Wireshark showing some TLS traffic as TCP and some as TLSv1.2 Ok - I disabled al the protocols and then enabled them one at a time ...just the ones I need: Ethernet - IP - TCP - TLS |
2020-01-30 09:10:40 +0000 | commented question | Wireshark showing some TLS traffic as TCP and some as TLSv1.2 Yes - 8444 has been added to the SL/TLS port range for HTP - no change, all packets still TCP.. Yes - agree that heuris |
2020-01-29 22:55:46 +0000 | asked a question | Wireshark showing some TLS traffic as TCP and some as TLSv1.2 Wireshark showing some TLS traffic as TCP and some as TLSv1.2 Hi I am running a CURL request against an F5 VIP, which g |