aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorNils Ellmenreich <[email protected]>2001-06-15 13:27:15 +0000
committerNils Ellmenreich <[email protected]>2001-06-15 13:27:15 +0000
commit8c24595c419e6725ef45b792d69403511da05a09 (patch)
tree3288252b57b846b3759f462d41b90ab3043a5416
parentUTF-8 uid, OS X sed problems (diff)
downloadgnupg-8c24595c419e6725ef45b792d69403511da05a09.tar.gz
gnupg-8c24595c419e6725ef45b792d69403511da05a09.zip
"$1"
-rw-r--r--doc/FAQ9
-rw-r--r--doc/faq.raw9
2 files changed, 8 insertions, 10 deletions
diff --git a/doc/FAQ b/doc/FAQ
index d2fb22b47..c47984d7a 100644
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -2,8 +2,8 @@
GNUPG FREQUENTLY ASKED QUESTIONS
-Version: 1.5
-Last-Modified: Jun 13, 2001
+Version: 1.5.1
+Last-Modified: Jun 15, 2001
Maintained-by: Nils Ellmenreich <nils 'at' gnupg.org>
@@ -209,6 +209,7 @@ you could search in the mailing list archive.
the following line to your ~/.gnupg/options:
load-extension idea
+
4. USAGE
4.1) What is the recommended key size?
@@ -218,7 +219,7 @@ you could search in the mailing list archive.
is probably the weakest link if the key size is larger
than 1024 bits. Encryption keys may have greater sizes,
but you should then check the fingerprint of this key:
- "gpg --fingerprint --fingerprint <user ID>".
+ "gpg --fingerprint <user ID>".
As for the key algorithms, you should stick with the default (i.e.,
DSA signature and ElGamal encryption). A ElGamal signing key has the
@@ -229,8 +230,6 @@ you could search in the mailing list archive.
versions. It has only been introduced because at the time it was
not clear whether there is was patent on DSA.
-
-
4.2) Why does it sometimes take so long to create keys?
The problem here is that we need a lot of random bytes and for that
diff --git a/doc/faq.raw b/doc/faq.raw
index d4c96c0d1..d03e5a768 100644
--- a/doc/faq.raw
+++ b/doc/faq.raw
@@ -13,8 +13,8 @@ The most recent version of the FAQ is available from
[H H1]GNUPG FREQUENTLY ASKED QUESTIONS[H /H1]
-Version: 1.5[H p]
-Last-Modified: Jun 13, 2001[H p]
+Version: 1.5.1[H p]
+Last-Modified: Jun 15, 2001[H p]
Maintained-by: [$maintainer]
@@ -147,6 +147,7 @@ you could search in the mailing list archive.
load-extension idea
[H /pre]
+
<S> USAGE
<Q> What is the recommended key size?
@@ -156,7 +157,7 @@ you could search in the mailing list archive.
is probably the weakest link if the key size is larger
than 1024 bits. Encryption keys may have greater sizes,
but you should then check the fingerprint of this key:
- "gpg --fingerprint --fingerprint <user ID>".
+ "gpg --fingerprint <user ID>".
As for the key algorithms, you should stick with the default (i.e.,
DSA signature and ElGamal encryption). A ElGamal signing key has the
@@ -167,8 +168,6 @@ you could search in the mailing list archive.
versions. It has only been introduced because at the time it was
not clear whether there is was patent on DSA.
-
-
<Q> Why does it sometimes take so long to create keys?
The problem here is that we need a lot of random bytes and for that