Whonix running as Qubes DispVM uses saved clock


ID: 695
PHID: PHID-TASK-4mgoyiickjv37iyydpvg
Author: anon5577
Status at Migration Time: wontfix
Priority at Migration Time: High



When running as Qubes DispVM, whonix-ws sometimes (often) does not set the clock correctly, but instead seems to restore the date/time from when the DispVM savefile was created.

I have seen this often, over a very long period, but always assumed it had to do with my DispVM customisation. This time, I set up a clean Qubes R3.2, updated whonix-gw template and created a DispVM without customisation. The problem still occurs.

I usually don’t find out until I start getting OCSP errors due signatures being in the future. But this means that most likely a lot of earlier browsing has been correlateable since it all had the same wrong clock, therefore I set the priority of this ticket to high since it is a possible anonymity leak.

Recreating the DispVM savefile gets a more up-to-date clock in DispVMs launched afterwards.

Steps to reproduce:

  • Install Whonix templateVM on Qubes
  • Update the template (through qubes manager GUI action) and shut it down
  • qvm-create-default-dvm whonix-ws
  • Wait a couple of days
  • Launch DispVM, start getting OCSP time errors on browsing. Note that system time is wrong.



2017-06-29 16:56:06 UTC


2017-07-07 14:28:34 UTC


2017-07-07 18:13:56 UTC


2017-07-23 16:06:13 UTC


2017-10-31 17:05:19 UTC


2017-10-31 20:29:57 UTC