-
-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support *git-remote-gcrypt* helper #143
Comments
Yes, I just heard from you. About PR, you are welcome. |
This seems to be an issue that can be safely closed until the PR from @kenny-evitt is in. |
@ls42 Just marked this as an "enhancement". Hopefully one day, this issue could be closed by an awesome PR. :-) |
This would indeed be a great feature. In particular in light of recent meltdown / spectre vulnerabilities that raises questions regarding security of virtual servers for hosting sensitive git repositories. |
This would be a pretty important feature to have! In fact not having the option to use @kenny-evitt: Did you get anywhere with implementing this? |
Hi all, note that Pass for iOS is not using the git command line (which is not available in iOS obviously), but using the |
Thanks for your swift reply @mssun! I guess we are out of luck then. It seems that implementing pass-tomb, as suggested in #114, is even more difficult - if not impossible - since “pass-tomb is based on dm-crypt and therefore it is not compatible with Mac systems”. |
@awehrfritz I haven't even started on implementing this, sadly. |
In a similar spirit to pass-tomb, I use Pass with the git-remote-gcrypt Git helper to encrypt the file and directory names (and the entire Git history too) of my Pass repos.
git-remote-gcrypt is implemented entirely as 'shell' (sh) scripts but the encrypted repository format seems pretty straightforward.
This isn't critical for me, I'm pretty sure (almost) no one else is using this Git helper with Pass, and I'm also confident that this is a low priority for the contributors to this project, so I'm willing to submit a PR (someday).
The text was updated successfully, but these errors were encountered: