- 1 Introduction
- 2 Fingerprinting Information
- 3 Whonix Fingerprint Comparison
- 4 Further Reading
- 5 References
- 6 License
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.
This section briefly addresses possible Whonix fingerprinting issues and how adversaries might use this information to verify Whonix is being used.
Various types of information can be leaked about the user's browser, (host) operating system and hardware depending on the external party in question.
- 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.
Tip: A unique fingerprint makes the user pseudonymous rather than anonymous.
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.
Firstly, Whonix solely generates Tor activity on the network. All traffic from both the Whonix-Workstation (
whonix-ws-14) and Whonix-Gateway (
whonix-gw-14) such as TBB , updates, and timesync pass through Tor. Establishing an online connection is the task of the host, so the host  is most likely using DHCP to obtain a local IP address.
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:
- The Internet connection is shared with other users that do not run Whonix.
- A browser is also used on the host. 
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.
When Whonix is started, the system clock is synchronized to make sure it slightly differs from the host clock via
whonixcheck also issues some network traffic to check for updates and news, which all passes through different circuits. This behavior might be specific to Whonix. 
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
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.
Entry Guards or Bridges
As noted in the Guard Fingerprinting chapter, using persistent 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.
Whonix Fingerprint Comparison
- TBB stands for Tor Browser Bundle. It is included in Whonix, see Tor Browser.
- Certainly less than 50,000 users, although an exact figure is yet to be published.
- Via the date object.
- Via WebGL
- 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
- Typically the entry guards are rotated after a few months.
- 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 for further exploration of this issue.
- tor-dev: entry guards and linkability
- 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.
Whonix Fingerprint wiki page Copyright (C) Amnesia <amnesia at boum dot org>
Whonix Fingerprint wiki page Copyright (C) 2012 - 2018 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.
Comments will be deleted after some time. Specifically after comments have been addressed in form of wiki enhancements. See Wiki Comments Policy.
This is a wiki. Want to improve this page? Help is welcome and volunteer contributions are happily considered! See Conditions for Contributions to Whonix, then Edit! IP addresses are scrubbed, but editing over Tor is recommended. Edits are held for moderation.
Whonix is provided by ENCRYPTED SUPPORT LP. See Imprint.