JCpac

joined 2 years ago
[–] JCpac 3 points 16 hours ago

With enough quantum tunneling, anything is possible!

[–] JCpac 1 points 16 hours ago

"Blows up blender with mind"

[–] JCpac 8 points 3 days ago* (last edited 3 days ago) (1 children)

I personally finished "Inside" in one sitting without planning to.

Phrasing...

[–] JCpac 23 points 1 week ago

I want to argue with this, but it makes too much sense

[–] JCpac 3 points 2 weeks ago

I am hilarious and you will quote everything I say

[–] JCpac 6 points 3 weeks ago

I see eye of newt, but where, prithee, is your...

sQuIrT oF lEmOn? 🍋‍🟩🤏

[–] JCpac 115 points 1 month ago (6 children)

No, it's Javascript, keep up

[–] JCpac 14 points 5 months ago

The topology enthusiast says the jug is full of glass

[–] JCpac 15 points 2 years ago

CSS is decorating a christmas tree off to the side. Some of the decorations are hovering in the air. We don't correct CSS, as it seems to be having fun regardless.

[–] JCpac 1 points 2 years ago (1 children)

Is it because of the "Host" HTTP header? I always thought it was optional, since the IP address and port were handled by the network and transport layers respectively. Turns out it's required to resolve between different virtual hosts in the same server. Today I Remembered (TIR?) that virtual hosts are a thing...

Is there anything else that might indicate the domain name in the handshake connection?

[–] JCpac 11 points 2 years ago (11 children)

I don't get it... How does this protect anything? If we want our packets to reach a web server, we need to write the server's IP address on them. If a snooper has the IP, can't they just lookup the domain name from a DNS server? Or is that not a service DNS provides?

If the IP address is encrypted, how will the routers know where to send the packets? Only solution I can think of would be onion routing... Am I wrong??

view more: next ›