From: Thomas Harning <harningt@gmail.com>
To: Luke Lu <git@vicaya.com>
Cc: Alexander Gladysh <agladysh@gmail.com>, git@vger.kernel.org
Subject: Re: [Q] Encrypted GIT?
Date: Thu, 13 Mar 2008 15:15:32 -0400 [thread overview]
Message-ID: <20080313151532.20d72b14@gmail.com> (raw)
In-Reply-To: <51ED164C-2269-48B7-B8C9-0E819BFD63EC@vicaya.com>
On Thu, 13 Mar 2008 11:36:46 -0700
Luke Lu <git@vicaya.com> wrote:
> An obvious and easy solution: use an encrypted partition on the
> remote server and ssh as transport. Last time I checked, git on
> encrypted volumes is plenty fast.
If its an encrypted partition on the remote server... then its visible
@ that server.. which I don't think is desired in the situation.
An encrypted partition is fairly useless on a remote server unless the
remote server is expected to be physically removed/powered down...
otherwise anything can get into that data while its alive (pending
permissions, lack-of-holes, etc..)
The encfs solution makes sure that nothing is ever revealed
remote-side... all data is prevented from even going over ssh in its
unencrypted form.
next prev parent reply other threads:[~2008-03-13 19:17 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
2008-03-13 18:36 ` Luke Lu
2008-03-13 19:15 ` Thomas Harning [this message]
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=20080313151532.20d72b14@gmail.com \
--to=harningt@gmail.com \
--cc=agladysh@gmail.com \
--cc=git@vger.kernel.org \
--cc=git@vicaya.com \
/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).