2 ms·
No, it should not. TCP/IP doesn't have a concept of names. I want to know that I am sending my HN password / login cookies to news.ycombinator.com. I don't have
by geofft 10y ago
No, it should not. TCP/IP doesn't have a concept of names. I want to know that I am sending my HN password / login cookies to news.ycombinator.com. I don't have any idea whether I should send my HN password to 104.20.43.44:80 or not.
You could imagine a more complex architecture involving DNSSEC and results from getaddrinfo(), but that seems to break the end-to-end principle (it is the browser that cares whether I am actually talking to news.ycombinator.com or not) and also reinvent the wheel. We have an HTTPS ecosystem that works pretty well. We do not have a secure DNS system that works pretty well, let alone a secure TCP/IP one.