So does Time Privacy aka “uwt” spoof the packet headers timestamps in transport or only the packets locally?
Timeprivacy can keep your time private. You can create wrappers for applications and timeprivacy will feed those applications with a fake time, which obfuscates at which time you really used that applications
Above statement taken from the git repo makes me think it only is for local things like metadata (inode data) or logging?
It’s not very spectacular. timeprivacy / time_privacy at best it’s a wrapper around faketime.
It does nothing that cannot be done manually using faketime. So I recommend to primarily look into faketime.
If you still need something else, come back to time privacy.
time_privacy was upstreamed to GitHub - wolfcw/libfaketime: libfaketime modifies the system time for a single application as timeprivacy.
For applications that should use a different date & time each time they are
run, consider using the included timeprivacy wrapper shellscript (contributed
by adrelanos at riseup dot net).
source code here:
libfaketime/src/timeprivacy at master · wolfcw/libfaketime · GitHub
uwt version:
uwt/usr/bin/time_privacy at master · Whonix/uwt · GitHub
Documentation and code isn’t great yet. No security issues. Just generally could use a revision.
thank you Patrick