3 ms·
Quote: It's true that carriers already know what URLs you're visiting when you use their network Is that true for https?
by brlewis 15y ago
Quote: It's true that carriers already know what URLs you're visiting when you use their network
Is that true for https?
- podperson 15y agoThey know the domain but not the rest of the url or the data being exchanged. But hey, he's a political science writer so he clearly knows more about all this than any of us.
- sp332 15y agoThey only know which server you're visiting, so they can route the packets properly. But the headers are encrypted, so they shouldn't get the whole URL. https://en.wikipedia.org/wiki/Https#Network_layers https://en.wikipedia.org/wiki/Https#Network_layers
- brlewis 15y agoI'm familiar with the normal workings of https. What I'd like to know is if there's anything special about cellphone browsers such that the carriers act as MITM (like with Kindle Fire). What I can't imagine, though, is any way they could MITM the URL and not be able to MITM the rest of the HTTP request and response.
- lurker17 15y agoObviously the browser can MITM anything. The browser renders the page content for you and translates your input into network traffic.
- rmc 15y agoAll ISP can do loads of packet sniffing. Remember FireSheep? So in theory they could intercept every non ssl request and see what sites your going to. But things like that might be illegal, and expensive. Kindle Fire is a different kettle of fish and is almost certainly not used by most ISPs.
- marshray 15y agoNon-smartphone browsers will often use a bastardization of https that does allow the carriers to perform MitM interception. This should* not be the case with smartphones however, particularly when connected to wifi and not even transferring data via the carrier. *The carrier may have planted an SSL trusted CA cert on your phone before giving it to you.