Timesync is a monitor and user interface for sdwdate, bootclockrandomization and timesanitycheck. Notifications are dispatched in X and/or tty0 depending on availability. Checks bootclockrandomization's status; runs timesanitycheck before and after running sdwdate; checks sdwdate's status.
After boot, sdwdate runs in startup mode. When sdwdate is still in progress when X gets available, a progress bar will be shown. Timesync informs with an active popup in X if any error has been detected. Otherwise a passive popup in X will notify success.
If sdwdate is still in progress when tty0 gets available, if sdwdate failed or succeeded, notifications will be send to tty0.
These are important information for the user, because a correct clock is crucial for security, anonymity and privacy.
To prevent the user from getting irrelevant information, unless timesync gets manually run, later on, when sdwdate runs in daemon mode, no more progress bars or success notifications will shown. Only failures will be notified then.
In other words:
- sdwdate startup mode: show progress bar if necessary, show failure or success messages.
- sdwdate daemon mode: don't show progress bar or success messages, show failure messages
- sdwdate manual mode: show progress bar, show failure or success messages.
(This package description has been automatically extracted and mirrored from debian/control.)
See also man folder for more information.
Generic Readme Version 0.3
Generic Readme beings here. Have a look into the man sub folder (if available).
The functionality of this package was once exclusively available in the Whonix (github) anonymity distribution.
Because multiple projects and individuals stated interest in various of Whonix's functionality (examples: Qubes OS (discussion); piratelinux (discussion)), it's best to share as much source code as possible, it's best to share certain characteristics (such as /etc/hostname etc.) among all anonymity distributions) Whonix has been split into multiple separate packages.
Files in etc/... in root source folder will be installed to /etc/..., files in usr/... will be installed to /usr/... and so forth. This should make renaming, moving files around, packaging, etc. very simple. Packaging of most packages looks very similar.
Although probably due to generic packaging not very hard. Still, this requires developer skills. Ports welcome!
See comments below and instructions.
- Replace
apparmor-profile-torbrowserwith the actual name of this package (equals the root source folder name of this package after you git cloned it). - You only need config-package-dev, when it is listed in the
Build-Depends:field indebian/control. - Many packages do not have signed git tags yet. You may request them if desired.
- We might later use a documentation template.
Binary packages are available in Whonix's APT repository. By no means you are required to use the binary version of this package. This might be interesting for users of Debian and derivatives. Note, that usage of this package outside of Whonix is untested and there is no maintainer that supports this use case.
1. Get Whonix's Signing Key.
2. Add Whonix's Signing Key to apt-key.
gpg --export 916B8D99C38EAF5E8ADC7A2A8D66066A2EEACCDA | sudo apt-key add -
3. Add Whonix's APT repository.
echo "deb http://sourceforge.net/projects/whonixdevelopermetafiles/files/internal/ wheezy main" > /etc/apt/sources.list.d/whonix.list
4. Update your package lists.
sudo apt-get update
5. Install this package. Replace package-name with the actual name of this package.
sudo apt-get install package-name
Most welcome. Ports, distribution maintainers, developers, patches, forks, testers, comments, etc. all welcome.
- Professional Support: https://www.whonix.org/wiki/Support#Professional_Support
- Free Forum Support: https://www.whonix.org/forum
- Github Issues
- twitter: https://twitter.com/Whonix