From: Thomas Harning <harningt@gmail.com>
To: "Alexander Gladysh" <agladysh@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [Q] Encrypted GIT?
Date: Thu, 13 Mar 2008 12:10:27 -0400 [thread overview]
Message-ID: <20080313121027.5f51f852@gmail.com> (raw)
In-Reply-To: <c6c947f60803130148w7981a3f0r718c0801343c7b78@mail.gmail.com>
On Thu, 13 Mar 2008 11:48:53 +0300
"Alexander Gladysh" <agladysh@gmail.com> wrote:
> Hi, list!
>
> I want to create a private GIT repo (without working copy) on a
> machine in external data-center. While I do not actually believe that
> it is possible that someone who has physical access to a machine would
> be interested in peeking into my repo, I'd like to play safe and to
> have this issue covered.
>
> Please advise what is the best way to do it. Are there any existing
> solutions?
>
Potential solution to store arbitrary data in a safe manner:
mkdir remote_git_raw remote_git
sshfs <data-center>:<path @ datacenter> $PWD/remote_git_raw
encfs $PWD/remote_git_raw $PWD/remote_git
This will lock your data in a remote encfs volume. (Uses FUSE)
Not quite sure about the implications on performance... but this will
certainly keep your data safe on that remote location.
next prev parent reply other threads:[~2008-03-13 16:11 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
2008-03-13 16:10 ` Thomas Harning [this message]
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=20080313121027.5f51f852@gmail.com \
--to=harningt@gmail.com \
--cc=agladysh@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 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).