Commit 3f0ac507 authored by intrigeri's avatar intrigeri
Browse files

Disable the hwclock.sh initscript at reboot/shutdown time.

Otherwise it would set the hardware clock to the system time, violating (a
strict interpretation of) our "don't leave traces on the hardware being used"
design goal.

Will-fix: #9364
parent cdb369af
......@@ -18,6 +18,7 @@ alsa-utils
gdomap
haveged
hdparm
hwclock.sh
i2p
kexec
kexec-load
......
--- a/etc/init.d/hwclock.sh 2015-05-16 10:47:58.445109125 +0000
+++ b/etc/init.d/hwclock.sh 2015-05-16 10:48:20.140450601 +0000
@@ -25,7 +25,7 @@
# Required-Stop: $local_fs
# Default-Start: S
# X-Start-Before: checkroot
-# Default-Stop: 0 6
+# Default-Stop:
### END INIT INFO
# These defaults are user-overridable in /etc/default/hwclock
......@@ -40,6 +40,8 @@ Tor may not function properly before it has finished (e.g. hidden
services running Tor prior to version 0.2.3.7-alpha requires clients
to have a time that is no more than 30 minutes incorrect).
The hardware clock is not affected.
# Guessing time based on Tor consensus
This idea originates from Liberte Linux' `tordate` script which uses
......@@ -186,3 +188,11 @@ efforts and compromise should be made to prevent these?
A Network Manager hook runs the whole thing:
[[!tails_gitweb config/chroot_local-includes/etc/NetworkManager/dispatcher.d/20-time.sh]].
The `hwclock.sh` initscript is disabled at reboot/shutdown time,
otherwise it would set the hardware clock to the system time,
violating (a strict interpretation of) our "don't leave traces on the
hardware being used" design goal:
* [[!tails_gitweb config/chroot_local-patches/do-not-modify-hardware-clock.diff]]
* [[!tails_gitweb config/chroot_local-hooks/52-update-rc.d]]
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment