Post-installation Security Advice
- 1 On Whonix-Gateway ™ and Whonix-Workstation ™
- 2 Network Time Syncing
- 3 Better Security
- 4 Appendix
- 5 Footnotes
On Whonix-Gateway ™ and Whonix-Workstation ™
After Whonix ™ has finished installing, immediately change the passwords for both the user
user and user
Regularly check for security updates and apply them in a timely fashion; see Operating System Updates.
Network Time Syncing
Follow the platform-specific recommendations below to avoid Tor connectivity problems and to limit possible adverse anonymity impacts.
To protect against time zone leaks, the system clock inside Whonix ™ is set to UTC. This means it may be a few hours before or ahead of your host system clock. Do not change this setting!
If the host clock (in UTC!  ) is more than 1 hour in the past or more than 3 hours in the future, Tor cannot connect. In this case, manually fix the host clock by right-clicking on it, and also check for an empty battery. Then, power off and power on the Whonix-Gateway ™ (
sys-whonix) and Tor should be able to reconnect. If the host clock is grossly inaccurate, the user might experience problems when updating the host operating system, so periodically check it is (roughly) correct.
Non-Qubes-Whonix: It is strongly discouraged to use the pause / suspend / save / hibernate features.
Qubes-Whonix ™: It is strongly discouraged to use the pause feature of Qube Manager, but it is is safe to use the suspend or hibernate feature of dom0.
If you are interested in using the pause / suspend / save / hibernate features, please click the expand button for further instructions.
- It is strongly discouraged to pause / suspend / save / hibernate the Whonix-Gateway ™, because it is difficult to restore the clock after resume. 
- It is strongly discouraged to pause / suspend / save / hibernate the Whonix-Workstation ™. If this advice is ignored, restart sdwdate after resume.
- It is strongly discouraged to pause Whonix-Gateway ™ (
sys-whonix) using the pause feature of Qube Manager, because it is difficult to restore the clock after resume. 
- It is strongly discouraged to pause Whonix-Workstation ™ (
anon-whonix) using the pause feature of Qube Manager. If this advice is ignored, restart sdwdate after resume. 
- It is safe to use the suspend or hibernate feature of dom0 and a manual restart of sdwdate is unnecessary. 
Start Menu →
Time Synchronization Monitor (sdwdate-gui) →
Or in a terminal. 
sudo systemctl restart sdwdate
This chapter is aimed at newcomers and only provides a short and simple overview for basic protection. Anonymity and platform security can be improved by following recommendations outlined in the Security Guide and Advanced Security Guide sections, along with the Network Time Synchronization page.
How do I Check the Current Whonix ™ Version?
Open a terminal.
Open a terminal.
- By default, Qubes does not require a password for superuser access.
- Type the command in the terminal and press
To view the system time in UTC on Linux platforms, run.
- TODO: Show desktop clock in local time; keep system in UTC
- This is because the clock will be incorrect after system resume. A correct clock is important for anonymity (see Dev/TimeSync to learn more).
Qubes does not dispatch the
/etc/qubes/suspend-pre.dhooks upon pause / resume using Qube Manager.
- Editors note: Simplified in Whonix 15. Run /usr/lib/sdwdate/restart_fresh only. https://github.com/Whonix/sdwdate/blob/master/usr/lib/sdwdate/restart_fresh
No comments for now due to spam. Use Whonix forums instead.
This is a wiki. Want to improve this page? Help is welcome and volunteer contributions are happily considered! Read, understand and agree to Conditions for Contributions to Whonix ™, then Edit! Edits are held for moderation.
Copyright (C) 2012 - 2019 ENCRYPTED SUPPORT LP. Whonix ™ is a trademark. Whonix ™ is a licensee of the Open Invention Network. Unless otherwise noted, the content of this page is copyrighted and licensed under the same Freedom Software license as Whonix ™ itself. (Why?)