MAC Address

From Whonix
Jump to navigation Jump to search

MAC Address Spoofing and Tracking Threats

MAC Address Documentation[edit]

Kicksecure seal
Kicksecure Hardened

Redirection to Kicksecure Documentation

Incomplete: This wiki page is incomplete by design. It only includes details specific to Whonix. For full understanding, please follow the link below to the Kicksecure wiki, which provides more complete background and instructions.

  • Introduction: Whonix Documentation Introduction, User Expectations, Footnotes and References, User Expectations - What Documentation Is and What It Is Not
  • Whonix is based on Kicksecure: Whonix is built on top of Kicksecure. This means it uses many of the same security tools, design concepts, and configurations.
  • Kicksecure is based on Debian: Kicksecure is developed using Debian as its base. Debian is a widely used, stable, and free Linux operating system.
  • Inheritance: As a result, Whonix is also based on Debian.
  • Debian is GNU/Linux-based: Debian is built using the GNU/Linux operating system. GNU provides essential tools and Linux is the system’s kernel (core).
  • Shared documentation benefits: Since each system is based on the one below it, a lot of documentation and guides are shared. This reduces the need to duplicate information.
  • Inherited documentation: Most instructions and explanations are inherited from Kicksecure or Debian, unless otherwise specified.
  • Shared principles: The systems share similar security goals and setup instructions. In most cases, users can follow Kicksecure documentation when using Whonix.
  • Keep using Whonix: This does not mean users should switch to Kicksecure. This page only points to related, helpful information.
  • Where to apply the instructions: Follow the instructions inside Whonix unless specifically stated otherwise.
  • Wiki editors notice: This information is pulled from a reusable wiki template: upstream_wiki. (See which pages use this.)
  • Comparison: Whonix versus Kicksecure
  • Documentation compatibility: Because Whonix is based on Kicksecure, you can often follow Kicksecure’s instructions as long as you apply them in the right place.
  • Summary: Whonix is built on top of Kicksecure, which itself is based on Debian. Debian is a GNU/Linux operating system. This layered design means Whonix inherits many features, tools, and documentation from both Kicksecure and Debian.
  • Click here: Visit the related page in the Kicksecure wiki for full documentation and background:

  • Note: Re-interpretation...
Apply the instructions inside Whonix, not inside Kicksecure.

Kicksecure: Perform these steps inside Kicksecure.

Instead, apply the steps inside Whonix-Workstation.

Kicksecure for Qubes: Perform these steps inside Qubes kicksecure-17 Template.

Instead, use the whonix-workstation-17 Template for these steps.

Auto-connect Risk[edit]

Beyond the challenge of generating an appropriate spoofed MAC address, there are technical hurdles related to preventing automatic network connections.

A spoofed MAC address is ineffective if the computer automatically connects to a public network after booting, thereby exposing the real MAC address:

  • Physical Isolation: Whonix-Gateway automatically connects to Tor upon startup.
  • USB Wi-Fi Device: Automatic connections may occur depending on the configuration.
  • VM Users: The host operating system is likely to automatically connect to the internet for updates, time synchronization, or other background services.

Other Location Tracking Risks[edit]

Tor Entry Guard Fingerprinting[edit]

Addressing MAC address concerns is only one part of a broader location tracking problem. Users must also consider how Tor entry guards are used across different locations to avoid guard fingerprinting. To mitigate this risk, follow one of the recommended configurations:

  1. Clone Whonix-Gateway (sys-whonix) with New Entry Guards.
  2. Regenerate the Tor State File after Saving the Current Tor State.
  3. Configure Tor to use Alternating Bridges.
  4. If relocating permanently, create Fresh Tor Entry Guards by Regenerating the Tor State File.

To fully mitigate this threat, entry guard changes must be applied to every Tor instance on both the host (e.g., apt-transport-tor) and guest systems.

Using Personal Computers in a Public Network[edit]

Info This applies to using a personal laptop, desktop, or any other internet-facing device in a public network.

In this scenario, the MAC address must be changed, and a new set of Tor entry guards should be configured. [1] Additionally, efforts should be made to obscure Tor usage from the network administrator. Depending on the user's setup, this may involve using an obfsproxy bridge or tunneling traffic through SSH or a VPN before connecting to the Tor network.

Depending on the threat model, changing the MAC address and using Tor may prevent revisiting the public network. If reuse is needed, the user must choose between keeping the same MAC address and Tor entry guards or generating new ones.

If the network administrator is suspected of logging MAC addresses, changing the MAC may arouse suspicion. Conversely, if the network is sufficiently public and individual observation is unlikely, it may be safe to use a new MAC address each time -- one that features a popular vendor ID and a random second part.

For further discussion on this complex topic, see Dev/MAC.

Changing MAC Addresses[edit]

Whonix[edit]

TODO: Please help test and improve these instructions.

1. Edit the network interfaces file.

  • Standard-Whonix-Version (VM) users: Edit /etc/network/interfaces on the host.
  • Physical Isolation users: Edit /etc/network/interfaces on Whonix-Gateway.

2. Install macchanger.

In a terminal, run:

su

apt update && apt install macchanger

3. Change the MAC address.

Info The following steps manually change the MAC address for a device. An example is provided for a wireless device (wlan0). Replace wlan0 with the appropriate device, such as an ethernet device (eth0).

su

ifconfig wlan0 down

macchanger -a wlan0

ifconfig wlan0 up

If the steps above do not work, the following method might work without macchanger. Replace wlan0 with the correct device name.

su

ifconfig wlan0 down

ifconfig wlan0 hw ether 00:AA:BB:CC:DD:EE

ifconfig wlan0 up

Alternatively, use iproute2 commands to change the MAC address.

ip link set down wlan0

ip link set wlan0 address 00:AA:BB:CC:DD:EE

ip link set up wlan0

4. Complete the MAC address change.

Below iface eth0 inet dhcp, add:

hwaddress ether 00:00....

5. Optional: Automatically randomize the MAC address on boot.

To enable this, add:

pre-up macchanger -e eth0

6. Modify network interface settings.

To prevent new network interfaces from being automatically activated, comment out the following line:

auto eth0

Then, configure manual activation with:

sudo ifup eth0

References[edit]

  1. This process involves removing the /var/lib/tor/state file.

License[edit]

Whonix MAC Address wiki page Copyright (C) Amnesia <amnesia at boum dot org>
Whonix MAC Address wiki page Copyright (C) 2012 - 2025 ENCRYPTED SUPPORT LLC <

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.

Notification image

We believe security software like Whonix needs to remain open source and independent. Would you help sustain and grow the project? Learn more about our 13 year success story and maybe DONATE!