From: "Jason Pyeron" <jpyeron@pdinc.us>
To: "'nick'" <nick@nicholasjohnson.ch>,
"'Junio C Hamano'" <gitster@pobox.com>
Cc: <git@vger.kernel.org>
Subject: RE: Git Privacy
Date: Sun, 16 Jul 2023 19:27:52 -0400 [thread overview]
Message-ID: <00b901d9b83d$249a2d20$6dce8760$@pdinc.us> (raw)
In-Reply-To: <CU3Z2NYP6BGG.1PQ6S5AF60XX6@anonymous>
> -----Original Message-----
> From: nick
> Sent: Sunday, July 16, 2023 7:07 PM
> Subject: Re: Git Privacy
>
> 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.
Discussed this with our policy wonks...
Short answer - no. There is no legal assumption that can be made - your work hours cannot be assumed to be 9-5. They also said that time zone is "too broad at 1/24th of the world", but understood the concern.
That being said the recommendation is to add --privacy
Where it assumes some defaults and those defaults can be controlled in your config or via --privacy=option1,option2
And then some of the options can be:
date-timezone=UTC
date-precision=8hour
etc...
v/r,
Jason Pyeron
--
Jason Pyeron | Architect
Contractor |
PD Inc | Certified SBA 8(a)
10 w 24th St | Certified SBA HUBZone
Baltimore, MD | CAGE Code: 1WVR6
.mil: jason.j.pyeron.ctr@mail.mil
.com: jpyeron@pdinc.us
tel : 202-741-9397
next prev parent reply other threads:[~2023-07-17 0:28 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
2023-07-16 23:27 ` Jason Pyeron [this message]
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='00b901d9b83d$249a2d20$6dce8760$@pdinc.us' \
--to=jpyeron@pdinc.us \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nick@nicholasjohnson.ch \
/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).