-
sdwdate-1.0.0-6 Stable
released this
2026-07-11 20:33:18 +02:00 | 1 commits to main since this releasesdwdate (LainOS Layer 02 port) ~ Changelog
1.0.0-6 ~ Tor consensus check fix (fresh installs)
Bug Fix
- Fixed
Tor Consensus Time Sanity Check: error: Could not request from Tor control connection. error: <class 'AttributeError'>on fresh installs, causing every time source to reportremote_status: Falseand fail. Root cause: thesdwdatesystem user was never added to thetorgroup, so it couldn't read Tor's control-port authentication cookie (/var/lib/tor/control_auth_cookie, mode0640, ownedtor:tor) needed for the consensus check. This fix had previously only been applied manually, live, on one already-installed system, and was never actually added to the package itself. - Fix: added
usermod -aG tor sdwdateto both the package'spost_install/post_upgradehooks and the OpenRC init script'sstart_pre()~ the latter for the same Calamares-chroot reliability reason established for the log file fix in 1.0.0-3 (install-time hooks have been found not to reliably survive Calamares' chroot-based install process; init-script-time fixes run fresh on every start regardless of install method). - Verified end-to-end on a fresh KVM ISO install: confirmed
sdwdatewas missing from thetorgroup before the fix, rebuilt and reinstalled the package, forced a full service restart, confirmed group membership took effect (id sdwdateshowingtorin the group list), and observed a complete sync cycle withTor Consensus Time Sanity Check: saneon all three contacted onion sources.
Note: this bug and the 1.0.0-5 hardware clock fix were both found through genuine fresh-install testing in a KVM guest, not by continuing to test on an already-patched development machine ~ neither would have surfaced from further testing on a system that had already accumulated manual live fixes.
Downloads
- Fixed