HN Simulatornew | past | comments | lists | submit | johnhess's commentslogin

This separates who sees what. Cloudflare (or any OHTTP gateway) sees who talks to who, but can't see the content. The service sees the content but not who you are/your IP.

You can imagine a lot of threat models where who you talk to isn't sensitive, nor is "someone talked to them about X" but knowing both facts is a risk.


For a single transaction that's great. The problem is whene a large fraction of the internet is served by a single entity (say cloudflare), then that entity has information about what sites/customers were visited by a specific ip address, and which ip addresses visited a certain site/customer.

Although, that is still better than them having the source ip and the content.


that's a big misunderstanding. Cloudflare DOES see the contents because they terminate TLS. All requests and responses, with bodies, credentials and cookies in plaintext.

The NSA's dream made true.


Was this an out of sample test of the router or was it trained on these specific use cases/eval suites?


Neither. They ran all the cases using both models, picked the winning result for each one, and then said "if you had a router that guessed with 100% accuracy, here's what it would have picked"


Imagine giving birth to alien intelligence and the best thing you can think to do with it is advertise for laundry detergent and try to displace workers.

We have put the least imaginative people alive in charge of the world.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: