All of lore.kernel.org
 help / color / mirror / Atom feed
From: bigbear <urs.rau@gmail.com>
To: git@vger.kernel.org
Subject: Re: Transparently encrypt repository contents with GPG
Date: Sat, 21 Apr 2012 10:25:10 -0700 (PDT)	[thread overview]
Message-ID: <1335029110871-7487506.post@n2.nabble.com> (raw)
In-Reply-To: <978bdee00903121419o61cd7a87rb55809796bd257d7@mail.gmail.com>


Matthias Nothhaft wrote
> 
> Hi,
> 
> I'm new to Git but I really already love it. ;-)
> 
> I would like to have repository that transparently encrypts and
> decrypts all files using GPG.
> 
> What I need is a way to automatically modify each file
> 
> a) before it is written in the repository
> b) after it is read from the repository
> 
> Is there a way to get this work somehow? Can someone give me some
> hints where I need to begin?
> 
> regards,
> Matthias
> 
> 

Have come across this on my own search for an encrypted git repo. Matthias
it looks as if somebody has come up with a "working" system that uses the
'smudge & clean' filter features of git. 
Seems to me that to use it for storing the repo on a non trusted or possibly
public git repo with some private content in the files this seems to be a
workable solution.

Transparent Git Encryption
https://gist.github.com/873637
and/or possibly 
https://github.com/shadowhand/git-encrypt

The way to do this is to use git's "smudge" and "clean" filters, but it's
not necessarily recommended for reasons that are explained here by Junio C
Hamano, the maintainer of git:

    http://article.gmane.org/gmane.comp.version-control.git/113221






--
View this message in context: http://git.661346.n2.nabble.com/Transparently-encrypt-repository-contents-with-GPG-tp2470145p7487506.html
Sent from the git mailing list archive at Nabble.com.

  parent reply	other threads:[~2012-04-21 17:25 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
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 [this message]
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=1335029110871-7487506.post@n2.nabble.com \
    --to=urs.rau@gmail.com \
    --cc=git@vger.kernel.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.