MAC spoofing failure notification should point to the corresponding documentation
It was implemented initially, and then the move to Wheezy made the link invisible (#7249), and for Jessie #7989 lead us to remove it. It would be great to tell the user what to do when MAC spoofing fails.
As the blueprint linked above points out:
- a desktop notification may not be the best way to convey this message;
- a process started in the background in a udev hook may not be the best way to trigger that notification.
So this needs both UX and implementation research, quite possibly done together (this is a corner case, and we don't want to design something perfect that's so hard to implement that it'll never be done).
MAC spoofing failure notification: remove the link to the documentation.
It was broken on Tails/Wheezy already (the link to the doc is not
visible, and one of the two possible links was broken anyway), so this
is not a regression brought by porting to Jessie. And on Jessie, due to
bug #7989 these links would not work as-is anyway. It's unclear how this
would be best solved; #10559 has been created to sum up the problem and
track future improvements.
#3 Updated by Anonymous over 1 year ago
There is a blueprint supposed to be linked here, but it is not. It might have been https://tails.boum.org/blueprint/macchanger/ or https://tails.boum.org/blueprint/network_connection/