Information
ID: 550
PHID: PHID-TASK-4xmx47a7thhafvagjsrj
Author: HulaHoop
Status at Migration Time: open
Priority at Migration Time: Normal
Description
A potential solution should be a part of sdwdate (or a separate component if you think it has multiple use cases).
ntpd does clock jump detection:
Problems we need to workaround so it becomes possible:
-
On KVM Whonix at least, the hardware timer information is not updated in WS because kvm-clock and others are disabled.
-
Use of a guest agent to pass that kind of information from the host is not an option because its unsafe.
-
Fetching and comparing remote data with the perceived time in the WS poses scalability, performance and bootstrapping problems if the guest time is way off.
Solution concept:
-
The information about the current time is available to code in the GW where kvm-clock is available (via hwclock).
-
Create a systemd service that runs constantly and queries the hwclock on GW. If the drift between system time and hwclock exceeds a threshold it would trigger syncing locally on the GW and send a simple packet pattern to the Whonix internal network.
-
knockd server [0][1] constantly monitors the internal network would trigger the iptables lockdown if it sees the magic knock sequence. Note that no ports needs to be open on WS.
[0] http://www.zeroflux.org/projects/knock
[1] Debian -- Error
Comments
HulaHoop
2016-08-27 20:59:59 UTC
HulaHoop
2016-08-27 23:54:10 UTC
HulaHoop
2016-08-29 12:01:24 UTC
Patrick
2016-08-29 18:37:15 UTC
HulaHoop
2016-08-29 19:42:18 UTC
HulaHoop
2016-08-29 21:13:52 UTC
Patrick
2016-08-29 22:42:00 UTC
HulaHoop
2016-09-01 17:20:12 UTC
Patrick
2016-09-01 20:59:16 UTC
HulaHoop
2016-09-01 23:30:55 UTC
HulaHoop
2016-09-01 23:49:59 UTC
Patrick
2016-09-02 00:02:18 UTC
HulaHoop
2016-09-02 02:13:23 UTC
Patrick
2018-02-04 15:17:13 UTC
HulaHoop
2018-02-12 03:36:16 UTC
Patrick
2018-02-12 09:43:02 UTC
HulaHoop
2018-02-12 16:07:35 UTC
HulaHoop
2018-02-12 16:24:24 UTC
Patrick
2018-02-12 22:01:46 UTC
HulaHoop
2018-02-14 00:12:13 UTC
HulaHoop
2018-02-28 23:33:10 UTC
HulaHoop
2018-02-28 19:40:43 UTC
HulaHoop
2018-02-28 22:39:06 UTC
HulaHoop
2018-02-28 23:03:03 UTC
HulaHoop
2018-03-01 03:11:36 UTC
HulaHoop
2018-03-01 03:34:12 UTC
HulaHoop
2018-03-01 17:13:01 UTC