diff options
Diffstat (limited to 'doc/faq.raw')
| -rw-r--r-- | doc/faq.raw | 32 |
1 files changed, 17 insertions, 15 deletions
diff --git a/doc/faq.raw b/doc/faq.raw index c46682496..2369fd977 100644 --- a/doc/faq.raw +++ b/doc/faq.raw @@ -1,4 +1,5 @@ [$htmltitle=GnuPG FAQ] +[$htmlcharset=<meta http-equiv="content-type" content="text/html; charset=utf-8">] [$sfaqheader=The GnuPG FAQ says:] [$sfaqfooter= The most recent version of the FAQ is available from @@ -51,7 +52,8 @@ you could search in the mailing list archive. used to encrypt data and to create digital signatures. It includes an advanced key management facility and is compliant with the proposed OpenPGP Internet standard as described in [H a href=http://www.rfc-editor.org/]RFC 2440[H/a]. - As such, it is aimed to be compatible with PGP from NAI, Inc. + As such, it is aimed to be compatible with PGP from PGP Corp. and + other OpenPGP tools <Q> Is GnuPG compatible with PGP? @@ -227,7 +229,7 @@ you could search in the mailing list archive. <Q> What is the recommended key size? - 1024 bit for DSA signatures; even for plain ElGamal signatures. + 1024 bit for DSA signatures; even for plain Elgamal signatures. This is sufficient as the size of the hash 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 @@ -238,7 +240,7 @@ you could search in the mailing list archive. [H /samp] As for the key algorithms, you should stick with the default (i.e., - DSA signature and ElGamal encryption). An ElGamal signing key has + DSA signature and Elgamal encryption). An Elgamal signing key has the following disadvantages: the signature is larger, it is hard to create such a key useful for signatures which can withstand some real world attacks, you don't get any extra security compared to @@ -722,12 +724,12 @@ you could search in the mailing list archive. <Q> Why is PGP 5.x not able to encrypt messages with some keys? - PGP, Inc. refuses to accept ElGamal keys of type 20 even for + PGP, Inc. refuses to accept Elgamal keys of type 20 even for encryption. They only support type 16 (which is identical at least for decryption). To be more inter-operable, GnuPG (starting with - version 0.3.3) now also uses type 16 for the ElGamal subkey which is + version 0.3.3) now also uses type 16 for the Elgamal subkey which is created if the default key algorithm is chosen. You may add a type - 16 ElGamal key to your public key, which is easy as your key + 16 Elgamal key to your public key, which is easy as your key signatures are still valid. <Q> Why is PGP 5.x not able to verify my messages? @@ -803,7 +805,7 @@ you could search in the mailing list archive. supports a few more features from the OpenPGP standard than PGP does. If your secret key has any of those features in use, then PGP will reject the key or you will have problems communicating later. Note - that PGP doesn't do ElGamal signing keys at all, so they are not + that PGP doesn't do Elgamal signing keys at all, so they are not usable with any version. These instructions should work for GnuPG 1.0.7 and later, and PGP @@ -941,11 +943,11 @@ you could search in the mailing list archive. That's a known bug, already fixed in newer versions. -<Q> An ElGamal signature does not verify anymore since version 1.0.2 ... +<Q> An Elgamal signature does not verify anymore since version 1.0.2 ... Use the option --emulate-md-encode-bug. -<Q> Old versions of GnuPG can't verify ElGamal signatures +<Q> Old versions of GnuPG can't verify Elgamal signatures Update to GnuPG 1.0.2 or newer. @@ -1159,7 +1161,7 @@ you could search in the mailing list archive. messages may be decrypted by people who accidently got your passphrase. You can add and copy keys to and from your keyring with the 'gpg - --import' and 'gpg --export' option. 'gpg --export-secret-keys' will + --import' and 'gpg --export' command. 'gpg --export-secret-keys' will export secret keys. This is normally not useful, but you can generate the key on one machine then move it to another machine. @@ -1192,13 +1194,13 @@ you could search in the mailing list archive. <Q> Why are some signatures with an ELG-E key valid? - These are ElGamal keys generated by GnuPG in v3 (RFC 1991) packets. - The OpenPGP draft later changed the algorithm identifier for ElGamal + These are Elgamal keys generated by GnuPG in v3 (RFC 1991) packets. + The OpenPGP draft later changed the algorithm identifier for Elgamal keys which are usable for signatures and encryption from 16 to 20. - GnuPG now uses 20 when it generates new ElGamal keys but still + GnuPG now uses 20 when it generates new Elgamal keys but still accepts 16 (which is according to OpenPGP "encryption only") if this key is in a v3 packet. GnuPG is the only program which had used - these v3 ElGamal keys - so this assumption is quite safe. + these v3 Elgamal keys - so this assumption is quite safe. <Q> How does the whole trust thing work? @@ -1339,4 +1341,4 @@ Copyright (C) 2000, 2001, 2002, 2003 Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111, USA Verbatim copying and distribution of this entire article is permitted in -any medium, provided this notice is preserved.
\ No newline at end of file +any medium, provided this notice is preserved. |