[git-remote-gcrypt] Simple language description of the encryption mechanism

Sean Whitton spwhitton at spwhitton.name
Tue Oct 6 20:56:54 BST 2020


Hello,

On Tue 06 Oct 2020 at 04:02pm +03, Callum Macdonald wrote:

> I understand there's an encrypted manifest file which contains
> encryption keys for parts of the rest of the repository. Then the
> packfiles are encrypted. However, what happens to these encrypted
> packfiles is a mystery to me. In the case of the rsync / sftp backend,
> it's clear, I guess they're uploaded. But what happens to them for a
> "regular" git transport?

What I'd suggest is creating a repo and pushing using gcrypt with a
regular git transport, then cloning the repo back without using
git-remote-gcrypt, and seeing what you get.

Basically, a commit is created containing all the data that would have
been rsynced.  It's not very sophisticated which is why the non-git
transports are strongly recommended.

-- 
Sean Whitton



More information about the sgo-software-discuss mailing list