Feature #12500

Entire MAC address spoofed

Added by sajolida 2017-05-02 12:30:04 . Updated 2017-05-18 15:58:45 .

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Spoof MAC
Target version:
Tails_3.0~rc1
Start date:
2017-05-02
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

When starting 3.0~beta3 on a X200 with an internal Wi-Fi card from factory, I get the entire MAC address spoofed.

2.12~rc1 behaves as expected and only randomized the end of the MAC address.

Subtasks

History

#1 Updated by intrigeri 2017-05-16 08:57:36

  • Status changed from New to Confirmed

#2 Updated by intrigeri 2017-05-17 09:59:47

FWIW I can’t reproduce this with a (wired) network interface in libvirt/QEMU. I wonder how sajolida noticed this, and whether this has anything to do with NetworkManager randomizing the MAC address when scanning for Wi-Fi networks.

Not a blocker, but still: sajolida, with which command did you notice this, and at which point during the network configuration process? (before/after having connected to a Wi-Fi AP?)

#3 Updated by intrigeri 2017-05-17 10:13:29

  • Status changed from Confirmed to Rejected
  • Assignee deleted (anonym)

Reproduced with a Broadcom BCM43225 Wi-Fi interface in some Acer laptop, before connecting to any Wi-Fi AP. The Journal says that the current (fully randomized) MAC address was set by NetworkManager for scanning, as expected. Once I’ve connected to a Wi-Fi AP, only the non-vendor bytes of the MAC address are randomized, as expected too. So I bet that sajolida checked while scanning and was thus confused. sajolida, please reopen if you can reproduce this outside of the Wi-Fi scanning phase.

#4 Updated by sajolida 2017-05-18 15:58:45

I’m sure I used macchanger -s to see the MAC. I’m not sure whether I was scanning or already connected but most likely I was scanning because I was doing lost of tests in a row for Bug #12362.