How to Write a New Git Protocol
rovaughn.github.io
How to Write a New Git Protocol
1–10 of 15 posts
Re: How to Write a New Git Protocol
#2Holy crap why?! Pre/post hooks to encrypt/decrypt seems like it'd be 100000x easier.
Re: How to Write a New Git Protocol
#3Nice job! I had no idea anything like this was even possible.
Re: How to Write a New Git Protocol
#4This would have been very nice to have a few months ago! At Aspera we wrote a protocol handler for Git[1] that let us send data over fasp (a reliable UDP protocol for fast bulk-data transfers). I learned a ton by reading Git's source code to figure out how to do it, but this blog post is much more pain-free.
Very good write up!
Re: How to Write a New Git Protocol
#5Thanks for sharing this. It's a good walkthrough and potentially quite useful for anyone wanting to implement a new protocol. It seems like the wrong tool for the job to me however.
This seems like it would be more easily implemented with smudge/clean filters[0]. In fact, this is exactly what git-crypt[1] does. The idea is that you run a filter on every file as it's checked out to do the decryption and every time a file is staged to do encryption. This requires nothing extra on the remote repository and you can you git commands as normal.
[0] http://git-scm.com/book/en/v2/Customizing-Git-Git-Attributes [1] https://github.com/AGWA/git-crypt
Re: How to Write a New Git Protocol
#6Thanks for sharing this. It's a good walkthrough and potentially quite useful for anyone wanting to implement a new protocol. It seems like the wrong tool for the job to me however. This seems like it would be more easily implemented with smudge/clean filters[0]. In fact, this is exactly what git-crypt[1] does. The idea is that you run a filter on every file as it's checked out to do the decryption and every time a f…
Depends on the behavior you want. With smudge/clean filters, the files in the repository history are encrypted. That means you don't get the benefit of delta encoding, and any tools you have that look directly at the repository (such as gitk or anything based on libgit2) cannot operate on the cleartext data.
On the other hand, git-remote-gcrypt (https://github.com/joeyh/git-remote-gcrypt/) encrypts when pushing and decrypts when pulling, which leaves the local repository unencrypted but keeps it encrypted on the untrusted remote server.
Re: How to Write a New Git Protocol
#7Thanks for sharing this. It's a good walkthrough and potentially quite useful for anyone wanting to implement a new protocol. It seems like the wrong tool for the job to me however. This seems like it would be more easily implemented with smudge/clean filters[0]. In fact, this is exactly what git-crypt[1] does. The idea is that you run a filter on every file as it's checked out to do the decryption and every time a f…
Depends on the behavior you want. With smudge/clean filters, the files in the repository history are encrypted. That means you don't get the benefit of delta encoding, and any tools you have that look directly at the repository (such as gitk or anything based on libgit2) cannot operate on the cleartext data. On the other hand, git-remote-gcrypt ( https://github.com/joeyh/git-remote-gcrypt/ ) encrypts when pushing and…
That's a fair point :) Although I do like the fact that the smudge/blur approach means that you can selectively encrypt files as well as still share the entire repository publicly via any protocol.
Re: How to Write a New Git Protocol
#8For people wanting to store their passwords, personal data and large files in a git-like fashion, I recommend Git-Annex: http://git-annex.branchable.com/
Re: How to Write a New Git Protocol
#9Earlier quoted context omitted.
Depends on the behavior you want. With smudge/clean filters, the files in the repository history are encrypted. That means you don't get the benefit of delta encoding, and any tools you have that look directly at the repository (such as gitk or anything based on libgit2) cannot operate on the cleartext data. On the other hand, git-remote-gcrypt ( https://github.com/joeyh/git-remote-gcrypt/ ) encrypts when pushing and…
That's a fair point :) Although I do like the fact that the smudge/blur approach means that you can selectively encrypt files as well as still share the entire repository publicly via any protocol.
True. And it also has the advantage of failing closed (if you accidentally push to the wrong place) rather than failing open.
Re: How to Write a New Git Protocol
#10git over ssh should be as safe as ssh, right?
Does it somehow go outside the ssh tunnel?