Just presented my 2 hr hackathon project at #btcpp privacy edition, Riga!
https://github.com/feuplebian/git-futz
With the recent attacks on developers of cypherpunk software bythe state and other malicious actors, developer privacy is becoming more important.
So I developed a command-line tool to fuzz location and time information from your unpublished git commit messages before you push your commits to a public branch.
Comments and suggestions welcome :)
This project ended up winning, I'm overwhelmed! 😬
This is cool. A few years ago l, all my commits had a start of day timestamps but pgp signing yubikey and qubes proxy got in the way so I stopped.
Thanks for bringing up signing. That's indeed another source of privacy leak. I'll have to think about how to approach this :)
I think what we need is unattended signing, or probably more likely, batch signing (sign once no matter how many commits) 🤔
nostr:nprofile1qqs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7hycrvd
This is really cool idea. A few years ago I experiemented with some shell aliases to mess with the commit dates. I gave up as a pgp signature comes with its own date so this needs to be manipulated too and I had an obsure signing setup.
nostr:npub1rhtejt4qaj76wjqvamf4wjxrv4tfzyeu33u2l9rl6fpfnku0fq0scs2alf gpg does take '--faked-system-time' so maybe there is someway align the pgp sig dates? I was using a yubikey through a qubeos proxy and gave up because of https://github.com/QubesOS/qubes-issues/issues/5034
here were my shell aliases:
```
shellAliases = {
git-today = ''
env GIT_AUTHOR_DATE="`date -I`T00:00:00" env GIT_COMMITTER_DATE="`date -I`T00:00:00" git'';
git-month = ''
env GIT_AUTHOR_DATE="`date +%Y-%m-01`T00:00:00" env GIT_COMMITTER_DATE="`date +%Y-%m-01`T00:00:00" git'';
git-last-month = ''
env GIT_AUTHOR_DATE="`date +%Y-%m-01 -d '-1month'`T00:00:00" env GIT_COMMITTER_DATE="`date +%Y-%m-01 -d '-1month'`T00:00:00" git'';
};
```
