passphrase2pgp VS age

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.

and echoing the result after converting to an age private key

I like that https://github.com/FiloSottile/age has small public keys.

> something fresh

It exists, it's called age..

Some random links

https://github.com/FiloSottile/age

https://www.reddit.com/r/crypto/comments/hr64hr/state_of_age...

https://github.com/FiloSottile/age/discussions/432

> (Acquiring keys, rotating keys, identifying compromised keys, and most importantly either reaches a large enough percentage of emails..

Oh nevermind, age doesn't do any of that. Indeed, it doesn't even do email https://github.com/FiloSottile/age/issues/93

Encrypted secrets thanks to SOPS and Age

I never heard of "Age" before this post. Thank you to share. If others are interested to learn more, here are two other interesting posts about Age:

https://github.com/FiloSottile/age/discussions/432

https://words.filippo.io/dispatches/age-authentication/

of all things I was able to resolve the issue via this github issue: https://github.com/FiloSottile/age/issues/370#issuecomment-1...

Why keep something secret on a public repo? Is that not an oxymoron?

Also, I’m terms of encryption something like age[0] makes it much easier to not shoot yourself in the foot.

[0] https://github.com/FiloSottile/age

Why RSA specifically? For backups, I recommend Tarsnap. But if you really don't want to pay for encrypted cloud hosting, then check out age encryption.

I wouldn't use OpenSSL personally. If you just need simple but secure symmetric encryption, checkout the scrypt(1) encryption utility from Tarsnap. If you need support for public keys, check out age(1).