Yes I did search first. I got results that seemed irrelvant (eg disable qubes update was the first suggestion). I also browsed some relevant-seeming parts of the wiki.
Apols if I missed something. If so please reply by posting a link.
For security testing I want to create a Win10 machine that has its clock stuck in the past. On a physical machine this is easy: remove the tiny battery that keeps the time and date updated while the machine is powered down, and isolate from the internet (“airgap” it). Such a machine boots up believing it is some constant date in the past and the clock progresses normally from that date unless manually updated.
I know how to do the airgap on a Qubes guest, but am stuck about emulating the stuck clock effect.
So I am asking how to set up a Win10 guest that has a clock that is permanently dated years back in time, whether that clock progresses at the normal rate or not. My thoughts are that this could be one of the following:
- A guest that starts at the same date and time on every boot, and the clock progresses normally within the session, but reverts to the original on reboot (as with the physical machine with a dead battery).
- A guest that after being manually backdated within windows the clock progresses in real time, and somehow saves the time on shutdown of the Qube, picking up the saved time on next reboot
- A guest that does not update the clock ever, so that after manual reboot it is stuck forever on the time that was set manually.
- A way to override the system wide clockVM for just this one guest.
- Any other workarounds?