News for hackers. Stuff that matters.

A comment on Bypassing anti-incognito detection in Google Chrome. Parent comment

Re:Bypassing anti-incognito detection in Google Chrome by wtmt on Saturday July 20, 2019 @04:21AM (#20484716)
What about swap space used on the disk by the OS, transparent to the application? Is that also a concern for “file system imprint”? What’s the threat model here? The application would have to use RAM that’s never swapped for storing this sort of information. That would make it quite heavy.
[ Parent | on HN ]
Re:Bypassing anti-incognito detection in Google Chrome by geekroutine on Saturday July 20, 2019 @04:34AM (#20484747)
I think chrome devs want to limit the "file system imprint" as much as possible to enforce "no-history in incognito". There's been some discussions on finding a way around crash reporting in incognito session which stores the dump in the disk, and to my knowledge this is the only violation of this policy. [1]https://bugs.chromium.org/p/chromium/issues/detail?id=876270...
[ Parent | on HN ]