From KDE UserBase Wiki
Revision as of 11:15, 1 August 2019 by FuzzyBot (talk | contribs) (Updating to match new version of source page)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

GnuPG加密和解密你的郵件和選定的文件。完成這樣的操作需要很多的命令選項。有了KGpg憂慮就可以消除了-你不再需要記住任何命令。 KGpg幫你建立和管理你密鑰,導入和導出密鑰,查看密鑰簽名,信任等級和有效期。實際上差不多所有你需要做的事情 KGpg都覆蓋到了。同時也提供嚮導幫助你建立你的密鑰。



Extending the life of your keys

As you can see in the image above, you can extend the life of your keys using the Change Expiration button. Simply choose the new date from the popup calendar. To do this, however, you must have access to the private key and its pass-phrase. Without them you can do nothing.

Change your passphrase

Should you suspect your passphrase is compromised, you can change this also from the Key Properties dialogue. The Change Passphrase button is below Change Expiration.

Revoking a key

If you lose your private key or think it has been compromised in some way you need to revoke it. To reliably render a key unusable you need to revoke it. Revoking is done by adding a special revocation signature to the key.

The revocation signature can be created together with the key. In this case it is stored in a separate file. This file can later be imported into the keyring and is then attached to the key rendering it unusable.


Please note that to import this signature to the key no password is required. Therefore you should store this revokation signature in a safe place, usually one that is different from you key pair. It is a good advise to use a place that is detached from your computer, either copy it to an external storage device like an USB stick or print it out.

If you have not created such a detached revocation on key creation you can create such a revocation signature at any time choosing Your Key -> Revoke key, optionally importing it to your keyring immediately.


The option to revoke a key has only been available in the context menu until KDE SC 4.7.1. Since then it has been moved to the key menu.


If a contact has more than one key - perhaps some old keys in addition to the current one - and the wrong key is being used for encryption, find the old keys and reduced their Trust status to Not Trusted. They will remain available for decrypting old messages, but not used for new ones.




More Information