hashpass VS git-remote-gcrypt

It's a good idea that I've considered. However, I didn't anticipate the need for this when I originally designed Hashpass in 2014, and adding it now would be a breaking change.

I am still considering it, but there would need to be a very slow, very careful rollout plan. Probably some transition period where users can opt into the new scheme, and then eventually make the new scheme the default but still support the old scheme, and finally remove the old scheme to make things simple again.

Since this is a Chrome extension which collects no information from users, I have no way of contacting users about this. So I would need to wait long enough that users discover it themselves in the UI. All told, I'd guess it would take about a year for the full migration.

Still, it's not unlike me to go to great lengths to remove minor annoyances like this.

Anyone is welcome to discuss things like this with me via GitHub issues: https://github.com/stepchowfun/hashpass

Are you aware of https://spwhitton.name/tech/code/git-remote-gcrypt/?

We use a modified https://github.com/spwhitton/git-remote-gcrypt on some of our git repos and employ the GPG Keychain app (from https://gpgtools.org) to help us manage the associated keys.

I used to rely heavily of Keybase reops, but since the takeover I'm no longer confident in their longevity. An alternative option is to encrypt files yourself and use a mainstream git provider. There are utils like gcrypt specifically for this use case. That way you can be confident in the encryption AND availability.

Yes, git-annex is perfect for this. It can do this with encryption via the rsync special remote. To store the git branches themselves, you can use git-remote-gcrypt. For backups, you can store the files on external hdds (additional to rsync.net) and keep them mostly offline/powered off. git-annex works really well with offline drives. Alternatively you can backup to another cloud provider that is supported as a special-remote.