From: Linus Torvalds <torvalds@linux-foundation.org>
To: John Tapsell <johnflux@gmail.com>
Cc: Matthias Andree <matthias.andree@gmx.de>, git@vger.kernel.org
Subject: Re: encrypted repositories?
Date: Fri, 17 Jul 2009 13:42:36 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0907171341040.13838@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.01.0907171337320.13838@localhost.localdomain>
On Fri, 17 Jul 2009, Linus Torvalds wrote:
>
> On Fri, 17 Jul 2009, John Tapsell wrote:
> >
> > Why couldn't you have the actual code encrypted, but have the server
> > still know about the SHAs etc? You would expose the actual commit
> > structure, but that might be acceptable?
>
> Even that wouldn't really work, because you'd never be able to generate
> any deltas.
>
> So there would be no real advantage. In fact, there would be only
> disadvantages, because without any delta generation, you'd now have to
> actually transfer _more_ data.
Oh, if you let the server know all the SHA's at _all_ levels (ie down to
the blob itself), and then just make the blobs be encrypted, we'd be able
to do some trivial optimizations, like only sending the actual blobs that
changed. HOWEVER. That would reveal absolutely tons of data about the
repository, and about the history. You'd have lost a _lot_ of security.
Linus
next prev parent reply other threads:[~2009-07-17 20:43 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
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 [this message]
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=alpine.LFD.2.01.0907171341040.13838@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=johnflux@gmail.com \
--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).