{"thread":{"id":"32841","subject":"Announcement of git-remote-gcrypt (A custom encrypted remote format)","startedAt":"2013-02-06T18:19:39Z","lastAt":"2013-02-06T18:19:39Z","messageCount":1,"participants":["Ulrik Sverdrup"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"208836","messageId":"CAPQrgXuuGfrskLpdrVgCXD6RLurtBQxJHKdSzFeJd30gVpGXPg@mail.gmail.com","threadId":"32841","inReplyTo":null,"subject":"Announcement of git-remote-gcrypt (A custom encrypted remote format)","fromName":"Ulrik Sverdrup","fromEmail":"ulrik.sverdrup@gmail.com","sentAt":"2013-02-06T18:19:39Z","receivedAt":"2013-02-06T18:19:39Z","isPatch":false,"sender":{"key":"ulrik.sverdrup@gmail.com","avatar":null},"body":"Hi,\n\ngit-remote-gcrypt is a remote helper for git that (ab)uses this format\nto make it possible to push, pull and clone directly to and from a\ncustom encrypted repository format. Available from::\n\n     https://github.com/blake2-ppc/git-remote-gcrypt\n\nIt is relatively simple, and hopefully the protocol is sound and\nsecure; it uses GPG and allows multiple participants to possibly\ncollaborate using an untrusted and even public host. The git-on-git\nbackend is experimental and probably buggy, but it works.\n\nThe format intentionally targets mainly dumb hosts such as various\nbulk storage providers and therefore there is nothing smart about the\nprotocol; when fetching we can do no better than downloading every new\npackfile.\n\nI hope it interests someone, and maybe it even reaches the target of\nbeing both usable and secure. It also helps me if you point out\nif/how/why it is broken(!).\n\n-ulrik\n"}]}