Creates a new key pair (public and private) and allows to send the public part to a certification authority (CA) for signing. The resulting certificate is then sent back to you, or stored in an LDAP server for you to download into your local keybox, where you can use it to sign and decrypt mails.
This mode of operation is called “decentralized key generation”, since all keys are created locally. Kleopatra (and GpgSM) do not support “centralized key generation” directly, but you can import the public/secret key bundle that you receive from the CA in PKCS#12 format via -> (Ctrl+I) .
Searches for, and imports, certificates from certificate servers into the local keybox. See the section called “Searching and Importing Certificates” for details.
You need to have key servers configured for this to work. See the section called “Configuring Directory Services” for more details.
Imports certificates and/or secret keys from files into the local keybox. See the section called “Searching and Importing Certificates” for details.
The format of the certificate file must be supported by GpgSM/GPG. Please refer to the GpgSM and GPG manuals for a list of supported formats.
Exports the selected certificates to a file.
The filename extension you choose for the export file name determines the format of the export file:
For OpenPGP certificates,
gpg
and
pgp
will result
in a binary file, whereas
asc
will result
in an ASCII-armored file.
For S/MIME certificates,
der
will result
in a binary, DER-encoded file, whereas
pem
will result
in an ASCII-armored file.
Unless multiple certificates are selected, Kleopatra
will propose
as the export file name.
fingerprint
.{asc,pem}
This function is only available when one or more certificates have been selected.
This function exports only the public keys, even if the secret key is available. Use -> to export both public and secret keys into a file, but note that this is almost always a bad idea.
Exports both the public and the secret key to a file.
In the dialog that opens, you can choose an