summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorWerner Koch <wk@gnupg.org>1998-02-17 20:48:52 +0000
committerWerner Koch <wk@gnupg.org>1998-02-17 20:48:52 +0000
commiteac12d4a1cde651933d7dad42145a0f740376539 (patch)
tree57005bfe1f0e297e751832f0a9a42dcb2c62f654 /README
parent693d9d2a6cf4ec9c41a68200a0bdbbb395c88670 (diff)
downloadlibgcrypt-eac12d4a1cde651933d7dad42145a0f740376539.tar.gz
import works
Diffstat (limited to 'README')
-rw-r--r--README33
1 files changed, 32 insertions, 1 deletions
diff --git a/README b/README
index f5dc7a82..52e6e142 100644
--- a/README
+++ b/README
@@ -109,6 +109,15 @@
8) Continue with step 4 if we did not find a prime in step 7.
9) Find a generator for that prime.
+ You should make a revocation certificate in cases someone gets
+ knowledge of your secret key or you forgot your passphrase:
+
+ g10 --gen-revoke your_user_id
+
+ Run this command and store it away; output is always ASCII armored,
+ so that you can print it and (hopefully never) re-create it if
+ your electronic media fails.
+
You can sign a key with this command:
@@ -125,7 +134,9 @@
wether you want to sign this key.
You may remove a signature at any time using the option "--edit-sig",
- which asks for the sigs to remove.
+ which asks for the sigs to remove. Self-signatures are not removable.
+
+
Sign
@@ -172,6 +183,26 @@
Ditto, but sign the file with the user id "Suttner"
+ Keyring Management
+ ------------------
+ To export your complete keyring(s) do this:
+
+ g10 --export
+
+ To export only some user ids do this:
+
+ g10 --export userids
+
+ Use "-a" or "--armor" to create ASCII armored output.
+
+ Importing keys is done with the option, you guessed it, "--import":
+
+ g10 --import [filenames]
+
+ New keys are appended to the default keyring and already existing
+ keys are merged. Keys without a self-signature are ignored.
+
+
How to Specify a UserID
-----------------------
There are several ways to specify a userID, here are some examples: