Re:HTTPS on NYTimes.com
by TurningCanadian on Tuesday January 10, 2017 @04:38PM
(#13369321)
Random coffee shop / hotel / etc wifi owners and other users on the network will only know that you're reading nytimes.com, and not which particular section/article.
[ Parent
| on HN ]
Re:HTTPS on NYTimes.com
by nathan_f77 on Wednesday January 11, 2017 @09:11AM
(#13373941)
It's actually very easy to figure out which article you're reading. I just did a little experiment for fun: https://github.com/ndbroadbent/nyt_privacy
The wifi owners can see that you're reading nytimes.com, but they can also see how much data was transmitted. All they need to do is look up the length of each article, and compare that with how much data the server returned.
Of course, I'm not too worried about hotel owners. I can imagine this technique is already being used by a lot of governments around the world.
Yes, that's assumed in what I meant. Vendors that track their users, such as Google and maybe the NYT, by implementing HTTPS are basically saying: We don't want to share that data with anyone else (e.g., 'random coffee shop / hotel / etc wifi owners'); we want to keep the monetization of our users' privacy to ourselves.
Re:HTTPS on NYTimes.com
by TurningCanadian on Tuesday January 10, 2017 @04:40PM
(#13369343)
And your session cookie..
Re:HTTPS on NYTimes.com
by semiquaver on Tuesday January 10, 2017 @04:46PM
(#13369406)
Session cookies are transmitted as headers which are protected by HTTPS.
Re:HTTPS on NYTimes.com
by TurningCanadian on Thursday January 12, 2017 @01:14PM
(#13384622)
Sorry, I meant that as an additional reply to
"If so, this change amounts to not protecting user privacy as much as insisting that only the NYT can monetize their users' privacy."
The cookie is now hidden from the MITM. Before, not only could they see what pages you see, but they could login as you.