passphrase2pgp VS pass-otp

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.

otp tokens are included in the encrypted file. It’s just appended to the file, e.g. otpauth://totp/… You’ll need to install https://github.com/tadfisher/pass-otp on desktop for this to work. But the android client comes with support builtin.

I use pass myself. I had no idea you could use it for otp. Are you using something like this? https://github.com/tadfisher/pass-otp

I use https://github.com/tadfisher/pass-otp with pass, which has a FOSS client for desktop and smartphone (at least for andriod, no idea for ios)

There are the password manager pass (https://www.passwordstore.org/), which has an extension pass-otp (https://github.com/tadfisher/pass-otp). This extension can be used instead of Google Authenticator.

> In particular, I don't see how 2FA is possible with this

Umm, why not?

First, you can use a different app (like aegis) to generate OTPs.

Second, pass has an extension (https://github.com/tadfisher/pass-otp) that can be used to generate OTPs.

git clone https://github.com/tadfisher/pass-otpcd pass-otpsudo make install

You can use pass