Bug #6294

NetworkManager in Wheezy resets MAC address to the inital one once disconnected

Added by sajolida 2013-09-26 03:19:42 . Updated 2014-03-11 18:26:19 .

Status:
Resolved
Priority:
Elevated
Assignee:
intrigeri
Category:
Target version:
Tails_1.1
Start date:
2014-03-10
Due date:
% Done:

100%

Feature Branch:
Type of work:
Upstream
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

See GNOME bug 708820

Even once this is fixed upstream (for Jessie), we might want to simply comment out the resetting code in NM (as long as Tails is based on Wheezy). After a quick look at the code, it seems to be a one line change in two places.

Subtasks

Feature #6890: Test MAC spoofing on Wheezy for hot-plugged network interfaces Resolved intrigeri

0

History

#1 Updated by intrigeri 2013-09-26 06:52:54

#2 Updated by sajolida 2013-10-09 09:59:28

  • Subject changed from NetworkManager in Wheezy resets MAC address to the permanent one once disconnected to NetworkManager in Wheezy resets MAC address to the inital one once disconnected
  • Priority changed from Elevated to Normal

Actually, we misunderstood the issue. The MAC address is not reset to the permanent one, but to the one it had when NetworkManager was started.

#3 Updated by intrigeri 2013-10-10 03:02:11

  • Priority changed from Normal to Elevated

#4 Updated by intrigeri 2013-12-08 14:52:55

  • Target version deleted (Tails_1.1)

#5 Updated by intrigeri 2013-12-08 15:01:12

  • Assignee set to intrigeri

#6 Updated by intrigeri 2013-12-08 16:20:31

  • Target version set to Tails_1.1

#7 Updated by intrigeri 2013-12-22 11:53:15

Unless I’m mistaken, once feature/spoof-mac is merged, this is a non-issue: we only start NetworkManager after spoofing the MAC address.

#8 Updated by intrigeri 2013-12-29 07:37:05

Confirmed, this issue will go away once Feature #5421 is solved.

#9 Updated by intrigeri 2014-03-09 23:22:32

  • Description updated

#10 Updated by anonym 2014-03-10 10:57:25

I feel quite confident that Feature #5421 fixes this issue.

It’s very clear that any device physically plugged before logging in in the Greeter will be unaffected since NM is started after all those devices has been spoofed. It’s a bit less clear about devices plugged after logging in but from what I remember from an earlier investigation, NM won’t handle any devices until all udev hooks (and hence MAC spoofing) have finished. Thus NM should only ever see the spoofed MAC address, and from my understanding of the upstream bug, that solves our issue.

#11 Updated by intrigeri 2014-03-11 17:17:37

Confirmed, that’s a non-issue both for {cold,hot}-plugged devices.

#12 Updated by intrigeri 2014-03-11 18:25:23

#13 Updated by intrigeri 2014-03-11 18:26:19

  • Status changed from Confirmed to Resolved

The testing branch (and hence, the feature/spoof-mac one) was merged into feature/wheezy, so that’s now a non-issue as long as one does not play with macchanger manually.