sdwdate-gui: Secure Distributed Web Date Graphical User Interface

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 systray with popup on mouse hover

sdwdate - Secure Distributed Web Date - systray - graphical user interface (GUI) - Homepage

Overview

sdwdate-gui is an optional graphical user interface (GUI) for sdwdate.

sdwdate-gui ensures the user knows whether network time synchronization has been completed, a critical factor for security, privacy, and anonymity. Ideally, after boot, users should wait with activities until sdwdate has completed. See also Do sdwdate issues impact anonymity?.

sdwdate can optionally be configured to block networking until sdwdate finishes, preventing potential leakage of the time before it is changed.

Upstream

• Introduction: Whonix Documentation Introduction, User Expectations, Footnotes and References, User Expectations - What Documentation Is and What It Is Not
• Whonix is based on Kicksecure^™: Whonix inherits many features and principles from Kicksecure.
• Kicksecure is based on Debian: Kicksecure builds upon the stability of Debian.
• Inheritance: Therefore, Whonix is also based on Debian.
• Debian is GNU/Linux-based: Debian primarily uses the GNU/Linux as its foundation.
• Shared documentation benefits: Because one distribution is based on another:
  • Inherited documentation: Little specific documentation is required for each layer.
  • Shared principles: Features and principles often remain consistent across forks. Users can often follow the same instructions for both Whonix and Kicksecure.
• Keep using Whonix: This does not mean the user should switch to Kicksecure.
• Where to apply the instructions: The instructions should be applied inside Whonix.
• Wiki editors notice: This box is wiki template upstream_wiki. (Pages that link to it.)
• Comparison: Whonix versus Kicksecure
• Documentation compatibility: Since Whonix is based on Kicksecure, the user can follow these instructions for Sdwdate-gui . Apply the instructions inside Whonix, not Kicksecure.
• Note: Re-interpretation...

Kicksecure: Perform these steps inside Kicksecure.

Instead the user should apply the instructions inside Whonix-Workstation.

Kicksecure for Qubes: Perform these steps inside Qubes kicksecure-17 Template.

Instead the user should apply the instructions inside whonix-workstation-17 Template.

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!