I noted today that even when sdwdate-gui was telling me “the clock is fast” etc in logs, and the random time-sync stuff hadn’t completed, it was still possible to download updates via sys-whonix for TemplateVMs.
So, there must be some logic flaw, since all updates should have been blocked until sdwdate finished i.e. jumped a random number of seconds forward or backward first.
An update to the list of onions used by sdwdate. On boot, it can take ages before sdwdate is ready in sys-whonix, with a whonixcheck popup in some case (Qubes).
When saying that sdwdate-gui is not installed in Qubes, I meant not enabled.
To completely enable it, we have to modify /usr/lib/sdwdate-gui/notify-shutdown too.
#!/bin/bash
## Copyright (C) 2018 - 2019 ENCRYPTED SUPPORT LP <adrelanos@riseup.net>
## See the file COPYING for copying conditions
NAME="$(/usr/bin/qubesdb-read /name)"
if [ ! -z "$NAME" ]; then
/usr/bin/qrexec-client-vm sys-whonix whonix.NewStatus+$NAME" shutdown"
fi
In my version, the qrexec-client-vm command was commented, replaced with true, as in start-maybe.
I am working with a fresh installation, from scratch. The Whonix policies are in dom0.
It’s already in the code, commented. I believe there was an issue with the position of the Exit button in the menu. Will look into it.
Merged, tested, and available from testers repository. The separation is category “perfection”. Working really, really good already. Much, much better to have an exit button.