From: Aaron Digulla <digulla@hepe.com>
To: Francis Galiegue <fge@one2team.com>
Cc: git@vger.kernel.org
Subject: Re: [FR] Encrypting the repository
Date: Fri, 10 Apr 2009 13:09:24 +0200 [thread overview]
Message-ID: <49DF28E4.3070609@hepe.com> (raw)
In-Reply-To: <200904101114.07385.fge@one2team.com>
Francis Galiegue wrote:
> Le vendredi 10 avril 2009, vous avez écrit :
>> Hello,
>>
>> I need a way to safely synchronize data between several places using an
> unsafe
>> storage (USB stick, Internet drive). So my question is: How much work would
> it
>> be to patch GIT to encrypt all files in the repository using AES-256?
>>
>> I'm aware that this leaves an issue unresolved (where should I store the
>> password so that GIT doesn't have to ask for it all the time?) but one step
> at a
>> time, please :)
>>
>> Regards,
>>
>
> Why don't you just create an archive and encrypt that archive, instead of
> encrypting every file?
Because I don't want to loose the change history.
> Also, what are the target systems?
Linux and Windows.
Regards,
--
Aaron "Optimizer" Digulla a.k.a. Philmann Dark
"It's not the universe that's limited, it's our imagination.
Follow me and I'll show you something beyond the limits."
http://www.pdark.de/ http://blog.pdark.de/
next prev parent reply other threads:[~2009-04-10 11:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 8:49 [FR] Encrypting the repository Aaron Digulla
2009-04-10 9:14 ` Francis Galiegue
2009-04-10 11:09 ` Aaron Digulla [this message]
2009-04-10 10:18 ` Geoffrey Lee
2009-04-10 10:30 ` Sverre Rabbelier
2009-04-10 11:11 ` Aaron Digulla
2009-04-10 11:17 ` Sverre Rabbelier
2009-04-11 2:03 ` Nicolas Pitre
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=49DF28E4.3070609@hepe.com \
--to=digulla@hepe.com \
--cc=fge@one2team.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 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).