5 ms·

> fullscreen Tor browser Tor recommends not going full-screen, since window size can be used as one of several identifiers.

tlrobinson 10y ago
I mean fullscreen within the VM's desktop (no need for normal GNOME/KDE/whatever desktop), which itself may not be fullscreen on host OS. It would act like a native app. If you quit the browser it shuts down the VM.
- gruez 10y ago
  >I mean fullscreen within the VM's desktop so like... maximized?
- zwindl 10y ago
  Ah, You mean the VM only have one program which is Tor browser, and when Tor terminated the VM should terminated with it.
micaksica 10y ago
The VM can go "full screen" and lock the height/width in X, then.
- trome 10y ago
  We could do stretching then when the user tries to enbiggen it, that way they don't get deanonymized!
  - micaksica 10y ago
    It is basically impossible to fully anonymize a browser as long as JavaScript+plugins are running. EFF's Panopticlick [1] and browserleaks [2] are good at explaining some of these fingerprinting vectors. [1] https://panopticlick.eff.org/ https://panopticlick.eff.org/ [2] http://browserleaks.com/ http://browserleaks.com/
homakov 10y ago
This is worst part of Tor browsing for me. 1000x800?! Are you kidding! Must be upped to macbook's 1680, or whatever is most popular resolution of a modern display
4ad 10y ago
How does this work? I would expect a generic resolution like 1920x1080 to convey much less identifiable information that some random 1583x1176 that the user might resize tor browser window to.
- easychewie 10y ago
  The idea is to not change the window size at all from the default. If this advice is followed, you minimize the possible information leak. In your example, 1583x1176 tells us that your system is capable of rendering at least that size. Given the unusual numbers, we further suspect you're not maximized on a system capable of an 1176px tall browser (much fewer of those than 1920x1080). While not uniquely identifying, it's a piece of the puzzle. https://trac.torproject.org/projects/tor/ticket/7255 https://trac.torproject.org/projects/tor/ticket/7255
  - 4ad 10y ago
    A better idea would be to simply not leak any of this information at all, or if it must, return some generic 1080p regardless of the actual size. It's a terrible UX to restrict yourself to the default window size (and depending on the window manager, the default window size might not even be respected). Plus, it's so easy to accidentally change the browser window size.

tlrobinson 10y ago

I mean fullscreen within the VM's desktop (no need for normal GNOME/KDE/whatever desktop), which itself may not be fullscreen on host OS. It would act like a native app. If you quit the browser it shuts down the VM.

gruez 10y ago
>I mean fullscreen within the VM's desktop so like... maximized?
zwindl 10y ago
Ah, You mean the VM only have one program which is Tor browser, and when Tor terminated the VM should terminated with it.

micaksica 10y ago

The VM can go "full screen" and lock the height/width in X, then.

trome 10y ago
We could do stretching then when the user tries to enbiggen it, that way they don't get deanonymized!
- micaksica 10y ago
  It is basically impossible to fully anonymize a browser as long as JavaScript+plugins are running. EFF's Panopticlick [1] and browserleaks [2] are good at explaining some of these fingerprinting vectors. [1] https://panopticlick.eff.org/ https://panopticlick.eff.org/ [2] http://browserleaks.com/ http://browserleaks.com/

homakov 10y ago

This is worst part of Tor browsing for me. 1000x800?! Are you kidding! Must be upped to macbook's 1680, or whatever is most popular resolution of a modern display

4ad 10y ago

How does this work? I would expect a generic resolution like 1920x1080 to convey much less identifiable information that some random 1583x1176 that the user might resize tor browser window to.

easychewie 10y ago
The idea is to not change the window size at all from the default. If this advice is followed, you minimize the possible information leak. In your example, 1583x1176 tells us that your system is capable of rendering at least that size. Given the unusual numbers, we further suspect you're not maximized on a system capable of an 1176px tall browser (much fewer of those than 1920x1080). While not uniquely identifying, it's a piece of the puzzle. https://trac.torproject.org/projects/tor/ticket/7255 https://trac.torproject.org/projects/tor/ticket/7255
- 4ad 10y ago
  A better idea would be to simply not leak any of this information at all, or if it must, return some generic 1080p regardless of the actual size. It's a terrible UX to restrict yourself to the default window size (and depending on the window manager, the default window size might not even be respected). Plus, it's so easy to accidentally change the browser window size.