Kind of ironic that their website is using an invalid security certificate?
https://news.ycombinator.com/item?id=18201211
it mightve been invalid while he set up his cdn / reverse proxy?
Every Byte of a TLS Connection Explained and Reproduced
41–50 of 104 posts
Re: Every Byte of a TLS Connection Explained and Reproduced
#42Earlier quoted context omitted.
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 silen…
If I'm not mistaken, its not UDP, it's ICMP, like you said
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!
Re: Every Byte of a TLS Connection Explained and Reproduced
#43Author here - I was going to publish this today but it leaked out ahead of time. Enjoy! EDIT: I'm putting a CDN in place.
very nice! first thing I noticed is that at https://github.com/syncsynchalt/illustrated-tls/blob/master/... the content and samples are hardcoded into HTML - might it be nice if this was generated from some kind of JSON file or similar such that the approach you have here could be generalized to support any network protocol someone might want to annotate with descriptions?
Re: Every Byte of a TLS Connection Explained and Reproduced
#44Earlier quoted context omitted.
Sufficiently speedy for what? It's not clear what you're asking. Gmail obviously runs over TLS. It also seem pretty nippy to me, but TLS only has a minor impact on the speed.
>It also seem pretty nippy to me OK. (my experience since the redesign is the opposite.)
The TLS overhead is pretty negligible for gmail. Even though there are a lot of steps here it is only 2 round trips for the handshake. Gmail will also use TLS 1.3 (this is 1.2) if your browser supports it which cuts that down to one round trip.[0]
Re: Every Byte of a TLS Connection Explained and Reproduced
#45I have no need to look at that page at length ... but I am. This is very well made and interesting.
Re: Every Byte of a TLS Connection Explained and Reproduced
#46Has anyone of you seen such beautiful explanation for other protocols (TCP, 4-way handshake)?
Re: Every Byte of a TLS Connection Explained and Reproduced
#47Author here - I was going to publish this today but it leaked out ahead of time. Enjoy! EDIT: I'm putting a CDN in place.
Kudos! This a great work. I remember few years back when I was exploring TLS, there were no such resources and it took many months of trial and error to get some reasonable understanding. I tried doing a similar thing, but was only able to do for couple of packets [0]. Surely such an illustration will go a long way to help newbies to understand a complicated protocol.
[0] https://serializethoughts.com/2014/07/27/dissecting-tls-clie...
Re: Every Byte of a TLS Connection Explained and Reproduced
#48Cool! Would you be able to add a ascii view beside it?
Re: Every Byte of a TLS Connection Explained and Reproduced
#49Author here - I was going to publish this today but it leaked out ahead of time. Enjoy! EDIT: I'm putting a CDN in place.
very nice! first thing I noticed is that at https://github.com/syncsynchalt/illustrated-tls/blob/master/... the content and samples are hardcoded into HTML - might it be nice if this was generated from some kind of JSON file or similar such that the approach you have here could be generalized to support any network protocol someone might want to annotate with descriptions?
Yes, if I do this again I will definitely generalize it into a content generator.
(Isn't that what every site turns into eventually, a custom CMS?)
As it is it's all tcpflow, hexdump, and vim.
Re: Every Byte of a TLS Connection Explained and Reproduced
#50Cool! Would you be able to add a ascii view beside it?
Not trying to come off trite, but the RFC [0] has a simple ASCII diagram of the message flow and the structures that follow are fairly easy to read. Granted you have to hop to a couple of other RFCs to understand extensions and maybe even real world impls to understand some changes (e.g. no time in the random block of client hello), but it's worth perusing if you're interested.