Google modifies the Filesystem API to prohibit websites from identifying whether users are Incognito mode
Earlier we mentioned that there is a logical flaw on the Incognito mode in Google Chrome. This flaw allows the website to detect if the user is in Incognito mode. The defect is mainly the file system interface provided with Google Chrome. The original Incognito mode will isolate the website file into the sandbox and close the webpage to immediately empty the sandbox. The file system interface considers the cache when a large web game is loaded and saves part of the cache in a sandbox that is not in stealth mode.
The advantage of incognito mode is that it quarantines files such as cookies to prevent accurate tagging of users, but ad networks use file interface issues to proactively identify users. If it is detected that the user is in stealth mode, other means such as canvas fingerprinting is used to continue to mark, match and track the user to push the precise advertisement. This Incognito mode seems to be meaningless, except that it doesn’t leave the history of the browser itself and wants to evade the ad tracker.
So Google will adjust the interface to prevent websites from detecting in subsequent versions. Google’s solution is to store metadata and actual files in memory, and then interact with the file system to achieve indirect read and write. However, there are weaknesses in this solution that the memory used in the privacy mode will be higher.
Until now, the latest Google Chrome Canary version opened a new test. To enable Filesystem API for Incognito mode in Google Chrome:
chrome://flags/#enable-filesystem-in-incognito
Via: techdows