Live data from Hacker News

Information Leaks via Safari’s Intelligent Tracking Prevention

arxiv.org

21–30 of 37 posts

Re: Information Leaks via Safari’s Intelligent Tracking Prevention

#21

Earlier quoted context omitted.

Chrome is just trying to start catching up to where Safari and Firefox are.

Chrome is restricting fingerprinting, but they still ship google analytics in the browser itself so it's harder to block. They'll only really block fingerprinting in their browser when they have no use for it.

First I'm hearing of this. Citation?

Re: Information Leaks via Safari’s Intelligent Tracking Prevention

#22
post #3

Reposting from the other [1] thread: Basically Safari keeps track of which domains are being requested in a 3rd party context (i.e. I load example.com in my browser and the page loads the facebook sdk - Safari increments a counter for facebook by 1). Once a given domain reaches 3 hits, Safari will strip cookies and some other data in 3rd party requests to that domain. The problem is that advertisers can use this to f…

The other article was

https://www.ft.com/content/916a766a-3d27-11ea-a01a-bae547046...

http://archive.md/lhUeF

Re: Information Leaks via Safari’s Intelligent Tracking Prevention

#23

Wow. I understand ITP's high level design, but didn't know it's implementation is so naive. Maintaining global database with a few rules which can be easily reverse engineered and giving its access to any documents? How did it go through the internal review process? Does Apple have any privacy/security review process for its major products? I understand that privacy engineering is very hard and sometime can get not v…

Things started getting explicitly dangerous a couple years ago, internally we always did no wrong, externally, everyone was praising us for being the one company focused on privacy...when pretty much everyone who cared to think about knew why we didn't encrypt iCloud backups, and knew we were collecting app store searches, News articles viewed, and location for ad targeting (this is easily found in public documentation). I left shortly after I realized how little my colleagues knew, cared, and were willing to think about it – a manager on Safari refused to believe that data was being collected, refused to read our documentation on it, and told those concerned that we needed to read up on differential privacy. (note: that didn't apply at all in the conversation, they werr reaching for buzzwords they remembered)

Re: Information Leaks via Safari’s Intelligent Tracking Prevention

#24
post #8
post #5

There is a fundamental difficulty when trying to implement privacy: A limit on the disclosure of information is itself a disclosure of information. A good privacy design needs to confront this issue directly. Sometimes there's nothing to be done. I think in some cases it's mathematically unsolvable (cf. Cynthia Dwork's paper on Differential Privacy). But an explicit consideration can at least surface some trade-offs.…

It makes me think of password requirements. Isn't it bad to earmark a password as requiring certain things rather than to let the possibilities be completely open?

The US organization NIST finally got the memo, and now recommends no password requirements, and no length limits, and encourages long, random passwords. My passwords are generally 64 chars of random, when I can get away with it.

Re: Information Leaks via Safari’s Intelligent Tracking Prevention

#25

Earlier quoted context omitted.

Chrome is just trying to start catching up to where Safari and Firefox are.

Chrome is restricting fingerprinting, but they still ship google analytics in the browser itself so it's harder to block. They'll only really block fingerprinting in their browser when they have no use for it.

I do not see connections on my network to google when I open and browse to 3rd party sites.

Can you show me that's true? If it is, that's fairly interesting.

Re: Information Leaks via Safari’s Intelligent Tracking Prevention

#26
We've addressed the issues disclosed to us, and if you try any of the 5 POCs in the paper you will find they no longer work in the latest Safari. Details of the fixes here: https://webkit.org/blog/9661/preventing-tracking-prevention-...

There may be room for more improvement here but be aware what the POCs illustrate is not an active vulnerability any more.

In addition, we don't believe this channel was ever exploited in the wild.

(If anyone is aware of other issues in this area, I encourage you to practice responsible disclosure and report to Apple or to the WebKit project.)

Re: Information Leaks via Safari’s Intelligent Tracking Prevention

#27
post #26

We've addressed the issues disclosed to us, and if you try any of the 5 POCs in the paper you will find they no longer work in the latest Safari. Details of the fixes here: https://webkit.org/blog/9661/preventing-tracking-prevention-... There may be room for more improvement here but be aware what the POCs illustrate is not an active vulnerability any more. In addition, we don't believe this channel was ever exploite…

[deleted]

Re: Information Leaks via Safari’s Intelligent Tracking Prevention

#28
post #3

Reposting from the other [1] thread: Basically Safari keeps track of which domains are being requested in a 3rd party context (i.e. I load example.com in my browser and the page loads the facebook sdk - Safari increments a counter for facebook by 1). Once a given domain reaches 3 hits, Safari will strip cookies and some other data in 3rd party requests to that domain. The problem is that advertisers can use this to f…

Why the counter in the first place? I'd rather they block cookies from any domain I'm not currently viewing.

Re: Information Leaks via Safari’s Intelligent Tracking Prevention

#29
post #26

We've addressed the issues disclosed to us, and if you try any of the 5 POCs in the paper you will find they no longer work in the latest Safari. Details of the fixes here: https://webkit.org/blog/9661/preventing-tracking-prevention-... There may be room for more improvement here but be aware what the POCs illustrate is not an active vulnerability any more. In addition, we don't believe this channel was ever exploite…

If only we had the same level of transparency in native apps. At least in Chrome, Firefox, Safari - you have dedicated large groups of engineers thinking about privacy, security and stability. Compared to native iOS/android where you get isolated groups of developers able to exploit and track with little to no visibility from end users - let alone access to source code for review by third party software engineers like we have on the web.... it's madding that apple doesn't invest more in its browser and yet pretends to care so much about privacy - of the major three browsers - apple definitely _seems_ to underinvest when it comes to web technology...

Re: Information Leaks via Safari’s Intelligent Tracking Prevention

#30
post #7

I’ve been following privacy issues and technology for a while, but haven’t come across a foundational discussion of (a) the merits of and (b) technical implementations of different approaches to avoid fingerprinting: “hiding” vs “blending in”(making me look identical to countless others - maybe even randomizing who I look like in a smart way). I wonder if any subject area experts reading this thread would be willing…

As Mirimir, I don't worry at all about fingerprinting. Because that persona is totally focused on privacy and anonymity stuff. Perhaps unusually so, but so it goes.

But then, here's the thing. My other personas are similarly focused, but on other stuff. And they don't use English.

A determined global adversary could link them through traffic analysis. But it's a big Internet, and I don't make it easy.

Post reply on HN