From: Thomas Rast <trast@student.ethz.ch>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Sverre Rabbelier <srabbelier@gmail.com>,
Matthias Nothhaft <matthias.nothhaft@googlemail.com>,
git@vger.kernel.org
Subject: Re: Transparently encrypt repository contents with GPG
Date: Fri, 13 Mar 2009 12:15:43 +0100 [thread overview]
Message-ID: <200903131215.49336.trast@student.ethz.ch> (raw)
In-Reply-To: <49BA39A1.9090203@drmicha.warpmail.net>
[-- Attachment #1: Type: text/plain, Size: 668 bytes --]
Michael J Gruber wrote:
> "git help attributes" may help: look for filter and set attributes and
> config (filter.$name.{clean,smudge}) accordingly. smudge should probably
> decrypt, clean should encrypt.
Wouldn't this trip over the randomness included in all encryption [to
avoid generating the same cyphertext for two separate identical
messages, which gives away some information], which would let git
think the file has been changed as soon as its stat info has changed
(or is just racy)?
Not to mention that this makes most source-oriented features such as
diff, blame, merge, etc., rather useless.
--
Thomas Rast
trast@{inf,student}.ethz.ch
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-03-13 11:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 21:19 Transparently encrypt repository contents with GPG Matthias Nothhaft
2009-03-12 21:34 ` Sverre Rabbelier
2009-03-13 10:46 ` Michael J Gruber
2009-03-13 10:51 ` Sverre Rabbelier
2009-03-13 11:15 ` Thomas Rast [this message]
2009-03-13 11:17 ` Sverre Rabbelier
2009-03-13 13:56 ` Michael J Gruber
2009-03-13 14:19 ` Sverre Rabbelier
2009-03-13 17:13 ` Jeff King
2009-03-13 20:23 ` Junio C Hamano
2009-03-14 11:16 ` Michael J Gruber
2009-03-14 18:45 ` Junio C Hamano
2009-03-16 16:01 ` Michael J Gruber
2009-03-17 7:40 ` Jeff King
2009-03-17 8:22 ` Jeff King
2012-04-21 17:25 ` bigbear
2012-06-17 7:33 ` lalebarde
[not found] ` <CAL1Gx-Ufs8TNVeeefAXBnX-eCnEk_DC1w6oJVRPcMcStdL_+-Q@mail.gmail.com>
2012-06-18 20:03 ` lalebarde
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=200903131215.49336.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=matthias.nothhaft@googlemail.com \
--cc=srabbelier@gmail.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).