Alternate public PGP key servers that support access via HKP (like SKS keyservers used to): keys.openpgp.org (based on hagrid) keyserver.ubuntu.com (based on Hockeypuck) keys.mailvelope.com (based on Mailvelope) Access via other protocols that are supported by GnuPG: LDAP: keyserver.pgp.com (based on Broadcom PGP Universal Server) Due to the fact that the SKS key servers were taken down due to ...
There is (a newer?) option in gpg (2.2.41) where you can extend all your subkeys at once with only the command: gpg --quick-set-expire <1> <2> <3> meaning: <1> fingerprint of your key (from gpg --list-secret-keys) <2> how long you would like to extend the expiration period <3> optionally, the subkey fingerprints to extend ('*' to extend all non-expired subkeys) e.g.: gpg --quick-set-expire ...
The usage field of that key only contains C (Certification). Without a subkey, this key can only be used to sign other keys, as it does not have the S (Sign), E (Encrypt) or A (Authenticate) usages allowed, and therefore the key is rejected when trying to use it as a signing key.
when I export a gpg private or public key, and specify armored as a switch, I get plain text key, however, the gnupgp website seems to state that these keys are actually encrypted. What's the point...
Then when using gpg, your ~/.gnupg directory should be backuped with as many precaution as the enciphered files. You also have the gpg --export > export and gpg --export-secret-keys > export commands to export all yours keys in a pair of files you should backup instead. But these precautions must be done before losing the disk.
Your private key, which, for historical reasons*, PGP and GPG call 'secret' and which is shown by --list-secret-keys, would be even longer; in addition, showing it on a terminal where in some cases a bad person might be able to get a copy of it is extremely bad for security. How do i get my key id?
Does anybody know the correct command to read a key file and show information about the key? Edit: Ideally the mechanism would be able to read the keyfile from stdin, such as cat keyfile.key | gpg --some-command I should have mentioned this earlier but so many commands for gpg work with stdin I didn't even consider it a relevant constraint.
I have generated keys using GPG, by executing the following command gpg --gen-key Now I need to export the key pair to a file; i.e., private and public keys to private.pgp and public.pgp, respecti...
I'm trying to copy my gpg key from one machine to another. I do: gpg --export ${ID} > public.key gpg --export-secret-key ${ID} > private.key Move files to new machine, and then: gpg --import public.key gpg: nyckel [ID]: public key [Name, e-mail] was imported gpg: Total number of treated keys: 1 gpg: imported: 1 (RSA: 1) gpg --allow-secret-key-import private.key sec [?]/[ID] [Creation date ...
