The First Few Milliseconds of an HTTPS Connection (2009)

SPDY requires that you run it inside TLS. Within the already existing TLS handshake the client and server can advertise that they support SPDY instead of HTTP.

The way you describe it comes of as more complicated?!

Of the things to note is that nothing of SPDY describes encryption, which is why a lot of people have thought about using it without TLS via some other negotiation strategy (but nobody have really implemented this, since the value is only minor/non-existent outside internal networks).

Agreed. Brilliant, and as someone who has been looking for accessible (for numerates) ways of learning about these such things I can't thank the poster enough.

I agree. I have meddled with wireshark time and again but never really got around to digging deep enough to understand what's exactly going on. I found this article to really fulfill my desire to understand the output of wireshark. It does a really good job of explaining what's going on. Much appreciated!

And now excuse me, i have to have a look at what happens when authenticating with my wlan router at the same level of depth :)

Yep, sorry for the repost.

I figured that enough time had passed since the last time since it's such an excellent article. ;-)

Did you ever get around to finish that? I'm curious.

About twenty years ago, I was able to do something pretty much like this for typing "cat file" - e.g. syscall interface, tty drivers, network protocols, filesystems, SCSI plus pervasive things like schedulers and memory managers. I can't do that any more, though, because I've become more of a storage specialist and some of the parts I haven't kept with have changed immensely. Also, some of the implementations of those parts in Linux are frankly insane and I no longer enjoy panning through a ton of dirt for a few flecks of gold.

There's a wonderful post similar to your old project. https://plus.google.com/112218872649456413744/posts/dfydM2Cn...

Could someone point to a resource that would explain what happens when Im viewing a website on my phone driving down the highway?

What does my cellphone send to the nearest cell-phone tower? What does the cell-phone tower send to the phone company servers? How do they tie back together packets coming back from https://news.ycombinator.com back to my phone?

They can see that anyway if they intercept the traffic anyway, since the IP will be in all packets. Even better, the TCP connection will end up creating routing tables on all hops along the way.

If the host name is encrypted the server needs to provide an SSL certificate identifying itself before it knows what host the user will request. This works if there's only one host on that IP, but if there's a 1-to-1 mapping between hosts and IPs then an attacker can figure out you're going to anonymous-upload.wikileaks.org from the fundamentally public information that you're going to 190.93.240.19. The way to fix this is to use tor, not to go back to old versions of SSL.

https://en.wikipedia.org/wiki/Server_Name_Indication

Note that certificates are always sent in plain. If it's a CA-signed certificate it will always have a common name or subject alt name field that specifies what host it is for (or a wildcard), readable in plain.

If it's a self-signed certificate scrubbed from anything identifiable then a server could still try to correlate what website you visited by the public key from the certificate.

Anyone monitoring you will have seen your initial DNS query.

Because good security is hard.

"was". He hasn't posted since Nov 2011

Discovered or rediscovered by someone, and seemingly new to some on here or still appreciated by enough others to upvote.

FWIW, it was the first time I'd seen it. Very comprehensive.