From: Enrico Weigelt <enrico.weigelt@vnc.biz>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Encrypted repositories
Date: Sat, 08 Sep 2012 05:34:48 +0200 (CEST) [thread overview]
Message-ID: <0666bd29-b156-4c3d-b859-ab140d2f849e@zcs> (raw)
In-Reply-To: <7vmx132aph.fsf@alter.siamese.dyndns.org>
> > Well, everybody can access the objects, but they're encrypted,
> > so you need the repo key (which, of course isn't contained in
> > the repo itself ;-p) to decrypt them.
>
> So, in short, blobs are not encrypted with the hash of their
> contents as encryption keys at all.
No, the blobs are encrypted with their content hash as key, and the
encrypted blob will be stored with it's content hash as object id.
> > For the usecases I have in mind (backups, filesharing, etc) this
> > wouldn't hurt so much, if the objects are compressed before
> > encryption.
>
> For that kind of usage pattern, you are better off looking at
> encrypted tarballs or zip archives.
No, that doesn't give us anything like history, incremental
synchronization, etc, etc.
What I finnaly wanna has is a usual git, just with encryption,
but I can live with loosing differential compression.
cu
--
Mit freundlichen Grüßen / Kind regards
Enrico Weigelt
VNC - Virtual Network Consult GmbH
Head Of Development
Pariser Platz 4a, D-10117 Berlin
Tel.: +49 (30) 3464615-20
Fax: +49 (30) 3464615-59
enrico.weigelt@vnc.biz; www.vnc.de
next prev parent reply other threads:[~2012-09-08 3:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fcbea7c0-b433-414b-abd3-b0e205a96fc5@zcs>
2012-09-06 2:23 ` Encrypted repositories Enrico Weigelt
2012-09-06 5:37 ` Junio C Hamano
2012-09-06 13:56 ` Enrico Weigelt
2012-09-06 19:49 ` Junio C Hamano
2012-09-08 3:34 ` Enrico Weigelt [this message]
2012-09-08 4:10 ` David Aguilar
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=0666bd29-b156-4c3d-b859-ab140d2f849e@zcs \
--to=enrico.weigelt@vnc.biz \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).