sdwdate: Secure Distributed Web Date

Whonix ®

Download

Windows Linux Mac VirtualBox KVM Qubes USB ISO (coming soon) More options Source Code

About

Overview Features Whonix vs VPNs Why Open Source? Project Activities Contributors Mission & Vision

Docs

Documentation FAQ Troubleshooting

Community

Forums Contribute

Support

Self Support First Policy Search Engines, Docs and AI Support (Limited) Reporting Bugs Contact (Restricted)

Tools Upload file Special pages Recent changes Print Version Page meta What links here Related changes Page information

Page Read Edit History Move Protection Unwatch Watch Delete Purge

User Preferences Watchlist Contributions Logout Create account Login

Donate

• Network Time Synchronization
• Timezone
• sdwdate
• sdwdate-gui
• Boot Clock Randomization
• Time Attacks
• Dev/sdwdate
• Dev/TimeSync

sdwdate-gui Control Panel

sdwdate - Secure Distributed Web Date - in Whonix

sdwdate Documentation

Since Whonix is based on Kicksecure^™, the user can follow these instructions Sdwdate (links to the Kicksecure^™ website)

Whonix specific

Whonix sets configuration option RANDOMIZE_TIME=true through package anon-apps-config /etc/sdwdate.d/40_anon-apps-config.conf RANDOMIZE_TIME=true.

prerequisite knowledge: Timezone

Do sdwdate issues impact anonymity?

sdwdate failing doesn't mean deanonymized.

Even sdwdate does not work, there's still Boot Clock Randomization

To put it into perspective, Tor Browser Bundle on the host operating system (unrelated to Whonix) have neither sdwdate nor Boot Clock Randomization.

This is similar to asking "How secure is Whonix)?" See: Security Overview and Whonix Protection against Real World Attacks.

sdwdate-gui makes Tor issues in more visible due to its graphical indication and easily accessible logs. It would be an Unsubstantiated conclusion to deduct that sdwdate is the cause of Tor issues.

The time of sdwdate issues matters. If sdwdate fails

• A) during its first run after boot then that's worse than,
• B) sdwdate failing during any subsequent runs.

In case of A), the user would only be protected by Boot Clock Randomization .

In case of B), it is less of an issue because it is only for time keeping in long running VMs. For example, if sdwdate succeeded after boot but then would only succeed once per day in long running VMs that might still be good enough.

Planned sdwdate-gui enhancements include:

• Only showing sdwdate failure if sdwdate failed after boot and multiple times in long running VMs.
• Making Tor log output (anon-log) more accessible. This might help to redirect the often misplaced attention on sdwdate to Tor.

See Also

• sdwdate-gui
• Timezone
• Network Time Synchronization

Whonix The most watertight privacy operating system in the world.

Dark mode

Follow us on social media

Supported by Power Up Privacy

Whonix is proudly supported until 2025 by Power Up Privacy, a privacy advocacy group that seeks to supercharge privacy projects with resources so they can complete their mission of making our world a better place. (Strictly subject to our sponsorship policy.)

At Whonix we value freedom and trust, supporting Open Source and Freedom Software

By using this website, you acknowledge you have read, understood, and agree to be bound by these agreements: Terms of Service, Privacy Policy, Cookie Policy, E-Sign Consent, DMCA, Imprint 2012- 2024 ENCRYPTED SUPPORT LP

Your support makes
all the difference!

We believe security software like Whonix needs to remain open source and independent. Would you help sustain and grow the project? Learn more about our 12 year success story and maybe DONATE!