Possible information leak with Incognito Mode
Reported by
johnsmit...@gmail.com,
Mar 31 2016
|
||||||||||
Issue description
Chrome Version : 49.0.2623.110 (Official Build) m (32-bit)
URLs (if applicable) : N/A
Other browsers tested: N/A
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Safari: N/A
Firefox: N/A
IE: N/A
What steps will reproduce the problem?
(1) Open websites in regular tabs then open any websites in Incognito
(2) Re-launch Chrome by going to Help->About Chrome (then click Relaunch)
(3) Observe that tabs opened in Incognito are now in the regular non-Incognito tabs
What is the expected result?
I expected the Incognito tabs to just close the session and disappear since we're closing the browser anyway.
What happens instead?
Incognito tabs from before re-appear into normal browsing tabs after relaunching
Please provide any additional information below. Attach a screenshot if
possible.
I'd like to test this further but it was difficult to safely obtain an older version of Chrome to test this again. If someone could point me to a way to do this, it would be much appreciated.
,
Apr 1 2016
Unable to reproduce the issue on Windows 7 by following steps mentioned below. 1. Installed previous version of chrome M49-49.0.2623.108 2. Opened few pages in normal mode and incognito mode as well 3. Clicked on About --> Google chrome 4. Once chrome updated to latest version 49.0.2623.110 clicked on relaunch button 5. Observed that incognito mode got closed as expected and it never opened once after update. johnsmithprotax@ - Is this issue is seen consistently from your end? If yes, Let us know on which OS you are seeing this issue?
,
Apr 5 2016
,
Apr 6 2016
We tried to reproduce it on Mac (M48 -> M49) and could not reproduce it either.
,
Apr 9 2016
The OS I am on is Windows 10 Enterprise. Is there a way for me to test it? The only thing I can think of that relates to this is we have a company wide group policy that disables Incognito mode but I run a script to re-enable it for internal testing. It's possible that it was a race condition of sort.
,
Apr 9 2016
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 22 2016
Any inputs from 'Enterprise' team? Thank you!
,
Apr 25 2016
,
Apr 29 2016
When you say "we have a company wide group policy that disables Incognito mode but I run a script to re-enable it for internal testing," what exactly are you doing? I presume you are overriding GPO by modifying the registry or something similar? This is definitely unsupported, but it should not be triggering the behavior you are seeing. When you go to chrome://policy, what does it show for the IncognitoEnabled policy? Leaving untriaged for now until we hear back from the original reporter.
,
May 27 2016
Any updates John, is this still an issue you can reproduce?
,
Apr 18 2018
georgesak@, Can we close this? No feed back for 2 years and seems to be fixed.
,
Apr 18 2018
Done. |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by johnsmit...@gmail.com
, Mar 31 2016