From: "nick" <nick@nicholasjohnson.ch>
To: <git@vger.kernel.org>
Subject: Git Privacy
Date: Thu, 13 Jul 2023 16:27:46 +0000 [thread overview]
Message-ID: <CTZ9RD9RQ5UO.3OIJX50PKMIR0@anonymous> (raw)
A couple years ago, I created git-privacy[1]. In it, I explain how
having exact commit times in a Git repo, over a long enough timespan,
can potentially be used to deduce private information about a
developer's life. Then I go on to explain the steps to prevent this
private information leakage.
I know this is low on the list of priorities when it comes to increasing
one's digital privacy, but I think it still matters. It's certainly
relevant to developers who need to remain anonymous while version
controlling their public software.
I was wondering if it would be appropriate to implement a feature which
would allow for automatic obfuscation of Git committer and author
timestamps without the need to assign environment variables or use Git
hooks. Perhaps a config option to automatically set the date to a time
before Git was invented?
Might there a better way to implement these ideas than what I'm
thinking? Please provide some feedback.
References:
1: https://git.nicholasjohnson.ch/git-privacy/
next reply other threads:[~2023-07-13 16:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 16:27 nick [this message]
2023-07-13 17:11 ` Git Privacy Junio C Hamano
2023-07-14 9:22 ` nick
2023-07-14 16:45 ` Junio C Hamano
2023-07-15 4:32 ` nick
2023-07-16 11:47 ` René Scharfe
2023-07-16 22:52 ` nick
2023-07-17 2:36 ` Junio C Hamano
2023-07-17 2:57 ` Junio C Hamano
2023-07-17 5:36 ` nick
2023-07-17 20:57 ` Theodore Ts'o
2023-07-17 22:49 ` nick
2023-07-17 16:37 ` Junio C Hamano
2023-07-16 23:07 ` nick
2023-07-16 23:27 ` Jason Pyeron
2023-07-17 4:20 ` nick
2023-07-18 21:59 ` brian m. carlson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CTZ9RD9RQ5UO.3OIJX50PKMIR0@anonymous \
--to=nick@nicholasjohnson.ch \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).