there is only one way to get around this. incognito mode needs to emulate all system resources without actually making them available. even without that consideration, for things like disk storage, there is no reason[1] why incognito mode should have less access than normal mode. all websites should function as normal. the only difference is that in incognito mode everything is wiped once it is closed, and nothing is…
If Chrome encrypted the data it wrote to disk, it can throw away the encryption key and delete the file when you close the incognito window, thus giving you access to the disk securely.
Bypassing anti-incognito detection in Google Chrome
11–20 of 114 posts
Re: Bypassing anti-incognito detection in Google Chrome
#12Is there any legitimate reason to allow arbitrary web apps to use gigabytes of space on my precious SSD, especially on mobile devices? I'm becoming increasingly wary of web apps having all sorts of access to things outside of the browser, sometimes without explicit permission. Browsers should limit every app to the same amount, perhaps 100MB, or maybe even 10MB. Apps that need more should ask for permission.
Re: Bypassing anti-incognito detection in Google Chrome
#13there is only one way to get around this. incognito mode needs to emulate all system resources without actually making them available. even without that consideration, for things like disk storage, there is no reason[1] why incognito mode should have less access than normal mode. all websites should function as normal. the only difference is that in incognito mode everything is wiped once it is closed, and nothing is…
If Chrome encrypted the data it wrote to disk, it can throw away the encryption key and delete the file when you close the incognito window, thus giving you access to the disk securely.
The amount of encrypted data could be a side channel
Re: Bypassing anti-incognito detection in Google Chrome
#14Re: Bypassing anti-incognito detection in Google Chrome
#15Is there any legitimate reason to allow arbitrary web apps to use gigabytes of space on my precious SSD, especially on mobile devices? I'm becoming increasingly wary of web apps having all sorts of access to things outside of the browser, sometimes without explicit permission. Browsers should limit every app to the same amount, perhaps 100MB, or maybe even 10MB. Apps that need more should ask for permission.
I believe the “Quota Management API” [1] the author is using is an experimental API for the browser to request more space, beyond the default maximum of 5MB. [1] https://developer.chrome.com/apps/offline_storage
Re: Bypassing anti-incognito detection in Google Chrome
#16Earlier quoted context omitted.
If Chrome encrypted the data it wrote to disk, it can throw away the encryption key and delete the file when you close the incognito window, thus giving you access to the disk securely.
Any sort of file system imprint would at least leave a trace that incognito had been used. I’m not sure how much of a problem at is, and how much of a trace it currently leaves.
the browser could even encrypt all their data by default. (but for non-incognito mode with a known key) it could then write the normal and incognito data in such a way that you can't even see that there is incognito data in there if you don't have the incognito key
Re: Bypassing anti-incognito detection in Google Chrome
#17Is there any legitimate reason to allow arbitrary web apps to use gigabytes of space on my precious SSD, especially on mobile devices? I'm becoming increasingly wary of web apps having all sorts of access to things outside of the browser, sometimes without explicit permission. Browsers should limit every app to the same amount, perhaps 100MB, or maybe even 10MB. Apps that need more should ask for permission.
I believe the “Quota Management API” [1] the author is using is an experimental API for the browser to request more space, beyond the default maximum of 5MB. [1] https://developer.chrome.com/apps/offline_storage
Re: Bypassing anti-incognito detection in Google Chrome
#18Earlier quoted context omitted.
If Chrome encrypted the data it wrote to disk, it can throw away the encryption key and delete the file when you close the incognito window, thus giving you access to the disk securely.
Any sort of file system imprint would at least leave a trace that incognito had been used. I’m not sure how much of a problem at is, and how much of a trace it currently leaves.
Re: Bypassing anti-incognito detection in Google Chrome
#19Is there any legitimate reason to allow arbitrary web apps to use gigabytes of space on my precious SSD, especially on mobile devices? I'm becoming increasingly wary of web apps having all sorts of access to things outside of the browser, sometimes without explicit permission. Browsers should limit every app to the same amount, perhaps 100MB, or maybe even 10MB. Apps that need more should ask for permission.
I believe the “Quota Management API” [1] the author is using is an experimental API for the browser to request more space, beyond the default maximum of 5MB. [1] https://developer.chrome.com/apps/offline_storage
Re: Bypassing anti-incognito detection in Google Chrome
#20Earlier quoted context omitted.
Any sort of file system imprint would at least leave a trace that incognito had been used. I’m not sure how much of a problem at is, and how much of a trace it currently leaves.
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.