Lines Matching full:keys
55 a secure working environment and safeguard the PGP keys used to
145 - **[S]** keys can be used for signing
146 - **[E]** keys can be used for encryption
147 - **[A]** keys can be used for authentication
148 - **[C]** keys can be used for certifying other keys
154 keys). Since this is not the case, this guide will refer to it as "the
172 can be used to indicate relationship with other keys. Only the **[C]**
175 - add or revoke other keys (subkeys) with S/E/A capabilities
178 - sign other people's keys for web of trust purposes
180 By default, GnuPG creates the following when generating new keys:
186 is what you will have. You can verify by running ``gpg --list-secret-keys``,
201 GnuPG uses passphrases to encrypt your private keys before storing them on
203 its entirety, the attackers cannot use your private keys without first
206 It is absolutely essential that your private keys are protected by a
224 RSA keys. The main upside of ECC cryptography is that it is much
226 compared byte for byte with 2048+ bit RSA keys. Unless you plan on
232 support ED25519 ECC keys, you should choose "nistp256" instead or
278 It is important to have a readily available backup of your PGP keys
283 keys after conferences and summits.
307 people's keys.
352 $ cd ~/.gnupg/private-keys-v1.d
361 $ cd ~/.gnupg/private-keys-v1.d
364 Now, if you issue the ``--list-secret-keys`` command, it will show that
367 $ gpg --list-secret-keys
377 If you don't have the "private-keys-v1.d" directory
380 If you do not have a ``~/.gnupg/private-keys-v1.d`` directory, then your
381 secret keys are still stored in the legacy ``secring.gpg`` file used by
384 ``secring.gpg`` format to use ``private-keys-v1.d`` instead.
387 file, which still contains your private keys.
398 GnuPG operation is performed, the keys are loaded into system memory and
402 The best way to completely protect your keys is to move them to a
409 private keys and performing crypto operations directly on the card
412 device is not able to retrieve the private keys themselves. This is very
429 support ED25519 ECC keys, but offer fewest security features (such as
438 keys.
569 Saving the changes will delete the keys you moved to the card from your
573 Verifying that the keys were moved
576 If you perform ``--list-secret-keys`` now, you will see a subtle
579 $ gpg --list-secret-keys
587 available on the smartcard. If you go back into your secret keys
591 $ cd ~/.gnupg/private-keys-v1.d
626 $ gpg --list-secret-keys
637 keys eventually disappear from keyservers.
696 impersonate you without having access to your PGP keys.
705 you happen to have multiple secret keys, you can tell git which key
758 verification, so it properly processes signatures made by ECC keys.
888 developers' public keys, then you can jumpstart your keyring by relying
900 publishing public keys in DNS and securing them using DNSSEC signed
903 looking up public keys, GnuPG will validate DNSSEC or TLS certificates,
904 respectively, before adding auto-retrieved public keys to your local
909 auto-retrieve the keys for Linus Torvalds and Greg Kroah-Hartman (if you
912 $ gpg --locate-keys torvalds@kernel.org gregkh@kernel.org
951 Kernel.org maintains a git repository with developers' public keys as a
954 that repository as your source of public keys can be found here: