git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "nick" <nick@nicholasjohnson.ch>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: <git@vger.kernel.org>
Subject: Re: Git Privacy
Date: Sun, 16 Jul 2023 23:07:06 +0000	[thread overview]
Message-ID: <CU3Z2NYP6BGG.1PQ6S5AF60XX6@anonymous> (raw)
In-Reply-To: <CU2GQHQV5GD3.CL67078EF4OO@anonymous>

nick wrote:
> The time zones reveal private information about developers and they
> don't even serve a use case, as far as I'm aware. A backwards-compatible
> way to solve this leak would be to convert timestamps to UTC by default
> and have a Git config option to revert back to the current behavior.

Come to think of it, even if timezones were converted to UTC by default,
time of day would still leak information about a user's likely timezone.

So based on that and keeping in mind Git's desire for strong
backwards-compatibility, I'm amending my proposal to just a standalone
Git option which would allow for forging timestamp and timezone
information, with timestamp information being forgeable to varying
degrees of granularity.

A new Git option is appropriate because Git doesn't already have
features which make this possible. So it would be necessary to implement
a new option anyways.

  parent reply	other threads:[~2023-07-16 23:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13 16:27 Git Privacy nick
2023-07-13 17:11 ` 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CU3Z2NYP6BGG.1PQ6S5AF60XX6@anonymous \
    --to=nick@nicholasjohnson.ch \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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.
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 NNTP newsgroup(s).