diff options
| author | Werner Koch <[email protected]> | 1999-05-20 12:11:41 +0000 |
|---|---|---|
| committer | Werner Koch <[email protected]> | 1999-05-20 12:11:41 +0000 |
| commit | 77d6309e2189254cf7a45884fb7ef6a415761988 (patch) | |
| tree | 60da5c2556a5b7cb9c8d65dedd7a293eec2a35e8 /doc/FAQ | |
| parent | See ChangeLog: Wed May 19 16:04:30 CEST 1999 Werner Koch (diff) | |
| download | gnupg-77d6309e2189254cf7a45884fb7ef6a415761988.tar.gz gnupg-77d6309e2189254cf7a45884fb7ef6a415761988.zip | |
See ChangeLog: Thu May 20 14:04:08 CEST 1999 Werner Koch
Diffstat (limited to 'doc/FAQ')
| -rw-r--r-- | doc/FAQ | 15 |
1 files changed, 9 insertions, 6 deletions
@@ -21,7 +21,7 @@ public key, and he would only be able to decrypt it by having the secret key and putting in the password to use his secret key. - GNUPG is also useful for signing things. Things that are encrypted with + GnuPG is also useful for signing things. Things that are encrypted with the secret key can be decrypted with the public key. To sign something, a hash is taken of the data, and then the hash is in some form encoded with the secret key. If someone has your public key, they can verify that it @@ -71,7 +71,7 @@ readable, just add the '-a' option. But the preferred method is to use a MIME aware mail reader (Mutt, Pine and many more). - There is a small security glitch in the OpenPGP (and therefor GNUPG) system; + There is a small security glitch in the OpenPGP (and therefore GnuPG) system; to avoid this you should always sign and encrypt a message instead of only encrypting it. @@ -85,13 +85,13 @@ "gpg --fingerprint --fingerprint <user ID>". Q: Why are some signatures with an ELG-E key valid? - A: These are ElGamal Key generated by GNUPG in v3 (rfc1991) + A: These are ElGamal Key generated by GnuPG in v3 (rfc1991) 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 + and encryption from 16 to 20. GnuPG now uses 20 when it generates new ElGamal keys but still accept 16 (which is according to OpenPGP "encryption only") if this key is in - a v3 packet. GNUPG is the only program which had used + a v3 packet. GnuPG is the only program which had used these v3 ElGamal keys - so this assumption is quite safe. Q: Why is PGP 5.x not able to encrypt messages with some keys? @@ -120,11 +120,14 @@ Q: How can I encrypt a message so that pgp 2.x is able to decrypt it? A: You can't do that because pgp 2.x normally uses IDEA which is not - supported by GNUPG because it is patented, but if you have a modified + supported by GnuPG because it is patented, but if you have a modified version of PGP you can try this: gpg --rfc1991 --cipher-algo 3des ... + Please don't pipe the data to encrypt to gpg but give it as a filename; + other wise, pgp 2 will not be able to handle it. + Q: How can I conventional encrypt a message, so that PGP can decrypt it? A: You can't do this for PGP 2. For PGP 5 you should use this: |