All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brown <git@davidb.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Miklos Vajna <vmiklos@frugalware.org>,
	Alexander Gladysh <agladysh@gmail.com>,
	git@vger.kernel.org
Subject: Re: [Q] Encrypted GIT?
Date: Thu, 13 Mar 2008 10:43:28 -0700	[thread overview]
Message-ID: <20080313174328.GA3783@old.davidb.org> (raw)
In-Reply-To: <alpine.LSU.1.00.0803131254580.1656@racer.site>

On Thu, Mar 13, 2008 at 12:55:11PM +0100, Johannes Schindelin 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.

Any decent file encryption program will never have this characteristic.
It's normally a bad idea from a security perspective.

David

  parent reply	other threads:[~2008-03-13 17:44 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
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 [this message]
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=20080313174328.GA3783@old.davidb.org \
    --to=git@davidb.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.