From: Jakub Narebski <jnareb@gmail.com>
To: "Matthias Andree" <matthias.andree@gmx.de>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>, git@vger.kernel.org
Subject: Re: encrypted repositories?
Date: Mon, 20 Jul 2009 06:48:03 -0700 (PDT) [thread overview]
Message-ID: <m3zlazbh4e.fsf@localhost.localdomain> (raw)
In-Reply-To: <op.uxc712eh1e62zd@balu.cs.uni-paderborn.de>
"Matthias Andree" <matthias.andree@gmx.de> writes:
> On a more general note, is someone looking into improving the http://
> efficiency? Perhaps there are synergies between my plan of (a)
> encryption and (b) more efficient "dumb" (http/rsync/...) protocol
> use.
There was idea about improving http:// efficiency, but it was via
crating git-over-HTTP aka. "smart" HTTP server, i.e. you would have to
have DAG exposed, like for git:// and ssh://
On the other hand for http:// server need only "dumb" web server, and
additional metadata generated by git-update-server-info. It is client
who does "walking" the DAG, so all data including server metadata can
be encrypted, and decrypted on-the-fly by client.
I don't know though what information leakage you would get from
existence of loose objects and packfiles, and their sizes. Probably
negligible...
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-07-20 13:48 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
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 [this message]
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=m3zlazbh4e.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=matthias.andree@gmx.de \
--cc=torvalds@linux-foundation.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).