git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Enrico Weigelt <enrico.weigelt@vnc.biz>
Cc: git@vger.kernel.org
Subject: Re: Encrypted repositories
Date: Thu, 06 Sep 2012 12:49:30 -0700	[thread overview]
Message-ID: <7vmx132aph.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <e1f18eed-1096-4121-879a-4dd78627a4ba@zcs> (Enrico Weigelt's message of "Thu, 06 Sep 2012 15:56:29 +0200 (CEST)")

Enrico Weigelt <enrico.weigelt@vnc.biz> writes:

>> Enrico Weigelt <enrico.weigelt@vnc.biz> writes:
>> 
>> > * blobs are encrypted with their (original) content hash as
>> >   encryption keys
>> 
>> What does this even mean?
>> 
>> Is it expected that anybody who has access to the repository can
>> learn names of objects (e.g. by running "ls .git/objects/??/")? If
>> so, from whom are you protecting your repository?
>
> 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.

>> How does this encryption interact with delta compression employed
>> in pack generation?
>
> Probably not at all ;-o
>
> 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.

  reply	other threads:[~2012-09-06 19:49 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 [this message]
2012-09-08  3:34         ` Enrico Weigelt
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=7vmx132aph.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=enrico.weigelt@vnc.biz \
    --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).