The same created during the time key generated, and actual recommendation is to use a longer set of characters but actually any number is accepted. NOTE that: -d is the same as -decrypt and -o the same as -outputĪnd the value of the passphrase is the actual value I used in my test to decrypt the above and not the variable. Then line to decrypt copied from terminal of my MAC and tested works, w/ no prompt: gpg -batch -passphrase MyPassphrase -o test.tt7 -d CE.txt.gpg Then to import use: gpg -import yourSecretKey.asc This will create a secret key in a file ONLY, unlike if you use keyname in the export call. So to explicitly export from where it was generated, the key to a file, you need to use that like this: gpg -export-secret-keys -armor E7E43C5C844E2917>yourSecretKey.asc Then two sub-keys on the left of the fist, you'll see similar to: sec rsa2048/E7E43C5C844E2917Īnd the part on a right after slash - will be your E7E43C5C844E2917 On the first line you'll see: 'Private key available' To get your keyID run: gpg -edit-key then To trust, use: gpg -key-edit then 'trust' then '5' then 'quit' gpg -list-secret-keys if it has a private key there and if not,.Simply means that you don't have a private or secret key in your gpg keyring.

Gpg for win