Matthew Zipkin

> Error: PEM parse error (unexpected data). This is not a passphrase issue - is your key in PEM format?

From https://github.com/handshake-org/hs-airdrop#usage: ``` [key-file] can be: - An SSH private key file. - An exported PGP armor keyring (.asc). - An exported PGP raw keyring (.pgp/.gpg). ```

> This means your key was not found in the airdrop tree. Are you sure you are using the key that was connected to your github profile in February 2019?...

@boymanjor I think we should leave this open until there is a fix in the code. I think future users will encounter this issue and find the workaround.

The key you passed to hs-airdrop is not in the airdorp snapshot, I can not help you understand why. Either it's the wrong key or you didn't qualify on the...

Is it possible your key was not an acceptable type? There are some restrictions on the readme and more details here: https://github.com/handshake-org/hs-airdrop/issues/35#issuecomment-586699876

Hmm no that should be ok: https://github.com/handshake-org/hs-airdrop#accepted-key-algorithms

The only way to check is to run hs-airdrop. It can be done on an air gapped machine if you prefer but it must search the hs-tree-data for the nonce.

You can audit the code, rotate your 3-year-old keys out so they aren't important anymore, or simply do not claim the airdrop. There are lots of other ways to get...

Looks like the nodejs crypto module can't decrypt your SSH key with the passphrase provided. This might be hard to debug -- what version of nodejs are you running?