mirror of
git://git.gnupg.org/gnupg.git
synced 2024-12-23 10:29:58 +01:00
"$1"
This commit is contained in:
parent
505527a4ae
commit
8c24595c41
9
doc/FAQ
9
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
|
||||
|
@ -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
|
||||
|
Loading…
x
Reference in New Issue
Block a user