git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Kestenholz <mk@feinheit.ch>
To: Matthias Andree <matthias.andree@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: encrypted repositories?
Date: Fri, 17 Jul 2009 16:30:39 +0000	[thread overview]
Message-ID: <1f6632e50907170930w4860b841i3a6028ea47c4d522@mail.gmail.com> (raw)
In-Reply-To: <op.uw7wmbr41e62zd@balu.cs.uni-paderborn.de>

On Fri, Jul 17, 2009 at 3:14 PM, Matthias Andree<matthias.andree@gmx.de> wrote:
>
> How would one go about this from the user side? I sincerely doubt I have the
> resources (time!) to actually implement this in Git.
>

Maybe you could send around packages created by git-bundle as
pgp-encrypted emails, and keep the original on your computer on an
encrypted filesystem? You could also encrypt the bundles and put them
onto a public server if that suits you better than email.

The biggest advantage of this approach would be that it can be done
now, and no changes to git itself are required.


Matthias

  parent reply	other threads:[~2009-07-17 16:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-17 15:14 encrypted repositories? Matthias Andree
2009-07-17 16:06 ` Michael J Gruber
2009-07-17 20:22   ` Jakub Narebski
2009-07-17 16:30 ` Matthias Kestenholz [this message]
2009-07-17 19:38 ` Linus Torvalds
2009-07-17 20:22   ` John Tapsell
2009-07-17 20:40     ` Linus Torvalds
2009-07-17 20:42       ` Linus Torvalds
2009-07-18 19:09         ` encrypted repositories? with git-torrent? Thomas Koch
2009-07-20 12:13           ` Matthias Andree
2009-07-20 12:09   ` encrypted repositories? Matthias Andree
2009-07-20 13:48     ` Jakub Narebski
2009-07-21  8:30       ` Matthias Andree
2009-07-20 15:30     ` Jeff King
2009-07-21  8:25       ` Matthias Andree
2009-07-23 10:40         ` Jeff King
2012-08-02 14:52 ` J-S-B

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=1f6632e50907170930w4860b841i3a6028ea47c4d522@mail.gmail.com \
    --to=mk@feinheit.ch \
    --cc=git@vger.kernel.org \
    --cc=matthias.andree@gmx.de \
    /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).