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

[Callum Macdonald]

Thanks.

Created some bogus gpg keys and did as you suggested. I pushed the results to GitHub here[1], then added the decrypted and inspected contents of the files to make it clearer.

Would you be interested in adding more detailed explanations / write ups, etc to this repo? I'd be open to writing something if so.

Cheers - CM.

[1] https://github.com/GenerousLabs/gcrypt-example

--
For avoidance of doubt: This email does not constitute permission to add me to your mailing list.

On Tue, 6 Oct 2020, at 22:56, Sean Whitton wrote:
> 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
>