I have working core tor and TBB running on Kicksecure and am trying to install kloak. I won’t ask about bio+silicon EMP efuse strokes, but I would like to get protection from keystroke and kloak looks like a solution. Do you know how to fix this?
. . .
sudo apt-get-update-plus install kloak
Hit:1 tor+http://deb.w5j6stm77zs6652pgsij4awcjeel3eco7kvipheu6mtr623eyyehj4yd.onion bullseye InRelease
Get:2 tor+http://5phjdr2nmprmhdhw4fdqfxvpvt363jyoeppewju2oqllec7ymnolieyd.onion/debian bullseye-fasttrack InRelease [12.9 kB]
Get:3 tor+http://5ajw6aqf3ep7sijnscdzw77t7xq4xjpsy335yb2wiwgouo7yfxtjlmid.onion/debian-security bullseye-security InRelease [48.4 kB]
Hit:4 tor+http://2s4yqjx5ul6okpp3f2gaunr2syex5jgbfpfvhxxbbjwnrsvbk5v3qbid.onion/debian bullseye InRelease
Get:5 tor+http://2s4yqjx5ul6okpp3f2gaunr2syex5jgbfpfvhxxbbjwnrsvbk5v3qbid.onion/debian bullseye-updates InRelease [44.1 kB]
Get:6 tor+http://2s4yqjx5ul6okpp3f2gaunr2syex5jgbfpfvhxxbbjwnrsvbk5v3qbid.onion/debian bullseye-backports InRelease [49.0 kB]
Reading package lists… Done
E: Release file for tor+http://5phjdr2nmprmhdhw4fdqfxvpvt363jyoeppewju2oqllec7ymnolieyd.onion/debian/dists/bullseye-fasttrack/InRelease is not valid yet (invalid for another 1h 58min 12s). Updates for this repository will not be applied.
E: Release file for tor+http://5ajw6aqf3ep7sijnscdzw77t7xq4xjpsy335yb2wiwgouo7yfxtjlmid.onion/debian-security/dists/bullseye-security/InRelease is not valid yet (invalid for another 1h 45min 49s). Updates for this repository will not be applied.
E: Release file for tor+http://2s4yqjx5ul6okpp3f2gaunr2syex5jgbfpfvhxxbbjwnrsvbk5v3qbid.onion/debian/dists/bullseye-updates/InRelease is not valid yet (invalid for another 37min 18s). Updates for this repository will not be applied.
E: Release file for tor+http://2s4yqjx5ul6okpp3f2gaunr2syex5jgbfpfvhxxbbjwnrsvbk5v3qbid.onion/debian/dists/bullseye-backports/InRelease is not valid yet (invalid for another 37min 17s). Updates for this repository will not be applied.
. . .
Unrelated to kloak.
Command sudo apt update is failing. This is most likely due to your existing clock issue.
Until that issue is resolved, you’ll run into follow-up issues based on that issue. It’s a blocker.
No chance the problem is somewhere at this level:
A Review of the Linux Kernel’s Release Signing and Key Management Policies – OSTIF.org
Dnf always works for me. What is it about updates over tor that triggers the “invalid for” x time? Updates of tor+https in virtual box work dependably (not in KVM still, though) but tor+http only whether in a VM or on bare metal are disrupted midway, partially. This pattern persists (in vm ubuntu, vm kicksecure, bare metal debian) even if I set the clock manually with the correct time. It looks like there is a lot involved in keysigning security, according to the audit information referenced above. Does Whonix manage with Nitro or Yubi key?
Then this issue isn’t caused by Whonix and as no solution could be provided here after days or weeks, seems unlikely will be resolved here. All I can do is recommend to try a different support.