git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Alexander Gladysh <agladysh@gmail.com>,
	git@vger.kernel.org
Subject: Re: [Q] Encrypted GIT?
Date: Thu, 13 Mar 2008 08:58:54 -0400	[thread overview]
Message-ID: <20080313125853.GA12927@mit.edu> (raw)
In-Reply-To: <20080313121644.GD2414@genesis.frugalware.org>

On Thu, Mar 13, 2008 at 01:16:44PM +0100, Miklos Vajna wrote:
> On Thu, Mar 13, 2008 at 12:55:11PM +0100, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > The latter can be remedied (somewhat) by encrypting each object 
> > individually.  In that case, .gitattributes can help (you should be able 
> > to find a mail to that extent, which I sent no more than 2 weeks ago).  
> > However, you must make sure that the encryption is repeatable, i.e. two 
> > different encryption runs _must_ result in _identical_ output.
> 
> afaik, this is not the case for gpg.

No, and you wouldn't want to use gpg because of the overhead it adds
around an encrypted message.  You would need to use a raw encryption
algorithm, or one with very minimal wrapping.  It's normally at this
point that that you'd need to bring in a security expert to ask a
whole lot of questions about your exact use scenario, do a formal
threat analysis, since there are all sorts of unanswered questions
about what kind of key management solution you really need for your
situation.

It's usually not as simple as "just encrypt it".  How many people need
to have access to the to the repository?  Do you need to revoke access
to the repository later?  Who is allowed to give a new person access
to the repository?  etc., etc., etc.

						- Ted

  reply	other threads:[~2008-03-13 13:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-13  8:48 [Q] Encrypted GIT? Alexander Gladysh
2008-03-13 11:47 ` Miklos Vajna
2008-03-13 11:55   ` Johannes Schindelin
2008-03-13 12:16     ` Miklos Vajna
2008-03-13 12:58       ` Theodore Tso [this message]
2008-03-13 13:27         ` Alexander Gladysh
2008-03-13 15:21         ` Johannes Schindelin
2008-03-13 16:00           ` Jeff King
2008-03-13 15:53         ` Jeff King
2008-03-13 16:01           ` Jeff King
2008-03-13 16:12           ` Theodore Tso
2008-03-13 16:19             ` Jeff King
2008-03-13 17:43     ` David Brown
2008-03-13 16:10 ` Thomas Harning
2008-03-13 18:36 ` Luke Lu
2008-03-13 19:15   ` Thomas Harning
2008-03-13 20:06     ` Luke Lu

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=20080313125853.GA12927@mit.edu \
    --to=tytso@mit.edu \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=agladysh@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=vmiklos@frugalware.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.
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).