macchanger.md

-[[!tag archived]]
 
-[[!toc levels=2]]
+
+
+[[_TOC_]]
+
 
 # Future work
 
@@ -20,8 +22,8 @@ emitted.
 
 Some bugs of interest that may bring some hope:
 
-* [[!gnomebug 387832]] resolved
-* [[!debbug 518368]] fixed upstream
+* [GNOME bug #387832](https://bugzilla.gnome.org/show_bug.cgi?id=387832) resolved
+* [Debian bug #518368](https://bugs.debian.org/518368) fixed upstream
 * <https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/336736> wontfix
 
 ## Vendor bit randomisation with macchiato
@@ -85,7 +87,7 @@ dispatcher hooks but just like in the section about "Connection
 failure detection", there's none yet.
 
 An alternative would be to do this in
-[[!tails_gitweb config/chroot_local-includes/usr/local/lib/tails-spoof-mac]], which
+[config/chroot local-includes/usr/local/lib/tails-spoof-mac](https://gitlab.tails.boum.org/tails/tails/-/blob/master/config/chroot_local-includes/usr/local/lib/tails-spoof-mac), which
 is run by the udev hook. In the end of the script we could try to
 verify that the spoofing indeed happened for the NIC in question, and
 if it didn't we could go into full-out panic mode:
@@ -154,3 +156,4 @@ rather than macchanger.
 Investigate and possibly document the kind of information that could
 still be seen on the LAN about the system. Such as the manufacturer (ex:
 Sony), model number, BIOS and version, etc.?
+