Network, Browser and Website Fingerprint
In this chapter, the term fingerprint refers to the specific way Whonix ™ behaves on the Internet. Those specificities could be used to determine whether a particular user is running Whonix ™ or not.
As explained on the Warning page, the default Whonix ™ configuration does not hide Tor use from network observers. However, the Whonix ™ design attempts to make Whonix ™ users indistinguishable from the rest of the Tor population, particularly Tor Browser Bundle (TBB)  users. If Whonix ™ and TBB  users have distinct fingerprints, then this information significantly degrades anonymity because the Whonix ™ user base is far smaller than the broader Tor population. 
This section briefly addresses possible Whonix ™ fingerprinting issues and how adversaries might use this information to verify Whonix ™ is in use.
Various types of information can be leaked about the user's browser, (host) operating system and hardware depending on the external party in question.
Entry Guards or Bridges
As noted in the Guard Fingerprinting chapter, using persistent Tor guards or bridges can threaten anonymity under certain circumstances:
While natural guard rotation is recommended, there are some corner cases in which an adversary could fingerprint the entry guards and de-anonymize a user. For instance:
- The same entry guards are used across various physical locations and access points.
- The same entry guards are used after permanently moving to a different physical location.
For example, if an adversary monitoring network activity observes a user connecting from multiple physical locations with persistent guards/bridges, then it can be reasonably assumed that all connections stem from the same person. Mitigating this risk requires techniques like using new Tor entry guards or configuring alternate bridges for different places.
Nick Mathewson from The Tor Project suggests additional precautions when moving networks: 
- Spoof the MAC address with randomized values on each move.
- Absolutely prevent non-Tor connections.
- Ensure a unique set of Tor entry guards (bridges) is utilized for each network you connect from. 
- Minimize the threat of stored Tor state files which record every network visited.
ISP or Local Network Administrators
The capabilities of the ISP or local network administrator are difficult to ascertain with complete certainty. This is still a general research question for The Tor Project, and not Whonix ™ developers. It is also impossible to prove a negative.
Table: Fingerprinting Domains
Firstly, Whonix ™ solely generates Tor activity on the network. All traffic from both the Whonix-Workstation ™ (
In contrast, usually TBB  users have additional network activity outside of Tor, either from another web browser or other applications. This means the proportion or volume of Tor activity might be feasible identifiers to determine whether a user is running Whonix ™ or the TBB . It is probably harder for the ISP to determine whether a single user is solely generating Tor traffic (and potentially using Whonix ™) if:
|Tor Entry Guards||Whonix ™ uses an unmodified version of Tor,  so entry guards are used as the default mechanism to connect to the Tor network.  Consequently, a Tor user will maintain the same relay as the first hop for an extended period,  which is a security feature.|
|Time Synchronization||When Whonix ™ is started, the system clock is synchronized to make sure it slightly differs from the host clock via |
|Website Traffic Fingerprinting||Website traffic fingerprinting is also an open Tor research question, which is unspecific to Whonix ™.  A related and unresearched issue is whether fingerprinting risks also apply to other traffic, such as |
In conclusion, the ability of the ISP or local network administrator to distinctly identify users who utilize TBB, Whonix ™, Tails, a custom transparent Tor proxy or similar project, depends on how well Tor actually works. As Whonix ™ is exclusively generating Tor activity on the network and relies on Tor to obfuscate that traffic, the answer depends on Tor itself and resolution of open research questions.
- The browser name and version.
- CSS media queries:
- Window dimensions.
- Desktop size.
- Widget size.
- Display type.
- A list of available extensions.
- Timezone. 
- Available fonts.
- User agent.
- Video card in use. 
- CPU and interpreter speed.
- Browser history. 
- Via exploited plugins:
- Leak the non-Tor IP address.
- Interface addresses and other machine information.
- List all plugins to fingerprint the user.
- Retrieve unique plugin identifiers.
- Read / store identifiers related to HTTP auth, DOM storage, cached scripts, client certificates and TLS session IDs.
- Browser cache.
To make it difficult to distinguish Whonix ™ and TBB  users, TBB  is included on the platform. Therefore, Whonix ™ should provide the same information as TBB  in order to generate very similar fingerprints.
Website Traffic Fingerprinting
Website fingerprinting attacks allow a local, passive eavesdropper to determine a client's web activity by leveraging features from her packet sequence. These attacks break the privacy expected by users of privacy technologies, including low-latency anonymity networks such as proxies, VPNs, or Tor. As a discipline, website fingerprinting is an application of machine learning techniques to the diverse field of privacy. To perform a website fingerprinting attack, the eavesdropping attacker passively records the time, direction, and size of the client's packets. Then, he uses a machine learning algorithm to classify the packet sequence so as to determine the web page it came from.
In simpler terms, any observer between the user and a Tor relay can see to what website a user is connecting. This includes the user's the internet service provider (ISP). The observer won't know the exact contents of the internet connection (such as user names, passwords, etc.) but the observer can know with reasonable certainty that a specific website (such as for example
google.com) has been visited. Website fingerprinting attacks are possibly also applicable to Tor bridges. That depends on the adversary's capability to detect Tor bridge traffic as well as on how well pluggable transports [archive] can hide Tor and resist website fingerprinting.
In terms of mitigating the use of these vectors in attacks against Tor, here's our recommendations for various groups in our community:
Users: Do multiple things at once with your Tor client
This might contradict Increase Protection from Malicious Entry Guards: One Guard per Application.
Whonix ™ Fingerprint Comparison
- TBB stands for Tor Browser Bundle [archive]. It is included in Whonix ™, see Tor Browser.
- Certainly less than 50,000 users, although an exact figure [archive] is yet to be published.
- tor-dev: entry guards and linkability [archive]
- Note: this is not a recommendation for non-persistent guards because a hostile DHCP server might provide new IPs until a hostile guard is chosen.
- In case of Default/Download version, it is the host's task to establish an online connection. In the case of Physical Isolation, it is the gateway's task to establish an online connection.
- This comes with the attendant risk of the user confusing one browser with another.
- Whonix ™ uses an unmodified version of Tor
- https://www.torproject.org/docs/faq#EntryGuards [archive]
- Typically the entry guards are rotated after a few months.
- https://github.com/Whonix/anon-gw-anonymizer-config [archive]
- Stream Isolation
- It is unknown if an ISP can detect whether a user has many different Tor circuits open. On the other hand, Tor seems to only open X entry guards and maintain them for a period, thus not opening as many entry guards as streams.
- See Tor Browser Design [archive] for further exploration of this issue.
- Via the date object.
- Via WebGL
Whonix ™ Fingerprint wiki page Copyright (C) Amnesia <amnesia at boum dot org>
Whonix ™ Fingerprint wiki page Copyright (C) 2012 - 2019 ENCRYPTED SUPPORT LP <firstname.lastname@example.org>
This program comes with ABSOLUTELY NO WARRANTY; for details see the wiki source code.
This is free software, and you are welcome to redistribute it under certain conditions; see the wiki source code for details.
This is a wiki. Want to improve this page? Help is welcome and volunteer contributions are happily considered! Read, understand and agree to Conditions for Contributions to Whonix ™, then Edit! Edits are held for moderation.
Copyright (C) 2012 - 2019 ENCRYPTED SUPPORT LP. Whonix ™ is a trademark. Whonix ™ is a licensee [archive] of the Open Invention Network [archive]. Unless otherwise noted, the content of this page is copyrighted and licensed under the same Freedom Software license as Whonix ™ itself. (Why?)