FYI: "Generic" fork

[pfalcon]

I've made a fork which works for me: https://github.com/pfalcon/git-remote-objcrypt . Changes include:

• Actually runs and not crashes right away with nowadays Node.js
• I'm not using Gitern
• I love rebases (and they now work)
• I use UTF-8 in filenames, etc. (and they now work)
• Some obvious inefficiencies fixed.

Thanks for your project!

(Note that I sent a private email regarding desirability of sharing such a fork, and as I didn't geta reply, I just follow the license.)

[huumn]

Sorry, been busy running another startup. Have at it, please! I did read your email just kept deprioritizing a replying.

I want to open source gitern too, which is mostly a bunch of weird SSH hacks and syscalls.

If you're looking to make something generic by all means go for it! (forgive me for the mediocre js ... I came from a systems background and this was my first real stab at modern js)

[pfalcon]

Hey @huumn, thanks for reply, and glad to hear that you're ok with it!

forgive me for the mediocre js ...

Oh, I'm not a JS programmer myself either, and it actually was an exercise in humility and practicality to hack on the existing code and resist the "rewrite it in Python" urge ;-). Some of hacks I had to apply are quite atrocious for sure. (And if I find myself still using it a couple of years from now, I'll probably go for a rewrite after all.)

Anyway, thanks again for implementing this project, it's really good improvement over git-remote-gcrypt's "Using an arbitrary or an sftp:// URI requires uploading the entire repository history with each push." (And the idea of reusing the SSH keys is a golden one, the need to maintain separate set of GPG keys like in most other projects always felt like a chore). I don't have intention to somehow advertise my fork any time soon, but hopefully someone interested to scale this space will find comments here useful to track the pathways in this area and maybe go further.