-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Location remains revealed #9
Comments
There is a slight delay between when a new tab is opened and the debugger starts mocking the data. This allows for websites to get the original value of the data before it is changed. After the initial loading of a tab, this will no longer be an issue. Does it continue to be an issue when you reload the page? |
Yep :) w = open();
w.eval('alert(navigator.userAgent)'); |
That only works because its an alert opening in a new tab (tab initialized issue). But how can you save the data from an alert? If you can't then its not very useful. When you console.log it, Vytal spoofs it.
|
onmessage = console.log;
w = open();
w.eval('opener.postMessage(navigator.userAgent)'); |
Very interesting. I will look into fixing this. Although since it opens a new blank tab its not a very discrete method. Thanks |
When I select Hong Kong for example, and my physical location is in Los Angeles, TOP WINDOW and INITIAL LOAD remain unchanged and show Los Angeles. Only FRAME and WEB WORKER show Hong Kong.
The text was updated successfully, but these errors were encountered: