gpg - What is the armored option for in GnuPG? - Unix Linux Stack . . . PGP (including GPG) 'armoring' is not encryption Encryption prevents unauthorized use of data (formally, provides confidentiality) by making it unreadable in a way that can only be reversed by someone who has the secret key
How to export a GPG private key and public key to a file gpg --output public gpg --export SOMEKEYID \ gpg --output - --export-secret-key SOMEKEYID |\ cat public gpg - |\ gpg --armor --output keys asc --symmetric --cipher-algo AES256 The last approach is ideal if you want to create a physical back-up of your public and private keys to safeguard against a disk failure when no other way exists to
How to decrypt file that was symmetrically encrypted using GPG? $ gpg --decrypt test txt gpg: AES encrypted data gpg: encrypted with 1 passphrase $ gpg --symmetric --decrypt test txt gpg: conflicting commands $ gpg --passphrase --decrypt test txt gpg: no valid OpenPGP data found gpg: decrypt_message failed: Unknown system error
How to import secret gpg key (copied from one machine to another)? GnuPG maintains a trust database which it uses to decide how much to trust what keys For example, trust your own keys the most, keys that aren't directly or indirectly signed by any trusted keys the least
gpg - GnuPG command to show key info from file - Unix Linux Stack . . . For newer versions: gpg --show-keys my-local-key asc From the man page:--show-keys This commands takes OpenPGP keys as input and prints information about them in the same way the command --list-keys does for locally stored key
gpg --list-keys command outputs uid - Unix Linux Stack Exchange GNUPG has a trust database stored at ~ gnupg trustdb gpg You can backup this trust database using the --export-ownertrust option: gpg --export-ownertrust > file txt If you exported your secret keys and import them later into a new environment, the trust database is no longer present However, this is easily remedied: