Wait for the upgrade to arrive.
Root cause was found and is in the process of being fixed. See forum posts:
where will it be released that fixed update?
Very soon, an update to this topic will be provided when the commit has been merged.
okay, thanks
Would it be advisable to recommend that users who do anything private or sensitive in Whonix or Kicksecure to ensure the Tirdad modules load and work properly, for possible risk of time attacks leading to identity correlation? Most risky for hidden service providers.
Preferably to avoid any unwanted ends.
No user action is needed other than waiting for the fix to be published. Tirdad is a useful hardening measure, but its absence is very unlikely to allow system, data, or identity compromise on its own. Case in point, Qubes-Whonix does not support Tirdad at the moment, and it is simply not present there. There are no warnings like “don’t use Qubes-Whonix if your risk level is high”.
Fixed tirdad has been uploaded to the testers repository.
Tested, no errors, Tirdad enabled.
Fixed tirdad has been uploaded to all repositories.
Note for the updater/s: You need to fully shutdown/restart sdwdate/entire system after the upgrade.