Differences between version 54 and predecessor to the previous major change of GPG/PGPNotes.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 54 | Last edited on Monday, May 17, 2004 2:16:10 am | by StuartYeates | Revert |
| Older page: | version 49 | Last edited on Wednesday, March 10, 2004 6:26:39 am | by StuartYeates | Revert |
@@ -17,10 +17,10 @@
See [GPGMailClients] for integrating encryption into your favourite email client.
Below, we give examples of how to set up GPG ready for use on your system.
-!!!__Creating And Managing Keys__
-![
SeaHorse]
+!!! __Creating And Managing Keys__
+! SeaHorse
There is a graphical interface to key management called [Seahorse|http://seahorse.sourceforge.net/]. It makes it easy to see who has signed whose keys, and you can edit/create keys as well as sign and encrypt/decrypt messages. It is still in development, and does not use protected memory (ie it is not setuid), so don't type your passphrase into it if others have access to your machine (and you are paranoid). There is an official debian package (apt-get install seahorse).
!GNU Privacy Assistant
@@ -213,5 +213,21 @@
See Also WhySignEmail
----
-Part of CategorySecurity
+!!!"There is no indication that this key really belongs to the owner"
+
+This error is the result of a breakdown of trust. There can be several issues:
+It can occur on your own keys if the trust database is deleted. The solution is to use:
+
+ gpg --edit 0x012345678
+ ...
+ trust
+
+and tell [GPG] that you trust yourself. It can also occur if you are trying to send encrypted email to someone whose key you haven't signed, the solution is to sign their key or use --trusted-key for this operation.
+----
+!!!Recover a public key from the corresponding secret key
+
+ gpg --export-secret-key 0x12345678 | gpgsplit --no-split --secret-to-public | gpg --import
+
+----
+
Part of CategoryCryptography
