Lines Matching refs:gpg
69 ``gpg`` command invoking GnuPG v.1. To check, run::
71 $ gpg --version | head -n1
73 If you see ``gpg (GnuPG) 1.4.x``, then you are using GnuPG v.1. Try the
79 If you see ``gpg (GnuPG) 2.x.x``, then you are good to go. This guide
86 If you have both ``gpg`` and ``gpg2`` commands, you should make sure you
90 $ alias gpg=gpg2
94 Configure gpg-agent options
98 you use the ``gpg`` command and run in the background with the purpose
111 edit your ``~/.gnupg/gpg-agent.conf`` file to set your own values::
119 It is no longer necessary to start gpg-agent manually at the
133 Check the full path to your ``gpg`` or ``gpg2`` command and use the
134 ``gpg2`` command if regular ``gpg`` for you is the legacy GnuPG v.1.
187 is what you will have. You can verify by running ``gpg --list-secret-keys``,
213 $ gpg --change-passphrase [fpr]
222 $ gpg --quick-addkey [fpr] ed25519 sign
227 $ gpg --send-key [fpr]
260 $ gpg --export-secret-key [fpr] | paperkey -o /tmp/key-backup.txt
310 $ gpg --homedir=/media/disk/foo/gnupg-backup --list-key [fpr]
345 $ gpg --with-keygrip --list-key [fpr]
377 $ gpg --list-secret-keys
384 You should also remove any ``secring.gpg`` files in the ``~/.gnupg``
391 secret keys are still stored in the legacy ``secring.gpg`` file used by
394 ``secring.gpg`` format to use ``private-keys-v1.d`` instead.
396 Once you get that done, make sure to delete the obsolete ``secring.gpg``
472 $ gpg --card-status
483 $ gpg --card-edit
485 gpg/card> admin
487 gpg/card> passwd
517 $ gpg --edit-key [fpr]
530 gpg>
534 commands are done from inside this menu mode, as indicated by ``gpg>``.
540 gpg> key 1
549 gpg> keytocard
562 gpg> key 1
563 gpg> key 2
564 gpg> keytocard
575 gpg> q
588 $ gpg --list-secret-keys
612 $ echo "Hello world" | gpg --clearsign > /tmp/test.asc
613 $ gpg --verify /tmp/test.asc
616 show "Good signature" after you run ``gpg --verify``.
635 $ gpg --list-secret-keys
651 $ gpg --quick-set-expire [fpr] 1y
656 $ gpg --quick-set-expire [fpr] 2020-07-01
660 $ gpg --send-key [fpr]
668 $ gpg --export | gpg --homedir ~/.gnupg --import
671 Using gpg-agent over ssh
674 You can forward your gpg-agent over ssh if you need to sign tags or
719 tell git to always use it instead of the legacy ``gpg`` from version 1::
721 $ git config --global gpg.program gpg2
755 # gpg: Signature made [...]
756 # gpg: Good signature from [...]
764 If you get "``gpg: Can't check signature: unknown pubkey
824 Make sure you configure ``gpg-agent`` before you turn this on.
845 Add the following to your ``~/.gnupg/gpg.conf``::
859 accounts. Once you have the above changes in your ``gpg.conf``, you can
863 $ gpg --locate-keys torvalds@kernel.org gregkh@kernel.org
895 ``trust-model`` setting in ``~/.gnupg/gpg.conf``::
919 gpg: Signature made Sun 07 Jan 2018 10:51:55 PM EST
920 gpg: using RSA key DA73759BF8619E484E5A3B47389A54219C0F2430
921 gpg: issuer "wens@...org"
922 gpg: Can't check signature: No public key
928 $ gpg --search DA73759BF8619E484E5A3B47389A54219C0F2430
929 gpg: data source: hkp://keys.gnupg.net
938 $ gpg --list-key torvalds@kernel.org
946 paste they key-id you found via ``gpg --search`` of the unknown key, and
955 $ gpg --recv-key C94035C21B4F2AEB