passphrase2pgp VS pass-tomb

As far as I'm aware, Mnemonikey is the first of its kind, rhyming only with the related but conceptually different passphrase2pgp tool, from which I drew my original inspiration.

I think people should seriously consider using something like passphrase2pgp [0] in addition to a hardware key like this. That way you can have a brain key (hopefully generated with diceware or equivalent) to tie together day-to-day keys like this to a more permanent identity. I'm honestly surprised that strategy is not more widespread.

[0] https://github.com/skeeto/passphrase2pgp

Check out Chris Wellons' tool passphrase2pgp - it does exactly what you're describing by hashing an arbitrary input passphrase with Argon2.

So the easiest way to synchronize gpg keys I found is https://github.com/skeeto/passphrase2pgp - it generates a deterministic gpg key (also ssh keys, x509 certificates...) from a passphrase. Excellent tool

One way to circumvent this is to use a strong passphrase to deterministically generate the PGP/SSH key [1] to unlock other passwords. The SSH key could grant access to a remote server with backups and the PGP key could decrypt passwords using pass [2].

1. https://github.com/skeeto/passphrase2pgp

2. https://www.passwordstore.org/

I know there are tools that can generate GPG from arbitrary inputs, but what I'm really looking for is something with direct compatibility with BIP 39 or (BIP 44) phrases in particular.

What if https://github.com/skeeto/passphrase2pgp is not obviously the software to use, or doesn't exist at some later point?

My own tool, passphrase2pgp works this way. It generates both OpenPGP and SSH Ed25519 keys from a user-chosen passphrase, and it's designed to send the key straight into the ssh-agent on demand.

Derive my keypair entirely from a passphrase, with generous key stretching. I never need to worry about backing up my keys. I later extended this idea to OpenPGP and SSH, where I also exclusively use passphrase-derived keys: passphrase2pgp.

passphrase2pgp: for storing my PGP and SSH keys in my brain. Neither ever reside in permanent storage.

By itself, Passwordstore will not encrypt file names or directory names, which might not be a problem if no one else has access to the machine that hosts your git repo, but if that's not the case (even if it's a private repo on whatever platform), you might want to use either Tomb or git-crypt-remote to have full end-to-end encryption. There are even some tools that glue tomb and pass together (https://github.com/roddhjav/pass-tomb for one), though I'm not sure what's the situation is like when it comes to mobile integration with tomb/git-crypt-remote.

That can of course be fixed by using pass-tomb, but that isn’t implemented in mobile clients (at least not on iOS).

- https://pujol.io/blog/tomb-with-gpg-keys/ - https://github.com/roddhjav/pass-tomb

A plug-in called pass-tomb exists to fix this, but doesn’t work with mobile apps (a least not iOS)