Bug #11931

MAC Spoofing is broken in Stretch

Added by anonym 2016-11-16 14:42:18 . Updated 2016-11-17 12:34:13 .

Status:
Resolved
Priority:
High
Assignee:
intrigeri
Category:
Spoof MAC
Target version:
Tails_3.0
Start date:
2016-11-16
Due date:
% Done:

100%

Feature Branch:
bugfix/11931-network-manager-vs-mac-spoofing
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

The automated test suite noticed that the even though MAC spoofing is enabled and reportedly succeeds, the MAC address is not spoofed. I see this in the journal:

Nov 16 00:00:31 amnesia spoof-mac[2654]: Trying to spoof MAC address of NIC eth0...
[...]
Nov 16 00:00:31 amnesia spoof-mac[2719]: Successfully spoofed MAC address of NIC eth0

However:

$ macchanger eth0
Current MAC:   52:54:00:d7:d3:0f (unknown)
Permanent MAC: 52:54:00:d7:d3:0f (unknown)

Subtasks

Related issues

Related to Tails - Feature #11293: Check if/how we should use NetworkManager's new MAC address spoofing capabilities Confirmed 2016-03-31
Blocked by Tails - Bug #11937: Rebase our NetworkManager package on 1.4.2-2 Resolved 2016-11-16

History

#1 Updated by intrigeri 2016-11-16 15:59:50

  • Priority changed from Normal to High

#2 Updated by intrigeri 2016-11-16 16:49:24

I’ve verified that tails-spoof-mac does what it claims to do; but then NetworkManager resets the MAC address to the permanent one: device (eth0): set-hw-addr: set-cloned MAC address to 52:54:00:2D:92:10 (permanent).

#3 Updated by intrigeri 2016-11-16 16:51:00

  • related to Feature #11293: Check if/how we should use NetworkManager's new MAC address spoofing capabilities added

#4 Updated by intrigeri 2016-11-16 17:12:11

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 10
  • Feature Branch set to bugfix/11931-network-manager-vs-mac-spoofing

I’m fixing this in NM’s default settings, but it may be that some connections will get the default settings (reset to the permanent MAC address) anyway:

  • the “Wired connection” we ship by default (easy to fix ourselves, but won’t apply to users with persistent NM settings)
  • existing connections already stored in persistent NM settings

#5 Updated by intrigeri 2016-11-16 17:43:51

  • blocked by Bug #11937: Rebase our NetworkManager package on 1.4.2-2 added

#6 Updated by intrigeri 2016-11-16 18:04:00

intrigeri wrote:
> I’m fixing this in NM’s default settings,

It works.

> but it may be that some connections will get the default settings (reset to the permanent MAC address) anyway:
>
> * the “Wired connection” we ship by default (easy to fix ourselves, but won’t apply to users with persistent NM settings)

That works too: using the “Wired connection” gives me a spoofed MAC.

> * existing connections already stored in persistent NM settings

This remains to be tested.

#7 Updated by intrigeri 2016-11-17 07:50:28

  • % Done changed from 10 to 20

> > * existing connections already stored in persistent NM settings
> This remains to be tested.

Added an automated test for that in commit:82c40ea.

#8 Updated by intrigeri 2016-11-17 10:58:15

intrigeri wrote:
> > > * existing connections already stored in persistent NM settings
> > This remains to be tested.
>
> Added an automated test for that in commit:82c40ea.

Note that this is useful for persistent connections added from Tails 3.x, but persistent connections that were added with Tails 2.x must be tested by hand.

#9 Updated by intrigeri 2016-11-17 12:34:13

  • Status changed from In Progress to Resolved
  • % Done changed from 20 to 100

Applied in changeset commit:9f499b832b5813b9503e8033c357f85fb9b4572e.