News for hackers. Stuff that matters.

A comment on Every Byte of a TLS Connection Explained and Reproduced. Parent comment

Re:Every Byte of a TLS Connection Explained and Reproduced by deaps on Friday October 12, 2018 @09:45AM (#18201365)
A ping is very much different. A ping is (typically) simply an ICMP Echo Request, (not TCP, thus no TLS, etc). The receiving device, if accepting echo requests and configured to reply with echo replies, then responds with an ICMP Echo Reply - or some device in the middle (or the device itself could respond with an ICMP unreachable, or some other response - or quite simply drop the ICMP Echo Request entirely and silently).

*Edited an incorrect UDP reference out based on the below comment.

[ Parent | on HN ]
Re:Every Byte of a TLS Connection Explained and Reproduced by gear54rus on Friday October 12, 2018 @10:21AM (#18201590)
If I'm not mistaken, its not UDP, it's ICMP, like you said
[ Parent | on HN ]
Re:Every Byte of a TLS Connection Explained and Reproduced by deaps on Friday October 12, 2018 @10:39AM (#18201713)
Ahh yeah - good call. Totally different protocol. I guess ICMP more closely resembles UDP at the end of the day, but you're absolutely right. I edited out the incorrect UDP reference so that a person reading for the first time will not get misled. Thanks!
[ Parent | on HN ]
Re:Every Byte of a TLS Connection Explained and Reproduced by e12e on Sunday October 14, 2018 @06:44AM (#18212292)
Which is also why some poorly configured network devices firewalls will eat pings - if they for example whitelist tcp and udp protocols and drop everything else (yes, that's a bad idea).

https://security.stackexchange.com/questions/22711/is-it-a-b...

[ Parent | on HN ]