path: root/wiki/src/blueprint/macchanger.mdwn
diff options
authorTails developers <>2013-11-26 11:43:40 +0100
committerTails developers <>2013-11-26 18:03:44 +0100
commit0f74cb77dd1e993fe68bb32d583fb4ce8241bcb8 (patch)
treedc9fce557dfc1469902b54521cfed5dc3b5bd68d /wiki/src/blueprint/macchanger.mdwn
parent0dda1d3a7d88ddd98b4f52f96c39fbabfa37fe2f (diff)
Use tails_gitweb for code references.
Diffstat (limited to 'wiki/src/blueprint/macchanger.mdwn')
1 files changed, 7 insertions, 6 deletions
diff --git a/wiki/src/blueprint/macchanger.mdwn b/wiki/src/blueprint/macchanger.mdwn
index 5f25635..91f9630 100644
--- a/wiki/src/blueprint/macchanger.mdwn
+++ b/wiki/src/blueprint/macchanger.mdwn
@@ -291,8 +291,9 @@ network by simply removing that list, and then we have udev "re-probe"
for network devices and load their modules.
-* `config/chroot_local-hooks/80-block-network` (run at build time)
-* `config/chroot_local-includes/usr/local/sbin/tails-unblock-network`
+* [[!tails_gitweb config/chroot_local-hooks/80-block-network]] (run at
+ build time)
+* [[!tails_gitweb config/chroot_local-includes/usr/local/sbin/tails-unblock-network]]
(run right after Tails Greeter logs in)
## Trigger
@@ -309,7 +310,7 @@ devices until when we known whether the user needs MAC spoofing or
+[[!tails_gitweb config/chroot_local-includes/etc/udev/rules.d/00-mac-spoof.rules]]
### Discarded approaches
@@ -339,7 +340,7 @@ used in a very straightforward way, so if we want to switch tool in
the future it's a simple task.
Helper scripts:
+[[!tails_gitweb config/chroot_local-includes/usr/local/sbin/tails-spoof-mac]]
## Connection failure detection
@@ -363,7 +364,7 @@ when entering the wrong passphrase, so no false positives in that
(relatively common) case.
For details, see the script:
+[[!tails_gitweb config/chroot_local-includes/usr/local/sbin/tails-blocked-network-detector]]
## MAC spoofing and virtual machine networking issues
@@ -456,7 +457,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
-`config/chroot_local-includes/usr/local/sbin/tails-spoof-mac`, which
+[[!tails_gitweb config/chroot_local-includes/usr/local/sbin/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: