git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: encrypted repositories?

From
Jakub Narebski <jnareb@gmail.com>
Date
Jul 20, 2009, 13:48 UTC
Message-ID
<m3zlazbh4e.fsf@localhost.localdomain>
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
Previous: Matthias AndreeNext: Matthias Andree
Message 12 of 17 in “encrypted repositories?”
  1. Matthias AndreeJul 17, 2009
  2. Michael J GruberJul 17, 2009
  3. Jakub NarebskiJul 17, 2009
  4. Matthias KestenholzJul 17, 2009
  5. Linus TorvaldsJul 17, 2009
  6. John TapsellJul 17, 2009
  7. Linus TorvaldsJul 17, 2009
  8. Linus TorvaldsJul 17, 2009
  9. Thomas KochJul 18, 2009
  10. Matthias AndreeJul 20, 2009
  11. Matthias AndreeJul 20, 2009
  12. Jakub NarebskiJul 20, 2009
  13. Matthias AndreeJul 21, 2009
  14. Jeff KingJul 20, 2009
  15. Matthias AndreeJul 21, 2009
  16. Jeff KingJul 23, 2009
  17. J-S-BAug 2, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.