1

Normal web browsing has slowly been shifting towards HTTPS from HTTP, but this still allows the ISP to view one's traffic. What the downside to using e2e encryption for regular web browsing? Why are chat apps able to support e2ee but normal browsers/webservers aren't able to?

6
  • 4
    No, HTTPS (correctly configured) does not allow plaintext traffic to be viewed by the ISP. – nobody Jan 15 at 19:34
  • @nobody - I thought TLS allows the ISP to view the message. I read about in the context of chat apps, where TLS allows the chat app company to decrypt and read the message before re-encrypting and forwarding on to the other user, whereas e2e only allows the other user to read the message. Why then can ISP see files you download, if all traffic is unviewable? – user760900 Jan 20 at 21:42
  • 5
    @user760900: Your question is about web browsing where the ends are the client accessing the page and the server providing a page. The scenario of a browser based chat application is a different one: here the ultimate ends of the communication are not client and server but client and another client. TLS provides the encryption here only between client#1 and server and client#2 and server, but not directly between client#1 and client#2. But again, this is different from what you were asking about in your question, i.e. web browsing. – Steffen Ullrich Jan 20 at 21:51
  • @SteffenUllrich - I see. I think I overestimated my learning and I have to go back study networking a lot more. Why, though, can the ISP see files one downloads, even if it's done over HTTPS, if HTTPS is e2e? – user760900 Jan 21 at 18:16
  • 8
    @user760900: "Why, though, can the ISP see files one downloads, even if it's done over HTTPS, if HTTPS is e2e?" - the ISP can't do this and I have no idea why you think they can. – Steffen Ullrich Jan 21 at 18:22

Browse other questions tagged or ask your own question.