passphrase2pgp VS ledger

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.

I thought this was about https://github.com/ledger/ledger and was so confused why they'd be on NPM.

Pretty shitty of them to pick the name LedgerHQ after Ledger has already been used for years.

as far as the ledger-cli google groups [1] go, they seem to think it is a proper journal file. It has been fairly tested with OFX imports (https://github.com/ledger/ledger/wiki/OFX-Import) as well bank autosync (https://github.com/egh/ledger-autosync).

In fact, someone also wrote a book on this - https://leanpub.com/personal-accounting-in-ledger/

I will defer if you are indeed building your own competing tool in this space which is better, but holding to the original point of my request - maybe it will be incremental to support your format if ledger-cli format is supported today. versus not supporting any disk format (or inventing a new one).

[1] https://groups.google.com/g/ledger-cli/search?q=double%20ent...

The best I found is a file from 13 years ago here https://github.com/ledger/ledger/blob/master/doc/grammar.y

You're looking for /r/ledgerwallet. This subreddit is about accounting, e.g. ledger for the command line.