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 ->.
Imports certificates and/or secret keys from files into the local keybox.
The format of the certificate file must be supported by GpgSM. Please refer to the GpgSM manual for a list of supported formats.
Exports the selected certificates into a file.
This 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 (PKCS#12) file.
It should rarely be necessary to use this function, and if it is, it should be carefully planned. Planning the migration of a secret key involves choice of transport media and secure deletion of the key data on the old machine, as well as the transport medium, among other things.
Terminates Kleopatra.
Would you like to make a comment or contribute an update to this page?
Send feedback to the KDE Docs Team