mirror of
git://git.gnupg.org/gnupg.git
synced 2025-06-13 18:21:03 +02:00
* faq.raw: New upstream version with new sections 1.3, 5.8, 6.20
and a list of MUAs. Replaced ftp.guug.de URL.
This commit is contained in:
parent
3ca93f344e
commit
575b4abda7
@ -1,3 +1,8 @@
|
|||||||
|
2002-10-17 Werner Koch <wk@gnupg.org>
|
||||||
|
|
||||||
|
* faq.raw: New upstream version with new sections 1.3, 5.8, 6.20
|
||||||
|
and a list of MUAs. Replaced ftp.guug.de URL.
|
||||||
|
|
||||||
2002-10-12 Werner Koch <wk@gnupg.org>
|
2002-10-12 Werner Koch <wk@gnupg.org>
|
||||||
|
|
||||||
* DETAILS (KEY_CREATED): Enhanced by fingerprint.
|
* DETAILS (KEY_CREATED): Enhanced by fingerprint.
|
||||||
|
375
doc/faq.raw
375
doc/faq.raw
@ -14,8 +14,8 @@ The most recent version of the FAQ is available from
|
|||||||
|
|
||||||
|
|
||||||
[H p]
|
[H p]
|
||||||
Version: 1.5.7[H br]
|
Version: 1.5.8[H br]
|
||||||
Last-Modified: Aug 21, 2002[H br]
|
Last-Modified: Oct 8, 2002[H br]
|
||||||
Maintained-by: [$maintainer]
|
Maintained-by: [$maintainer]
|
||||||
[H /p]
|
[H /p]
|
||||||
|
|
||||||
@ -23,17 +23,17 @@ Maintained-by: [$maintainer]
|
|||||||
This is the GnuPG FAQ. The latest HTML version is available
|
This is the GnuPG FAQ. The latest HTML version is available
|
||||||
[H a href=[$hGPG]/faq.html]here[H/a].
|
[H a href=[$hGPG]/faq.html]here[H/a].
|
||||||
|
|
||||||
The index is generated automatically, so there may be errors here. Not
|
The index is generated automatically, so there may be errors. Not all
|
||||||
all questions may be in the section they belong to. Suggestions about
|
questions may be in the section they belong to. Suggestions about how
|
||||||
how to improve the structure of this FAQ are welcome.
|
to improve the structure of this FAQ are welcome.
|
||||||
|
|
||||||
Please send additions and corrections to the maintainer. It would be
|
Please send additions and corrections to the maintainer. It would be
|
||||||
most convenient if you could provide the answer to be included here
|
most convenient if you could provide the answer to be included here
|
||||||
as well. Your help is very much appreciated.
|
as well. Your help is very much appreciated!
|
||||||
|
|
||||||
Please, don't send message like "This should be a FAQ - what's the answer?".
|
Please, don't send message like "This should be a FAQ - what's the
|
||||||
If it hasn't been asked before, it isn't a FAQ. In that case you could
|
answer?". If it hasn't been asked before, it isn't a FAQ. In that case
|
||||||
search in the mailing list archive.
|
you could search in the mailing list archive.
|
||||||
|
|
||||||
[H HR]
|
[H HR]
|
||||||
<C>
|
<C>
|
||||||
@ -54,31 +54,40 @@ search in the mailing list archive.
|
|||||||
<Q> Is GnuPG compatible with PGP?
|
<Q> Is GnuPG compatible with PGP?
|
||||||
|
|
||||||
In general, yes. GnuPG and newer PGP releases should be implementing
|
In general, yes. GnuPG and newer PGP releases should be implementing
|
||||||
the OpenPGP standard. But there are some interoperability
|
the OpenPGP standard. But there are some interoperability problems.
|
||||||
problems. See question <Rcompat> for details.
|
See question <Rcompat> for details.
|
||||||
|
|
||||||
|
<Q> Is GnuPG free to use for personal or commercial use?
|
||||||
|
|
||||||
|
Yes. GnuPG is part of the GNU family of tools and applications built
|
||||||
|
and provided in accordance with the Free Software Foundation (FSF)
|
||||||
|
General Public License (GPL). Therefore the software is free to copy,
|
||||||
|
use, modify and distribute in accordance with that license. Please
|
||||||
|
read the file titled COPYING that accompanies the application for
|
||||||
|
more information.
|
||||||
|
|
||||||
|
|
||||||
<S> SOURCES of INFORMATION
|
<S> SOURCES of INFORMATION
|
||||||
|
|
||||||
<Q> Where can I find more information?
|
<Q> Where can I find more information on GnuPG?
|
||||||
|
|
||||||
Here's a list of on-line resources:
|
On-line resources:
|
||||||
|
|
||||||
[H UL]
|
[H UL]
|
||||||
[H LI]The documentation page is located at [H a href=[$hGPG]/docs.html]<[$hGPG]/docs.html>[H/a].
|
[H LI]The documentation page is located at [H a href=[$hGPG]/docs.html]<[$hGPG]/docs.html>[H/a].
|
||||||
Have a look at the HOWTOs and the GNU Privacy Handbook (GPH, available
|
Also, have a look at the HOWTOs and the GNU Privacy Handbook (GPH,
|
||||||
in English, Spanish and Russian). The latter provides a detailed user's
|
available in English, Spanish and Russian). The latter provides a
|
||||||
guide to GnuPG. You'll also find a document about how to convert from
|
detailed user's guide to GnuPG. You'll also find a document about
|
||||||
PGP 2.x to GnuPG.
|
how to convert from PGP 2.x to GnuPG.
|
||||||
|
|
||||||
[H LI]On [H a href=http://lists.gnupg.org]<http://lists.gnupg.org>[H/a] you'll find an online archive of the
|
[H LI]At [H a href=http://lists.gnupg.org]<http://lists.gnupg.org>[H/a] you'll find an online archive of the
|
||||||
GnuPG mailing lists. Most interesting should be gnupg-users for all
|
GnuPG mailing lists. Most interesting should be gnupg-users for all
|
||||||
user-related issues and gnupg-devel if you want to get in touch with
|
user-related issues and gnupg-devel if you want to get in touch with
|
||||||
the developers.
|
the developers.
|
||||||
|
|
||||||
In addition, searchable archives can be found on MARC, e.g.: [H br]
|
In addition, searchable archives can be found on MARC, e.g.: [H br]
|
||||||
GnuPG-users: [H a href=http://marc.theaimsgroup.com/?l=gnupg-users&r=1&w=2]<http://marc.theaimsgroup.com/?l=gnupg-users&r=1&w=2>[H/a],[H br]
|
gnupg-users: [H a href=http://marc.theaimsgroup.com/?l=gnupg-users&r=1&w=2]<http://marc.theaimsgroup.com/?l=gnupg-users&r=1&w=2>[H/a],[H br]
|
||||||
GnuPG-devel: [H a href=http://marc.theaimsgroup.com/?l=gnupg-devel&r=1&w=2]<http://marc.theaimsgroup.com/?l=gnupg-devel&r=1&w=2>[H/a].[H br]
|
gnupg-devel: [H a href=http://marc.theaimsgroup.com/?l=gnupg-devel&r=1&w=2]<http://marc.theaimsgroup.com/?l=gnupg-devel&r=1&w=2>[H/a].[H br]
|
||||||
|
|
||||||
[H B]PLEASE:[H/B]
|
[H B]PLEASE:[H/B]
|
||||||
Before posting to a list, read this FAQ and the available
|
Before posting to a list, read this FAQ and the available
|
||||||
@ -99,28 +108,30 @@ search in the mailing list archive.
|
|||||||
<Q> Where do I get GnuPG?
|
<Q> Where do I get GnuPG?
|
||||||
|
|
||||||
You can download the GNU Privacy Guard from its primary FTP server
|
You can download the GNU Privacy Guard from its primary FTP server
|
||||||
[H a href=ftp://ftp.gnupg.org/pub/gcrypt]ftp.gnupg.org[H /a] or from one of the mirrors:
|
[H a href=ftp://ftp.gnupg.org/pub/gcrypt]<ftp.gnupg.org>[H /a] or from one of the mirrors:
|
||||||
|
|
||||||
[H a href=[$hGPG]/mirrors.html]
|
[H a href=[$hGPG]/mirrors.html]
|
||||||
<[$hGPG]/mirror.html>
|
<[$hGPG]/mirror.html>
|
||||||
[H /a]
|
[H /a]
|
||||||
|
|
||||||
The current version is 1.0.4, please upgrade to this version as it
|
The current stable version is 1.2.x. Please upgrade to this version as
|
||||||
fixes a security bug regarding the verification of multiple signatures.
|
it includes additional features, functions and security fixes that may
|
||||||
|
not have existed in prior versions.
|
||||||
|
|
||||||
|
|
||||||
<S> INSTALLATION
|
<S> INSTALLATION
|
||||||
|
|
||||||
<Q> Which OSes does GnuPG run on?
|
<Q> Which OSes does GnuPG run on?
|
||||||
|
|
||||||
It should run on most Unices as well as Windows 95 and Windows NT. A
|
It should run on most Unices as well as Windows versions (including
|
||||||
list of OSes reported to be OK is presented at:
|
Windows NT/2000) and Macintosh OS/X. A list of OSes reported to be OK
|
||||||
|
is presented at:
|
||||||
|
|
||||||
[H a href=http://www.gnupg.org/backend.html#supsys]
|
[H a href=http://www.gnupg.org/backend.html#supsys]
|
||||||
<http://www.gnupg.org/gnupg.html#supsys>
|
<http://www.gnupg.org/gnupg.html#supsys>
|
||||||
[H /a]
|
[H /a]
|
||||||
|
|
||||||
<Q> Which random gatherer should I use?
|
<Q> Which random data gatherer should I use?
|
||||||
|
|
||||||
"Good" random numbers are crucial for the security of your encryption.
|
"Good" random numbers are crucial for the security of your encryption.
|
||||||
Different operating systems provide a variety of more or less quality
|
Different operating systems provide a variety of more or less quality
|
||||||
@ -134,13 +145,13 @@ search in the mailing list archive.
|
|||||||
[H/pre]
|
[H/pre]
|
||||||
|
|
||||||
In addition, there's also the kernel random device by Andi Maier
|
In addition, there's also the kernel random device by Andi Maier
|
||||||
[H a href= http://www.cosy.sbg.ac.at/~andi]<http://www.cosy.sbg.ac.at/~andi>[H /a], but it's still beta. Use at your
|
[H a href= http://www.cosy.sbg.ac.at/~andi/]<http://www.cosy.sbg.ac.at/~andi/>[H /a], but it's still beta. Use at your
|
||||||
own risk!
|
own risk!
|
||||||
|
|
||||||
On other systems, the Entropy Gathering Daemon (EGD) is a good choice.
|
On other systems, the Entropy Gathering Daemon (EGD) is a good choice.
|
||||||
It is a perl-daemon that monitors system activity and hashes it into
|
It is a perl-daemon that monitors system activity and hashes it into
|
||||||
random data. See the download page [H a href=http://www.gnupg.org/download.html]<http://www.gnupg.org/download.html>[H /a]
|
random data. See the download page [H a href=http://www.gnupg.org/download.html]<http://www.gnupg.org/download.html>[H /a]
|
||||||
to obtain egd. Use:
|
to obtain EGD. Use:
|
||||||
|
|
||||||
[H pre]
|
[H pre]
|
||||||
--enable-static-rnd=egd
|
--enable-static-rnd=egd
|
||||||
@ -149,28 +160,28 @@ search in the mailing list archive.
|
|||||||
here.
|
here.
|
||||||
|
|
||||||
If the above options do not work, you can use the random number
|
If the above options do not work, you can use the random number
|
||||||
generator "unix". This is [H B]very[H /B] slow and should be avoiced. The
|
generator "unix". This is [H B]very[H /B] slow and should be avoided. The
|
||||||
random quality isn't very good so don't use it on sensitive data.
|
random quality isn't very good so don't use it on sensitive data.
|
||||||
|
|
||||||
<Didea>
|
<Didea>
|
||||||
<Q> How do I include support for RSA and IDEA?
|
<Q> How do I include support for RSA and IDEA?
|
||||||
|
|
||||||
RSA is included as of GnuPG 1.0.3.
|
RSA is included as of GnuPG version 1.0.3.
|
||||||
|
|
||||||
The official GnuPG distribution does not contain IDEA due to a
|
The official GnuPG distribution does not contain IDEA due to a patent
|
||||||
patent restriction. The patent does not expire before 2007 so don't
|
restriction. The patent does not expire before 2007 so don't expect
|
||||||
expect official support before then.
|
official support before then.
|
||||||
|
|
||||||
However, there is an unofficial module to include it even
|
However, there is an unofficial module to include it even in earlier
|
||||||
in earlier versions of GnuPG. It's available from
|
versions of GnuPG. It's available from
|
||||||
[H a href=ftp://ftp.gnupg.org/pub/gcrypt/contrib/]<ftp://ftp.gnupg.org/pub/gcrypt/contrib/>[H /a]. Look for:
|
[H a href=ftp://ftp.gnupg.org/pub/gcrypt/contrib/]<ftp://ftp.gnupg.org/pub/gcrypt/contrib/>[H /a]. Look for:
|
||||||
|
|
||||||
[H pre]
|
[H pre]
|
||||||
idea.c
|
idea.c
|
||||||
[H /pre]
|
[H /pre]
|
||||||
|
|
||||||
Compilation directives are in the headers of these files. Then add
|
Compilation directives are in the headers of these files. You will
|
||||||
the following line to your ~/.gnupg/options:
|
then need to add the following line to your ~/.gnupg/options file:
|
||||||
|
|
||||||
[H pre]
|
[H pre]
|
||||||
load-extension idea
|
load-extension idea
|
||||||
@ -181,8 +192,8 @@ search in the mailing list archive.
|
|||||||
|
|
||||||
<Q> What is the recommended key size?
|
<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
|
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
|
link if the key size is larger than 1024 bits. Encryption keys may
|
||||||
have greater sizes, but you should then check the fingerprint of
|
have greater sizes, but you should then check the fingerprint of
|
||||||
this key:
|
this key:
|
||||||
@ -192,9 +203,9 @@ search in the mailing list archive.
|
|||||||
[H /pre]
|
[H /pre]
|
||||||
|
|
||||||
As for the key algorithms, you should stick with the default (i.e.,
|
As for the key algorithms, you should stick with the default (i.e.,
|
||||||
DSA signature and ElGamal encryption). A ElGamal signing key has the
|
DSA signature and ElGamal encryption). An ElGamal signing key has
|
||||||
following disadvantages: the signature is larger, it is hard to
|
the following disadvantages: the signature is larger, it is hard
|
||||||
create such a key useful for signatures which can withstand some
|
to create such a key useful for signatures which can withstand some
|
||||||
real world attacks, you don't get any extra security compared to
|
real world attacks, you don't get any extra security compared to
|
||||||
DSA, and there might be compatibility problems with certain PGP
|
DSA, and there might be compatibility problems with certain PGP
|
||||||
versions. It has only been introduced because at the time it was
|
versions. It has only been introduced because at the time it was
|
||||||
@ -222,12 +233,12 @@ search in the mailing list archive.
|
|||||||
over your secret key ring (which is in most cases vulnerable to
|
over your secret key ring (which is in most cases vulnerable to
|
||||||
advanced dictionary attacks) - I strongly encourage everyone to only
|
advanced dictionary attacks) - I strongly encourage everyone to only
|
||||||
create keys on a local computer (a disconnected laptop is probably
|
create keys on a local computer (a disconnected laptop is probably
|
||||||
the best choice) and if you need it on your connected box (I know:
|
the best choice) and if you need it on your connected box (I know,
|
||||||
We all do this) be sure to have a strong password for your account
|
we all do this) be sure to have a strong password for both your
|
||||||
and for your secret key and that you can trust your system
|
account and for your secret key, and that you can trust your system
|
||||||
administrator.
|
administrator.
|
||||||
|
|
||||||
When I check GnuPG on a remote system via ssh (I have no Alpha here
|
When I check GnuPG on a remote system via ssh (I have no Alpha here)
|
||||||
;-) I have the same problem. It takes a *very* long time to create
|
;-) I have the same problem. It takes a *very* long time to create
|
||||||
the keys, so I use a special option, --quick-random, to generate
|
the keys, so I use a special option, --quick-random, to generate
|
||||||
insecure keys which are only good for some tests.
|
insecure keys which are only good for some tests.
|
||||||
@ -247,14 +258,15 @@ search in the mailing list archive.
|
|||||||
[H/pre]
|
[H/pre]
|
||||||
|
|
||||||
Some options take arguments. For example, the --output option (which
|
Some options take arguments. For example, the --output option (which
|
||||||
can be abbreviated -o) is an option that takes a filename. The
|
can be abbreviated as -o) is an option that takes a filename. The
|
||||||
option's argument must follow immediately after the option itself,
|
option's argument must follow immediately after the option itself,
|
||||||
otherwise gpg doesn't know which option the argument is supposed to
|
otherwise gpg doesn't know which option the argument is supposed to
|
||||||
go with. As an option, --output and its filename must come before
|
paired with. As an option, --output and its filename must come before
|
||||||
the command. The --recipient (-r) option takes a name or keyid to
|
the command. The --recipient (-r) option takes a name or keyID to
|
||||||
encrypt the message to, which must come right after the -r argument.
|
encrypt the message to, which must come right after the -r argument.
|
||||||
The --encrypt (or -e) command comes after all the options followed
|
The --encrypt (or -e) command comes after all the options and is
|
||||||
by the file you wish to encrypt. So use:
|
followed by the file you wish to encrypt. Therefore in this example
|
||||||
|
the command-line issued would be:
|
||||||
|
|
||||||
[H pre]
|
[H pre]
|
||||||
gpg -r alice -o secret.txt -e test.txt
|
gpg -r alice -o secret.txt -e test.txt
|
||||||
@ -266,9 +278,10 @@ search in the mailing list archive.
|
|||||||
gpg --recipient alice --output secret.txt --encrypt test.txt
|
gpg --recipient alice --output secret.txt --encrypt test.txt
|
||||||
[H/pre]
|
[H/pre]
|
||||||
|
|
||||||
If you're saving it in a file called ".txt" then you'd probably
|
If you're encrypting to a file with the extension ".txt", then you'd
|
||||||
expect to see ASCII-armored text in there, so you need to add the
|
probably expect to see ASCII-armored text in the file (not binary),
|
||||||
--armor (-a) option, which doesn't take any arguments:
|
so you need to add the --armor (-a) option, which doesn't take any
|
||||||
|
arguments:
|
||||||
|
|
||||||
[H pre]
|
[H pre]
|
||||||
gpg --armor --recipient alice --output secret.txt --encrypt test.txt
|
gpg --armor --recipient alice --output secret.txt --encrypt test.txt
|
||||||
@ -288,17 +301,19 @@ search in the mailing list archive.
|
|||||||
[H/pre]
|
[H/pre]
|
||||||
|
|
||||||
If your filename begins with a hyphen (e.g. "-a.txt"), GnuPG assumes
|
If your filename begins with a hyphen (e.g. "-a.txt"), GnuPG assumes
|
||||||
this is an option and may complain. To avoid this you have either
|
this is an option and may complain. To avoid this you have to either
|
||||||
to use "./-a.txt" or stop the option and command processing with two
|
use "./-a.txt", or stop the option and command processing with two
|
||||||
hyphens: "-- -a.txt". [H B]The exception:[H /B] signing and encrypting at the
|
hyphens: "-- -a.txt".
|
||||||
same time. Use:
|
|
||||||
|
[H B]The exception to using only one command:[H /B] signing and encrypting
|
||||||
|
at the same time. For this you can combine both commands, such as in:
|
||||||
|
|
||||||
[H pre]
|
[H pre]
|
||||||
gpg [--options] --sign --encrypt foo.txt
|
gpg [--options] --sign --encrypt foo.txt
|
||||||
[H/pre]
|
[H/pre]
|
||||||
|
|
||||||
<Q> I can't delete a user ID because it is already deleted on my public
|
<Q> I can't delete a user ID on my secret keyring because it has
|
||||||
keyring?
|
already been deleted on my public keyring. What can I do?
|
||||||
|
|
||||||
Because you can only select from the public key ring, there is no
|
Because you can only select from the public key ring, there is no
|
||||||
direct way to do this. However it is not very complicated to do
|
direct way to do this. However it is not very complicated to do
|
||||||
@ -307,43 +322,46 @@ search in the mailing list archive.
|
|||||||
ring. Now select this user ID and delete it. Both user IDs will be
|
ring. Now select this user ID and delete it. Both user IDs will be
|
||||||
removed from the secret ring.
|
removed from the secret ring.
|
||||||
|
|
||||||
<Q> I can't delete the secret key because my public key disappeared?
|
<Q> I can't delete my secret key because the public key disappeared.
|
||||||
|
What can I do?
|
||||||
|
|
||||||
To select a key a search is always done on the public keyring,
|
To select a key a search is always done on the public keyring,
|
||||||
therefore it is not possible to select an secret key without
|
therefore it is not possible to select a secret key without
|
||||||
having the public key. Normally it shoud never happen that the
|
having the public key. Normally it shoud never happen that the
|
||||||
public key got lost but the secret key is still available. The
|
public key got lost but the secret key is still available. The
|
||||||
reality is different, so GnuPG implements a special way to deal
|
reality is different, so GnuPG implements a special way to deal
|
||||||
with it: Simply use the long keyid which can be obtained by using
|
with it: Simply use the long keyID to specify the key to delete,
|
||||||
the --with-colons options (it is the fifth field in the lines
|
which can be obtained by using the --with-colons options (it is
|
||||||
beginning with "sec").
|
the fifth field in the lines beginning with "sec").
|
||||||
|
|
||||||
<Q> What are trust, validity and ownertrust?
|
<Q> What are trust, validity and ownertrust?
|
||||||
|
|
||||||
"ownertrust" is used instead of "trust" to make clear that this is
|
With GnuPG, the term "ownertrust" is used instead of "trust" to
|
||||||
the value you have assigned to a key to express how much you trust
|
help clarify that this is the value you have assigned to a key
|
||||||
the owner of this key to correctly sign (and so introduce) other
|
to express how much you trust the owner of this key to correctly
|
||||||
keys. "validity", or calculated trust, is a value which says how
|
sign (and thereby introduce) other keys. The "validity", or
|
||||||
much GnuPG thinks a key is valid (that it really belongs to the one
|
calculated trust, is a value which indicates how much GnuPG
|
||||||
who claims to be the owner of the key). For more see the chapter
|
considers a key as being valid (that it really belongs to the
|
||||||
"The Web of Trust" in the Manual.
|
one who claims to be the owner of the key). For more information
|
||||||
|
on trust values see the chapter "The Web of Trust" in The GNU
|
||||||
|
Privacy Handbook.
|
||||||
|
|
||||||
<Q> How do I sign a patch file?
|
<Q> How do I sign a patch file?
|
||||||
|
|
||||||
Use "gpg --clearsign --not-dash-escaped ...". The problem with
|
Use "gpg --clearsign --not-dash-escaped ...". The problem with
|
||||||
--clearsign is that all lines starting with a dash are quoted with
|
--clearsign is that all lines starting with a dash are quoted with
|
||||||
"- "; obviously diff produces many lines starting with a dash and
|
"- "; obviously diff produces many lines starting with a dash and
|
||||||
these are then quoted and that is not good for a patch ;-). To use a
|
these are then quoted and that is not good for a patch ;-). To use
|
||||||
patch file without removing the cleartext signature, the special
|
a patch file without removing the cleartext signature, the special
|
||||||
option --not-dash-escaped may be used to suppress generation of
|
option --not-dash-escaped may be used to suppress generation of
|
||||||
these escape sequences. You should not mail such a patch because
|
these escape sequences. You should not mail such a patch because
|
||||||
spaces and line endings are also subject to the signature and a
|
spaces and line endings are also subject to the signature and a
|
||||||
mailer may not preserve these. If you want to mail a file you can
|
mailer may not preserve these. If you want to mail a file you can
|
||||||
simply sign it using your MUA.
|
simply sign it using your MUA (Mail User Agent).
|
||||||
|
|
||||||
<Q> Where is the "encrypt-to-self" option?
|
<Q> Where is the "encrypt-to-self" option?
|
||||||
|
|
||||||
Use "--encrypt-to your_keyid". You can use more than one of these
|
Use "--encrypt-to your_keyID". You can use more than one of these
|
||||||
options. To temporarily override the use of this additional key,
|
options. To temporarily override the use of this additional key,
|
||||||
you can use the option "--no-encrypt-to".
|
you can use the option "--no-encrypt-to".
|
||||||
|
|
||||||
@ -355,13 +373,13 @@ search in the mailing list archive.
|
|||||||
|
|
||||||
<Q> What does the "You are using the xxxx character set." mean?
|
<Q> What does the "You are using the xxxx character set." mean?
|
||||||
|
|
||||||
This note is printed when UTF8 mapping has to be done. Make sure
|
This note is printed when UTF-8 mapping has to be done. Make sure
|
||||||
that the displayed charset is the one you have activated on your
|
that the displayed character set is the one you have activated on
|
||||||
system. Since "iso-8859-1" is the charset most used, this is the
|
your system. Since "iso-8859-1" is the character set most used,
|
||||||
default. You can change the charset with the option "--charset".
|
this is the default. You can change the charset with the option
|
||||||
It is important that your active character set matches the one
|
"--charset". It is important that your active character set matches
|
||||||
displayed - if not, restrict yourself to plain 7 bit ASCII and no
|
the one displayed - if not, restrict yourself to plain 7 bit ASCII
|
||||||
mapping has to be done.
|
and no mapping has to be done.
|
||||||
|
|
||||||
<Q> How can a get list of key IDs used to encrypt a message?
|
<Q> How can a get list of key IDs used to encrypt a message?
|
||||||
|
|
||||||
@ -370,28 +388,31 @@ search in the mailing list archive.
|
|||||||
awk '/^\[GNUPG:\] ENC_TO / { print $3 }'
|
awk '/^\[GNUPG:\] ENC_TO / { print $3 }'
|
||||||
[H /pre]
|
[H /pre]
|
||||||
|
|
||||||
<Q> I can't decrypt my symmetrical only (-c) encrypted message with
|
<Q> I can't decrypt my symmetrical-only (-c) encrypted messages with
|
||||||
a new version of GnuPG.
|
a new version of GnuPG.
|
||||||
|
|
||||||
There used to be a bug in GnuPG < 1.0.1 which happens only if 3DES
|
There was a bug in GnuPG versions prior to 1.0.1 which affected
|
||||||
or Twofish has been used for symmetric only encryption (this has
|
messages only if 3DES or Twofish was used for symmetric-only
|
||||||
never been the default). The bug has been fixed but to enable you
|
encryption (this has never been the default). The bug has been
|
||||||
to decrypt old messages, you should run gpg with the option
|
fixed, but to enable decryption of old messages you should run gpg
|
||||||
"--emulate-3des-s2k-bug", decrypt the message and encrypt it again
|
with the option "--emulate-3des-s2k-bug", decrypt the message and
|
||||||
without this option. The option will be removed in 1.1, so better
|
encrypt it again without this option. The option will be removed
|
||||||
re-encrypt your message now.
|
in version 1.1 when released, so please re-encrypt any affected
|
||||||
|
messages now.
|
||||||
|
|
||||||
<Q> How can I use GnuPG in an automated environment?
|
<Q> How can I use GnuPG in an automated environment?
|
||||||
|
|
||||||
You should use the option --batch and don't use passphrases as
|
You should use the option --batch and don't use passphrases as
|
||||||
there is usually no way to store it more secure than the secret
|
there is usually no way to store it more securely than on the
|
||||||
keyring itself. The suggested way to create the keys for the
|
secret keyring itself. The suggested way to create keys for an
|
||||||
automated environment is:
|
automated environment is:
|
||||||
|
|
||||||
On a secure machine:
|
On a secure machine:
|
||||||
[H OL]
|
[H OL]
|
||||||
[H LI] If you want to do automatic signing, create a signing
|
[H LI] If you want to do automatic signing, create a signing subkey
|
||||||
subkey for your key (edit menu, choose "addkey" and the DSA).
|
for your key (use the interactive key editing menu by issueing
|
||||||
|
the command 'gpg --edit-key keyID', enter "addkey" and select
|
||||||
|
the DSA key type).
|
||||||
[H LI] Make sure that you use a passphrase (needed by the current
|
[H LI] Make sure that you use a passphrase (needed by the current
|
||||||
implementation).
|
implementation).
|
||||||
[H LI] gpg --export-secret-subkeys --no-comment foo >secring.auto
|
[H LI] gpg --export-secret-subkeys --no-comment foo >secring.auto
|
||||||
@ -405,9 +426,9 @@ search in the mailing list archive.
|
|||||||
|
|
||||||
On the target machine:
|
On the target machine:
|
||||||
[H OL]
|
[H OL]
|
||||||
[H LI] Install secring.auto as secret keyring.
|
[H LI] Install secring.auto as the secret keyring.
|
||||||
[H LI] Now you can start your new service. It is a good idea to
|
[H LI] Now you can start your new service. It's also a good idea to
|
||||||
install some intrusion detection system so that you hopefully
|
install an intrusion detection system so that you hopefully
|
||||||
get a notice of an successful intrusion, so that you in turn
|
get a notice of an successful intrusion, so that you in turn
|
||||||
can revoke all the subkeys installed on that machine and
|
can revoke all the subkeys installed on that machine and
|
||||||
install new subkeys.
|
install new subkeys.
|
||||||
@ -416,26 +437,73 @@ search in the mailing list archive.
|
|||||||
<Q> Which email-client can I use with GnuPG?
|
<Q> Which email-client can I use with GnuPG?
|
||||||
|
|
||||||
Using GnuPG to encrypt email is one of the most popular uses.
|
Using GnuPG to encrypt email is one of the most popular uses.
|
||||||
Several mail clients or mail user-agents (MUA) support GnuPG at
|
Several mail clients or mail user agents (MUAs) support GnuPG to
|
||||||
varying degrees. Simplifying a bit, there are two ways mail can be
|
varying degrees. Simplifying a bit, there are two ways mail can be
|
||||||
encrypted with GnuPG: the "old style" ASCII armor, i.e. plain text
|
encrypted with GnuPG: the "old style" ASCII armor (i.e. cleartext
|
||||||
encryption, and RFC2015 style (previously PGP/MIME, now OpenPGP).
|
encryption), and RFC 2015 style (previously PGP/MIME, now OpenPGP).
|
||||||
The latter has full MIME support. Some MUAs support only one of
|
The latter has full MIME support. Some MUAs support only one of
|
||||||
them, so whichever you actually use depends on your needs as well
|
them, so whichever you actually use depends on your needs as well
|
||||||
as the capabilities of your addressee.
|
as the capabilities of your addressee. As well, support may be
|
||||||
|
native to the MUA, or provided via "plug-ins" or external tools.
|
||||||
|
|
||||||
The following list is probably not exhaustive:
|
The following list is not exhaustive:
|
||||||
|
|
||||||
OpenPGP: Mutt (Unix), Emacs/Mew, Becky2 (Windows, with plugin),
|
[H pre]
|
||||||
TkRat (Unix). There is effort for a Mozilla plugin and
|
MUA OpenPGP ASCII How? (N,P,T)
|
||||||
Emacs/GNUS has support in the current CVS.
|
---------------------------------------------------------------
|
||||||
|
Calypso N Y P (Unixmail)
|
||||||
|
Elm N Y T (mailpgp,morepgp)
|
||||||
|
Elm ME+ N Y N
|
||||||
|
Emacs/Gnus Y Y T (Mailcrypt,gpg.el)
|
||||||
|
Emacs/Mew Y Y N
|
||||||
|
Emacs/VM N Y T (Mailcrypt)
|
||||||
|
Evolution Y Y N
|
||||||
|
Exmh Y Y N
|
||||||
|
GNUMail.app Y Y P (PGPBundle)
|
||||||
|
GPGMail Y Y N
|
||||||
|
KMail (<=1.4.x) N Y N
|
||||||
|
KMail (1.5.x) Y(P) Y(N) P/N
|
||||||
|
Mozilla Y Y P (Enigmail)
|
||||||
|
Mulberry Y Y P
|
||||||
|
Mutt Y Y N
|
||||||
|
Sylpheed Y Y N
|
||||||
|
Sylpheed-claws Y Y N
|
||||||
|
TkRat Y Y N
|
||||||
|
XEmacs/Gnus Y Y T (Mailcrypt)
|
||||||
|
XEmacs/Mew Y Y N
|
||||||
|
XEmacs/VM N Y T (Mailcrypt)
|
||||||
|
XFmail Y Y N
|
||||||
|
|
||||||
ASCII: Emacs/{VM,GNUS}/MailCrypt, Mutt(Unix), Pine(Unix), and
|
N - Native, P - Plug-in, T - External Tool
|
||||||
probably many more.
|
[H /pre]
|
||||||
|
|
||||||
Good overviews of OpenPGP-support can be found at
|
The following table lists proprietary MUAs. The GNU Project
|
||||||
[H a href=http://cryptorights.org/pgp-users/pgp-mail-clients.html]http://cryptorights.org/pgp-users/pgp-mail-clients.html[H /a]
|
suggests against the use of these programs, but they are listed
|
||||||
and [H a href=http://www.geocities.com/openpgp/courrier_en.html]http://www.geocities.com/openpgp/courrier_en.html[H /a].
|
for interoperability reasons for your convenience.
|
||||||
|
|
||||||
|
[H pre]
|
||||||
|
MUA OpenPGP ASCII How? (N,P,T)
|
||||||
|
---------------------------------------------------------------
|
||||||
|
Apple Mail Y Y P (GPGMail)
|
||||||
|
Becky2 Y Y P (BkGnuPG)
|
||||||
|
Eudora Y Y P (EuroraGPG)
|
||||||
|
Eudora Pro Y Y P (EudoraGPG)
|
||||||
|
Lotus Notes N Y P
|
||||||
|
Netscape 4.x N Y P
|
||||||
|
Netscape 7.x Y Y P (Enigmail)
|
||||||
|
Novell Groupwise N Y P
|
||||||
|
Outlook N Y P (G-Data)
|
||||||
|
Outlook Express N Y P (GPGOE)
|
||||||
|
Pegasus N Y P (QDPGP,PM-PGP)
|
||||||
|
Pine N Y T (pgpenvelope,(gpg|pgp)4pine)
|
||||||
|
Postme N Y P (GPGPPL)
|
||||||
|
The Bat! N Y P (Ritlabs)
|
||||||
|
[H /pre]
|
||||||
|
|
||||||
|
Good overviews of OpenPGP-support can be found at:[H br]
|
||||||
|
[H a href=http://cryptorights.org/pgp-users/resources/pgp-mail-clients.html]<http://cryptorights.org/pgp-users/resources/pgp-mail-clients.html>[H /a],[H br]
|
||||||
|
[H a href=http://www.geocities.com/openpgp/courrier_en.html]<http://www.geocities.com/openpgp/courrier_en.html>[H /a] and[H br]
|
||||||
|
[H a href=http://www.bretschneidernet.de/tips/secmua.html]<http://www.bretschneidernet.de/tips/secmua.html>[H /a].
|
||||||
|
|
||||||
<Q> Can't we have a gpg library?
|
<Q> Can't we have a gpg library?
|
||||||
|
|
||||||
@ -443,7 +511,7 @@ search in the mailing list archive.
|
|||||||
of the GnuPG maintainers is that this would lead to several security
|
of the GnuPG maintainers is that this would lead to several security
|
||||||
issues and will therefore not be implemented in the foreseeable
|
issues and will therefore not be implemented in the foreseeable
|
||||||
future. However, for some areas of application gpgme could do the
|
future. However, for some areas of application gpgme could do the
|
||||||
trick. You'll find it at [H a href=ftp://ftp.guug.de/pub/gcrypt/alpha/gpgme]ftp://ftp.guug.de/pub/gcrypt/alpha/gpgme[H /a].
|
trick. You'll find it at [H a href=ftp://ftp.gnupg.org/gcrypt/alpha/gpgme]<ftp://ftp.gnupg.org/gcrypt/alpha/gpgme>[H /a].
|
||||||
|
|
||||||
<Q> I have successfully generated a revocation certificate, but I don't
|
<Q> I have successfully generated a revocation certificate, but I don't
|
||||||
understand how to send it to the key servers.
|
understand how to send it to the key servers.
|
||||||
@ -531,7 +599,7 @@ search in the mailing list archive.
|
|||||||
algorithm is still patented until 2007. Under certain conditions you
|
algorithm is still patented until 2007. Under certain conditions you
|
||||||
may use IDEA even today. In that case, you may refer to Question
|
may use IDEA even today. In that case, you may refer to Question
|
||||||
<Ridea> about how to add IDEA support to GnuPG and read
|
<Ridea> about how to add IDEA support to GnuPG and read
|
||||||
[H a href=http://www.gnupg.org/gph/en/pgp2x.html]http://www.gnupg.org/gph/en/pgp2x.html[H /a] to perform the migration.
|
[H a href=http://www.gnupg.org/gph/en/pgp2x.html]<http://www.gnupg.org/gph/en/pgp2x.html>[H /a] to perform the migration.
|
||||||
|
|
||||||
<Q> (removed)
|
<Q> (removed)
|
||||||
|
|
||||||
@ -600,6 +668,14 @@ search in the mailing list archive.
|
|||||||
--export-secret-keys <key-ID>
|
--export-secret-keys <key-ID>
|
||||||
[H /pre]
|
[H /pre]
|
||||||
|
|
||||||
|
<Q> I just installed the most recent version of GnuPG and don't have a
|
||||||
|
~/.gnupg/options file. Is this missing from the installation?
|
||||||
|
|
||||||
|
No. The ~/.gnupg/options file has been renamed to ~/.gnupg/conf for
|
||||||
|
new installs as of version 1.1.92. If an existing ~/.gnupg/options file
|
||||||
|
is found during an upgrade it will still be used, but this change was
|
||||||
|
required to have a more consistent naming scheme with forthcoming tools.
|
||||||
|
|
||||||
|
|
||||||
<S> PROBLEMS and ERROR MESSAGES
|
<S> PROBLEMS and ERROR MESSAGES
|
||||||
|
|
||||||
@ -612,6 +688,22 @@ search in the mailing list archive.
|
|||||||
memory your operating system supports locking without being root. The
|
memory your operating system supports locking without being root. The
|
||||||
program drops root privileges as soon as locked memory is allocated.
|
program drops root privileges as soon as locked memory is allocated.
|
||||||
|
|
||||||
|
To setuid(root) permissions on the gpg binary you can either use:
|
||||||
|
|
||||||
|
[H pre]
|
||||||
|
chmod u+s /path/to/gpg
|
||||||
|
[H /pre]
|
||||||
|
|
||||||
|
or
|
||||||
|
|
||||||
|
[H pre]
|
||||||
|
chmod 4755 /path/to/gpg
|
||||||
|
[H /pre]
|
||||||
|
|
||||||
|
Some refrain from using setuid(root) unless absolutely required for
|
||||||
|
security reasons. Please check with your system administrator if you
|
||||||
|
are not able to make these determinations yourself.
|
||||||
|
|
||||||
On UnixWare 2.x and 7.x you should install GnuPG with the 'plock'
|
On UnixWare 2.x and 7.x you should install GnuPG with the 'plock'
|
||||||
privilege to get the same effect:
|
privilege to get the same effect:
|
||||||
|
|
||||||
@ -641,14 +733,14 @@ search in the mailing list archive.
|
|||||||
|
|
||||||
<Q> Large File Support doesn't work ...
|
<Q> Large File Support doesn't work ...
|
||||||
|
|
||||||
LFS is correctly working in post-1.0.4 CVS. If configure doesn't
|
LFS works correctly in post-1.0.4 versions. If configure doesn't
|
||||||
detect it correctly, try a different (i.e., better) compiler. egcs
|
detect it, try a different (i.e., better) compiler. egcs 1.1.2 works
|
||||||
1.1.2 works fine, other gccs sometimes don't. BTW, several
|
fine, other gccs sometimes don't. BTW, several compilation problems
|
||||||
compilation problems of GnuPG 1.0.3 and 1.0.4 on HP-UX and Solaris
|
of GnuPG 1.0.3 and 1.0.4 on HP-UX and Solaris were due to broken LFS
|
||||||
were due to broken LFS support.
|
support.
|
||||||
|
|
||||||
<Q> In the edit menu the trust values is not displayed correctly after
|
<Q> In the edit menu the trust values are not displayed correctly after
|
||||||
signing uids - why?
|
signing uids. Why?
|
||||||
|
|
||||||
This happens because some information is stored immediately in
|
This happens because some information is stored immediately in
|
||||||
the trustdb, but the actual trust calculation can be done after the
|
the trustdb, but the actual trust calculation can be done after the
|
||||||
@ -704,20 +796,21 @@ search in the mailing list archive.
|
|||||||
|
|
||||||
<Q> I get "gpg: waiting for lock ..."
|
<Q> I get "gpg: waiting for lock ..."
|
||||||
|
|
||||||
A previous gpg has most likely exited abnormally and left a lock
|
A previous instance of gpg has most likely exited abnormally and left
|
||||||
file. Go to ~/.gnupg and look for .*.lock files and remove them.
|
a lock file. Go to ~/.gnupg and look for .*.lock files and remove them.
|
||||||
|
|
||||||
<Q> Older gpg's (e.g., 1.0) have problems with keys from newer gpgs ...
|
<Q> Older gpg binaries (e.g., 1.0) have problems with keys from newer
|
||||||
|
gpg binaries ...
|
||||||
|
|
||||||
As of 1.0.3, keys generated with gpg are created with preferences to
|
As of 1.0.3, keys generated with gpg are created with preferences to
|
||||||
TWOFISH (and AES since 1.0.4) and that also means that they have the
|
TWOFISH (and AES since 1.0.4) and that also means that they have the
|
||||||
capability to use the new MDC encryption method. This will go into
|
capability to use the new MDC encryption method. This will go into
|
||||||
OpenPGP soon and is also suppoted by PGP 7. This new method avoids
|
OpenPGP soon, and is also suppoted by PGP 7. This new method avoids
|
||||||
a (not so new) attack on all email encryption systems.
|
a (not so new) attack on all email encryption systems.
|
||||||
|
|
||||||
This in turn means that pre-1.0.3 gpg's have problems with newer
|
This in turn means that pre-1.0.3 gpg binaries have problems with
|
||||||
keys. Because of security fixes, you should keep your GnuPG
|
newer keys. Because of security and bug fixes, you should keep your
|
||||||
installation in a recent state anyway. As a workaround, you can
|
GnuPG installation in a recent state anyway. As a workaround, you can
|
||||||
force gpg to use a previous default cipher algo by putting:
|
force gpg to use a previous default cipher algo by putting:
|
||||||
|
|
||||||
[H pre]
|
[H pre]
|
||||||
@ -733,10 +826,10 @@ search in the mailing list archive.
|
|||||||
cipher Rijndael that is incorrectly being referred as "deprecated".
|
cipher Rijndael that is incorrectly being referred as "deprecated".
|
||||||
Ignore this warning, more recent versions of gpg are corrected.
|
Ignore this warning, more recent versions of gpg are corrected.
|
||||||
|
|
||||||
<Q> Some dates are displayed as ????-??-??, why?
|
<Q> Some dates are displayed as ????-??-??. Why?
|
||||||
|
|
||||||
Due to constraints in most libc implementations, dates beyond
|
Due to constraints in most libc implementations, dates beyond
|
||||||
2038-01-19 can't be displayed correctly. 64 bit OSes are not
|
2038-01-19 can't be displayed correctly. 64-bit OSes are not
|
||||||
affected by this problem. To avoid printing wrong dates, GnuPG
|
affected by this problem. To avoid printing wrong dates, GnuPG
|
||||||
instead prints some question marks. To see the correct value, you
|
instead prints some question marks. To see the correct value, you
|
||||||
can use the options --with-colons and --fixed-list-mode.
|
can use the options --with-colons and --fixed-list-mode.
|
||||||
@ -748,13 +841,13 @@ search in the mailing list archive.
|
|||||||
the list of reported bugs on the documentation page). If you're not
|
the list of reported bugs on the documentation page). If you're not
|
||||||
sure about it being a bug, you can send mail to the gnupg-devel
|
sure about it being a bug, you can send mail to the gnupg-devel
|
||||||
list. Otherwise, use the GUUG bug tracking system
|
list. Otherwise, use the GUUG bug tracking system
|
||||||
[H a href=http://bugs.guug.de/Reporting.html]http://bugs.guug.de/Reporting.html[H /a].
|
[H a href=http://bugs.guug.de/Reporting.html]<http://bugs.guug.de/Reporting.html>[H /a].
|
||||||
|
|
||||||
<Q> Why doesn't GnuPG support X509 certificates?
|
<Q> Why doesn't GnuPG support X.509 certificates?
|
||||||
|
|
||||||
GnuPG, first and foremost, is an implementation of the OpenPGP
|
GnuPG, first and foremost, is an implementation of the OpenPGP
|
||||||
standard (RFC 2440), which is a competing infrastructure, different
|
standard (RFC 2440), which is a competing infrastructure, different
|
||||||
from X509.
|
from X.509.
|
||||||
|
|
||||||
They are both public-key cryptosystems, but how the public keys are
|
They are both public-key cryptosystems, but how the public keys are
|
||||||
actually handled is different.
|
actually handled is different.
|
||||||
@ -789,6 +882,14 @@ search in the mailing list archive.
|
|||||||
http://www.gnupg.org/developer/gpg-woody-fix.txt
|
http://www.gnupg.org/developer/gpg-woody-fix.txt
|
||||||
[H /pre]
|
[H /pre]
|
||||||
|
|
||||||
|
<Q> I've upgraded to GnuPG version 1.0.7 and now it takes longer to load
|
||||||
|
my keyrings. What can I do?
|
||||||
|
|
||||||
|
The way signature states are stored has changed so that v3 signatures
|
||||||
|
can be supported. You can use the new --rebuild-keydb-caches migration
|
||||||
|
command, which was built into this release and increases the speed of
|
||||||
|
many operations for existing keyrings.
|
||||||
|
|
||||||
|
|
||||||
<S> ADVANCED TOPICS
|
<S> ADVANCED TOPICS
|
||||||
|
|
||||||
@ -811,7 +912,7 @@ search in the mailing list archive.
|
|||||||
having the secret key and putting in the password to use his secret
|
having the secret key and putting in the password to use his secret
|
||||||
key.
|
key.
|
||||||
|
|
||||||
GnuPG is also useful for signing things. Things that are encrypted
|
GnuPG is also useful for signing things. Files that are encrypted
|
||||||
with the secret key can be decrypted with the public key. To sign
|
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
|
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
|
form encoded with the secret key. If someone has your public key, they
|
||||||
@ -849,9 +950,9 @@ search in the mailing list archive.
|
|||||||
gpg --fingerprint user-id
|
gpg --fingerprint user-id
|
||||||
[H/pre]
|
[H/pre]
|
||||||
|
|
||||||
over the phone (if you really know the voice of the other person), at a
|
over the phone (if you really know the voice of the other person), at
|
||||||
key signing party (which are often held at computer conferences), or at
|
a key signing party (which are often held at computer conferences),
|
||||||
a meeting of your local GNU/Linux User Group.
|
or at a meeting of your local GNU/Linux User Group.
|
||||||
|
|
||||||
Hmm, what else. You may use the option "-o filename" to force output
|
Hmm, what else. You may use the option "-o filename" to force output
|
||||||
to this filename (use "-" to force output to stdout). "-r" just lets
|
to this filename (use "-" to force output to stdout). "-r" just lets
|
||||||
@ -920,7 +1021,7 @@ search in the mailing list archive.
|
|||||||
field is the assigned value:
|
field is the assigned value:
|
||||||
|
|
||||||
[H pre]
|
[H pre]
|
||||||
- = No Ownertrust value yet assigned.
|
- = No ownertrust value yet assigned or calculated.
|
||||||
n = Never trust this keyholder to correctly verify others signatures.
|
n = Never trust this keyholder to correctly verify others signatures.
|
||||||
m = Have marginal trust in the keyholders capability to sign other
|
m = Have marginal trust in the keyholders capability to sign other
|
||||||
keys.
|
keys.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user