security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2025-01-10 13:04:23 +01:00
Code Activity

* faq.raw: New upstream version with new sections 1.3, 5.8, 6.20

Browse Source 
and a list of MUAs.  Replaced ftp.guug.de URL.
This commit is contained in:
Werner Koch 2002-10-17 14:52:33 +00:00
parent 3ca93f344e
commit 575b4abda7
2 changed files with 302 additions and 196 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/ChangeLog
View File

@ -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>
* DETAILS (KEY_CREATED): Enhanced by fingerprint.

493
doc/faq.raw
View File

@ -14,8 +14,8 @@ The most recent version of the FAQ is available from
[H p]
Version: 1.5.7[H br]
Last-Modified: Aug 21, 2002[H br]
Version: 1.5.8[H br]
Last-Modified: Oct 8, 2002[H br]
Maintained-by: [$maintainer]
[H /p]
@ -23,17 +23,17 @@ Maintained-by: [$maintainer]
This is the GnuPG FAQ. The latest HTML version is available
[H a href=[$hGPG]/faq.html]here[H/a].
The index is generated automatically, so there may be errors here. Not
all questions may be in the section they belong to. Suggestions about
how to improve the structure of this FAQ are welcome.
The index is generated automatically, so there may be errors. Not all
questions may be in the section they belong to. Suggestions about how
to improve the structure of this FAQ are welcome.
Please send additions and corrections to the maintainer. It would be
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?".
If it hasn't been asked before, it isn't a FAQ. In that case you could
search in the mailing list archive.
Please, don't send message like "This should be a FAQ - what's the
answer?". If it hasn't been asked before, it isn't a FAQ. In that case
you could search in the mailing list archive.
[H HR]
<C>
@ -54,31 +54,40 @@ search in the mailing list archive.
<Q> Is GnuPG compatible with PGP?
In general, yes. GnuPG and newer PGP releases should be implementing
the OpenPGP standard. But there are some interoperability
problems. See question <Rcompat> for details.
the OpenPGP standard. But there are some interoperability problems.
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
<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 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
in English, Spanish and Russian). The latter provides a detailed user's
guide to GnuPG. You'll also find a document about how to convert from
PGP 2.x to GnuPG.
Also, have a look at the HOWTOs and the GNU Privacy Handbook (GPH,
available in English, Spanish and Russian). The latter provides a
detailed user's guide to GnuPG. You'll also find a document about
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
user-related issues and gnupg-devel if you want to get in touch with
the developers.
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-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-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]
[H B]PLEASE:[H/B]
Before posting to a list, read this FAQ and the available
@ -89,7 +98,7 @@ search in the mailing list archive.
[H LI]The GnuPG source distribution contains a subdirectory:
[H PRE]
./doc
./doc
[H /PRE]
where some additional documentation is located (mainly interesting
@ -99,28 +108,30 @@ search in the mailing list archive.
<Q> Where do I get GnuPG?
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]
<[$hGPG]/mirror.html>
<[$hGPG]/mirror.html>
[H /a]
The current version is 1.0.4, please upgrade to this version as it
fixes a security bug regarding the verification of multiple signatures.
The current stable version is 1.2.x. Please upgrade to this version as
it includes additional features, functions and security fixes that may
not have existed in prior versions.
<S> INSTALLATION
<Q> Which OSes does GnuPG run on?
It should run on most Unices as well as Windows 95 and Windows NT. A
list of OSes reported to be OK is presented at:
It should run on most Unices as well as Windows versions (including
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]
<http://www.gnupg.org/gnupg.html#supsys>
<http://www.gnupg.org/gnupg.html#supsys>
[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.
Different operating systems provide a variety of more or less quality
@ -130,50 +141,50 @@ search in the mailing list archive.
a /dev/random. In these cases, use the configure option:
[H pre]
--enable-static-rnd=linux
--enable-static-rnd=linux
[H/pre]
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!
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
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]
--enable-static-rnd=egd
--enable-static-rnd=egd
[H/pre]
here.
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.
<Didea>
<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
patent restriction. The patent does not expire before 2007 so don't
expect official support before then.
The official GnuPG distribution does not contain IDEA due to a patent
restriction. The patent does not expire before 2007 so don't expect
official support before then.
However, there is an unofficial module to include it even
in earlier versions of GnuPG. It's available from
However, there is an unofficial module to include it even in earlier
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 pre]
idea.c
idea.c
[H /pre]
Compilation directives are in the headers of these files. Then add
the following line to your ~/.gnupg/options:
Compilation directives are in the headers of these files. You will
then need to add the following line to your ~/.gnupg/options file:
[H pre]
load-extension idea
load-extension idea
[H /pre]
@ -181,20 +192,20 @@ search in the mailing list archive.
<Q> What is the recommended key size?
1024 bit for DSA signatures; even for plain ElGamal signatures
this is sufficient as the size of the hash is probably the weakest
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
this key:
[H pre]
gpg --fingerprint <user ID>
gpg --fingerprint <user ID>
[H /pre]
As for the key algorithms, you should stick with the default (i.e.,
DSA signature and ElGamal encryption). A 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
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
DSA, and there might be compatibility problems with certain PGP
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
advanced dictionary attacks) - I strongly encourage everyone to only
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:
We all do this) be sure to have a strong password for your account
and for your secret key and that you can trust your system
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 both your
account and for your secret key, and that you can trust your system
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
the keys, so I use a special option, --quick-random, to generate
insecure keys which are only good for some tests.
@ -243,62 +254,66 @@ search in the mailing list archive.
the filename comes at the very end. So the basic way to run gpg is:
[H pre]
gpg [--option something] [--option2] [--option3 something] --command file
gpg [--option something] [--option2] [--option3 something] --command file
[H/pre]
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,
otherwise gpg doesn't know which option the argument is supposed to
go with. As an option, --output and its filename must come before
the command. The --recipient (-r) option takes a name or keyid to
paired with. As an option, --output and its filename must come before
the command. The --recipient (-r) option takes a name or keyID to
encrypt the message to, which must come right after the -r argument.
The --encrypt (or -e) command comes after all the options followed
by the file you wish to encrypt. So use:
The --encrypt (or -e) command comes after all the options and is
followed by the file you wish to encrypt. Therefore in this example
the command-line issued would be:
[H pre]
gpg -r alice -o secret.txt -e test.txt
gpg -r alice -o secret.txt -e test.txt
[H/pre]
If you write the options out in full, it is easier to read:
[H pre]
gpg --recipient alice --output secret.txt --encrypt test.txt
gpg --recipient alice --output secret.txt --encrypt test.txt
[H/pre]
If you're saving it in a file called ".txt" then you'd probably
expect to see ASCII-armored text in there, so you need to add the
--armor (-a) option, which doesn't take any arguments:
If you're encrypting to a file with the extension ".txt", then you'd
probably expect to see ASCII-armored text in the file (not binary),
so you need to add the --armor (-a) option, which doesn't take any
arguments:
[H pre]
gpg --armor --recipient alice --output secret.txt --encrypt test.txt
gpg --armor --recipient alice --output secret.txt --encrypt test.txt
[H/pre]
If you imagine square brackets around the optional parts, it becomes
a bit clearer:
[H pre]
gpg [--armor] [--recipient alice] [--output secret.txt] --encrypt test.txt
gpg [--armor] [--recipient alice] [--output secret.txt] --encrypt test.txt
[H/pre]
The optional parts can be rearranged any way you want:
[H pre]
gpg --output secret.txt --recipient alice --armor --encrypt test.txt
gpg --output secret.txt --recipient alice --armor --encrypt test.txt
[H/pre]
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
to 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
same time. Use:
this is an option and may complain. To avoid this you have to either
use "./-a.txt", or stop the option and command processing with two
hyphens: "-- -a.txt".
[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]
gpg [--options] --sign --encrypt foo.txt
gpg [--options] --sign --encrypt foo.txt
[H/pre]
<Q> I can't delete a user ID because it is already deleted on my public
keyring?
<Q> I can't delete a user ID on my secret keyring because it has
already been deleted on my public keyring. What can I do?
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
@ -307,43 +322,46 @@ search in the mailing list archive.
ring. Now select this user ID and delete it. Both user IDs will be
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,
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
public key got lost but the secret key is still available. The
reality is different, so GnuPG implements a special way to deal
with it: Simply use the long keyid which can be obtained by using
the --with-colons options (it is the fifth field in the lines
beginning with "sec").
with it: Simply use the long keyID to specify the key to delete,
which can be obtained by using the --with-colons options (it is
the fifth field in the lines beginning with "sec").
<Q> What are trust, validity and ownertrust?
"ownertrust" is used instead of "trust" to make clear that this is
the value you have assigned to a key to express how much you trust
the owner of this key to correctly sign (and so introduce) other
keys. "validity", or calculated trust, is a value which says how
much GnuPG thinks a key is valid (that it really belongs to the one
who claims to be the owner of the key). For more see the chapter
"The Web of Trust" in the Manual.
With GnuPG, the term "ownertrust" is used instead of "trust" to
help clarify that this is the value you have assigned to a key
to express how much you trust the owner of this key to correctly
sign (and thereby introduce) other keys. The "validity", or
calculated trust, is a value which indicates how much GnuPG
considers a key as being valid (that it really belongs to the
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?
Use "gpg --clearsign --not-dash-escaped ...". The problem with
--clearsign is that all lines starting with a dash are quoted with
"- "; 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
patch file without removing the cleartext signature, the special
these are then quoted and that is not good for a patch ;-). To use
a patch file without removing the cleartext signature, the special
option --not-dash-escaped may be used to suppress generation of
these escape sequences. You should not mail such a patch because
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
simply sign it using your MUA.
simply sign it using your MUA (Mail User Agent).
<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,
you can use the option "--no-encrypt-to".
@ -355,59 +373,62 @@ search in the mailing list archive.
<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
that the displayed charset is the one you have activated on your
system. Since "iso-8859-1" is the charset most used, this is the
default. You can change the charset with the option "--charset".
It is important that your active character set matches the one
displayed - if not, restrict yourself to plain 7 bit ASCII and no
mapping has to be done.
This note is printed when UTF-8 mapping has to be done. Make sure
that the displayed character set is the one you have activated on
your system. Since "iso-8859-1" is the character set most used,
this is the default. You can change the charset with the option
"--charset". It is important that your active character set matches
the one displayed - if not, restrict yourself to plain 7 bit ASCII
and no mapping has to be done.
<Q> How can a get list of key IDs used to encrypt a message?
[H pre]
gpg --batch --decrypt --list-only --status-fd 1 2>/dev/null | \
awk '/^\[GNUPG:\] ENC_TO / { print $3 }'
gpg --batch --decrypt --list-only --status-fd 1 2>/dev/null | \
awk '/^\[GNUPG:\] ENC_TO / { print $3 }'
[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.
There used to be a bug in GnuPG < 1.0.1 which happens only if 3DES
or Twofish has been used for symmetric only encryption (this has
never been the default). The bug has been fixed but to enable you
to decrypt old messages, you should run gpg with the option
"--emulate-3des-s2k-bug", decrypt the message and encrypt it again
without this option. The option will be removed in 1.1, so better
re-encrypt your message now.
There was a bug in GnuPG versions prior to 1.0.1 which affected
messages only if 3DES or Twofish was used for symmetric-only
encryption (this has never been the default). The bug has been
fixed, but to enable decryption of old messages you should run gpg
with the option "--emulate-3des-s2k-bug", decrypt the message and
encrypt it again without this option. The option will be removed
in version 1.1 when released, so please re-encrypt any affected
messages now.
<Q> How can I use GnuPG in an automated environment?
You should use the option --batch and don't use pass phrases as
there is usually no way to store it more secure than the secret
keyring itself. The suggested way to create the keys for the
You should use the option --batch and don't use passphrases as
there is usually no way to store it more securely than on the
secret keyring itself. The suggested way to create keys for an
automated environment is:
On a secure machine:
[H OL]
[H LI] If you want to do automatic signing, create a signing
subkey for your key (edit menu, choose "addkey" and the DSA).
[H LI] If you want to do automatic signing, create a signing subkey
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
implementation).
[H LI] gpg --export-secret-subkeys --no-comment foo >secring.auto
[H LI] Copy secring.auto and the public keyring to a test directory.
[H LI] Change to this directory.
[H LI] gpg --homedir . --edit foo and use "passwd" to remove the
passphrase from the subkeys. You may also want to remove all
passphrase from the subkeys. You may also want to remove all
unused subkeys.
[H LI] Copy secring.auto to a floppy and carry it to the target box.
[H /OL]
On the target machine:
[H OL]
[H LI] Install secring.auto as secret keyring.
[H LI] Now you can start your new service. It is a good idea to
install some intrusion detection system so that you hopefully
[H LI] Install secring.auto as the secret keyring.
[H LI] Now you can start your new service. It's also a good idea to
install an intrusion detection system so that you hopefully
get a notice of an successful intrusion, so that you in turn
can revoke all the subkeys installed on that machine and
install new subkeys.
@ -416,26 +437,73 @@ search in the mailing list archive.
<Q> Which email-client can I use with GnuPG?
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
encrypted with GnuPG: the "old style" ASCII armor, i.e. plain text
encryption, and RFC2015 style (previously PGP/MIME, now OpenPGP).
encrypted with GnuPG: the "old style" ASCII armor (i.e. cleartext
encryption), and RFC 2015 style (previously PGP/MIME, now OpenPGP).
The latter has full MIME support. Some MUAs support only one of
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),
TkRat (Unix). There is effort for a Mozilla plugin and
Emacs/GNUS has support in the current CVS.
[H pre]
MUA OpenPGP ASCII How? (N,P,T)
---------------------------------------------------------------
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
probably many more.
N - Native, P - Plug-in, T - External Tool
[H /pre]
Good overviews of OpenPGP-support can be found at
[H a href=http://cryptorights.org/pgp-users/pgp-mail-clients.html]http://cryptorights.org/pgp-users/pgp-mail-clients.html[H /a]
and [H a href=http://www.geocities.com/openpgp/courrier_en.html]http://www.geocities.com/openpgp/courrier_en.html[H /a].
The following table lists proprietary MUAs. The GNU Project
suggests against the use of these programs, but they are listed
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?
@ -443,7 +511,7 @@ search in the mailing list archive.
of the GnuPG maintainers is that this would lead to several security
issues and will therefore not be implemented in the foreseeable
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
understand how to send it to the key servers.
@ -452,13 +520,13 @@ search in the mailing list archive.
have to import the certificate into gpg first:
[H pre]
gpg --import my-revocation.asc
gpg --import my-revocation.asc
[H /pre]
then send the revoked key to the keyservers:
[H pre]
gpg --keyserver certserver.pgp.com --send-keys mykeyid
gpg --keyserver certserver.pgp.com --send-keys mykeyid
[H /pre]
(or use a keyserver web interface for this).
@ -473,7 +541,7 @@ search in the mailing list archive.
If you want to put your keyrings somewhere else, use:
[H pre]
--homedir /my/path/
--homedir /my/path/
[H /pre]
to make GnuPG create all its files in that directory. Your keyring
@ -496,7 +564,7 @@ search in the mailing list archive.
modified version of PGP you can try this:
[H pre]
gpg --rfc1991 --cipher-algo 3des ...
gpg --rfc1991 --cipher-algo 3des ...
[H/pre]
Please don't pipe the data to encrypt to gpg but provide it using a
@ -508,14 +576,14 @@ search in the mailing list archive.
You need to provide two additional options:
[H pre]
--compress-algo 1 --cipher-algo cast5
--compress-algo 1 --cipher-algo cast5
[H/pre]
You may also use "3des" instead of "cast5", and "blowfish" does not
work with all versions of PGP 5. You may also want to put:
[H pre]
compress-algo 1
compress-algo 1
[H/pre]
into your ~/.gnupg/options file - this does not affect normal GnuPG
@ -531,7 +599,7 @@ search in the mailing list archive.
algorithm is still patented until 2007. Under certain conditions you
may use IDEA even today. In that case, you may refer to Question
<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)
@ -560,7 +628,7 @@ search in the mailing list archive.
imported the PGP keyring you can give this command:
[H pre]
$ lspgpot pgpkeyring | gpg --import-ownertrust
$ lspgpot pgpkeyring | gpg --import-ownertrust
[H /pre]
where pgpkeyring is the original keyring and not the GnuPG keyring
@ -574,7 +642,7 @@ search in the mailing list archive.
secret keys with this command:
[H pre]
$ gpg --export-secret-keys --no-comment -a your-key-id
$ gpg --export-secret-keys --no-comment -a your-key-id
[H /pre]
Another possibility is this: by default, GnuPG encrypts your secret
@ -584,8 +652,8 @@ search in the mailing list archive.
different algo:
[H pre]
$ gpg --s2k-cipher-algo=CAST5 --s2k-digest-algo=SHA1 \
--compress-algo=1 --edit-key <username>
$ gpg --s2k-cipher-algo=CAST5 --s2k-digest-algo=SHA1 \
--compress-algo=1 --edit-key <username>
[H /pre]
Then use passwd to change the password (just change it to the same
@ -596,10 +664,18 @@ search in the mailing list archive.
For PGP 6.x the following options work to export a key:
[H pre]
$ gpg --s2k-cipher-algo 3des --compress-algo 1 --rfc1991 \
--export-secret-keys <key-ID>
$ gpg --s2k-cipher-algo 3des --compress-algo 1 --rfc1991 \
--export-secret-keys <key-ID>
[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
@ -612,18 +688,34 @@ search in the mailing list archive.
memory your operating system supports locking without being root. The
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'
privilege to get the same effect:
[H pre]
filepriv -f plock /path/to/gpg
filepriv -f plock /path/to/gpg
[H /pre]
If you can't or don't want to install GnuPG setuid(root), you can
use the option "--no-secmem-warning" or put:
[H pre]
no-secmem-warning
no-secmem-warning
[H /pre]
in your ~/.gnupg/options file (this disables the warning).
@ -632,7 +724,7 @@ search in the mailing list archive.
and older GnuPG versions (<=1.0.4) issue the warning:
[H pre]
gpg: Please note that you don't have secure memory
gpg: Please note that you don't have secure memory
[H /pre]
This warning can't be switched off by the above option because it
@ -641,14 +733,14 @@ search in the mailing list archive.
<Q> Large File Support doesn't work ...
LFS is correctly working in post-1.0.4 CVS. If configure doesn't
detect it correctly, try a different (i.e., better) compiler. egcs
1.1.2 works fine, other gccs sometimes don't. BTW, several
compilation problems of GnuPG 1.0.3 and 1.0.4 on HP-UX and Solaris
were due to broken LFS support.
LFS works correctly in post-1.0.4 versions. If configure doesn't
detect it, try a different (i.e., better) compiler. egcs 1.1.2 works
fine, other gccs sometimes don't. BTW, several compilation problems
of GnuPG 1.0.3 and 1.0.4 on HP-UX and Solaris were due to broken LFS
support.
<Q> In the edit menu the trust values is not displayed correctly after
signing uids - why?
<Q> In the edit menu the trust values are not displayed correctly after
signing uids. Why?
This happens because some information is stored immediately in
the trustdb, but the actual trust calculation can be done after the
@ -704,24 +796,25 @@ search in the mailing list archive.
<Q> I get "gpg: waiting for lock ..."
A previous gpg has most likely exited abnormally and left a lock
file. Go to ~/.gnupg and look for .*.lock files and remove them.
A previous instance of gpg has most likely exited abnormally and left
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
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
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.
This in turn means that pre-1.0.3 gpg's have problems with newer
keys. Because of security fixes, you should keep your GnuPG
installation in a recent state anyway. As a workaround, you can
This in turn means that pre-1.0.3 gpg binaries have problems with
newer keys. Because of security and bug fixes, you should keep your
GnuPG installation in a recent state anyway. As a workaround, you can
force gpg to use a previous default cipher algo by putting:
[H pre]
cipher-algo cast5
cipher-algo cast5
[H /pre]
into your options file.
@ -733,10 +826,10 @@ search in the mailing list archive.
cipher Rijndael that is incorrectly being referred as "deprecated".
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
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
instead prints some question marks. To see the correct value, you
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
sure about it being a bug, you can send mail to the gnupg-devel
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
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
actually handled is different.
@ -775,7 +868,7 @@ search in the mailing list archive.
and place a:
[H pre]
unset CDPATH
unset CDPATH
[H /pre]
statement below it.
@ -786,9 +879,17 @@ search in the mailing list archive.
correctly. You may want to apply this patch if you can't upgrade:
[H pre]
http://www.gnupg.org/developer/gpg-woody-fix.txt
http://www.gnupg.org/developer/gpg-woody-fix.txt
[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
@ -797,7 +898,7 @@ search in the mailing list archive.
To generate a secret/public keypair, run:
[H pre]
gpg --gen-key
gpg --gen-key
[H/pre]
and choose the default values.
@ -811,7 +912,7 @@ search in the mailing list archive.
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
GnuPG is also useful for signing things. Files 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
@ -846,12 +947,12 @@ search in the mailing list archive.
that person: You should verify the key fingerprint with:
[H pre]
gpg --fingerprint user-id
gpg --fingerprint user-id
[H/pre]
over the phone (if you really know the voice of the other person), at a
key signing party (which are often held at computer conferences), or at
a meeting of your local GNU/Linux User Group.
over the phone (if you really know the voice of the other person), at
a key signing party (which are often held at computer conferences),
or at a meeting of your local GNU/Linux User Group.
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
@ -889,23 +990,23 @@ search in the mailing list archive.
command.
[H pre]
gpg --list-keys --with-colons
gpg --list-keys --with-colons
[H/pre]
If the first field is "pub" or "uid", the second field shows you the
trust:
[H pre]
o = Unknown (this key is new to the system)
e = The key has expired
q = Undefined (no value assigned)
n = Don't trust this key at all
m = There is marginal trust in this key
f = The key is full trusted
u = The key is ultimately trusted; this is only used
for keys for which the secret key is also available.
r = The key has been revoked
d = The key has been disabled
o = Unknown (this key is new to the system)
e = The key has expired
q = Undefined (no value assigned)
n = Don't trust this key at all
m = There is marginal trust in this key
f = The key is full trusted
u = The key is ultimately trusted; this is only used
for keys for which the secret key is also available.
r = The key has been revoked
d = The key has been disabled
[H/pre]
The value in the "pub" record is the best one of all "uid" records.
@ -913,19 +1014,19 @@ search in the mailing list archive.
the owner to correctly sign another person's key) with:
[H pre]
gpg --list-ownertrust
gpg --list-ownertrust
[H/pre]
The first field is the fingerprint of the primary key, the second
field is the assigned value:
[H pre]
- = No Ownertrust value yet assigned.
n = Never trust this keyholder to correctly verify others signatures.
m = Have marginal trust in the keyholders capability to sign other
keys.
f = Assume that the key holder really knows how to sign keys.
u = No need to trust ourself because we have the secret key.
- = No ownertrust value yet assigned or calculated.
n = Never trust this keyholder to correctly verify others signatures.
m = Have marginal trust in the keyholders capability to sign other
keys.
f = Assume that the key holder really knows how to sign keys.
u = No need to trust ourself because we have the secret key.
[H/pre]
Keep these values confidential because they express your opinions
@ -948,7 +1049,7 @@ search in the mailing list archive.
item.
[H pre]
"key 12345678.3456"
"key 12345678.3456"
[H/pre]
This is about the key with key ID 12345678 and the internal number
@ -956,14 +1057,14 @@ search in the mailing list archive.
in the trustdb.
[H pre]
"uid 12345678.3456/ACDE"
"uid 12345678.3456/ACDE"
[H/pre]
This is about the user ID for the same key. To identify the user ID
the last two bytes of a ripe-md-160 over the user ID ring is printed.
[H pre]
"sig 12345678.3456/ACDE/9A8B7C6D"
"sig 12345678.3456/ACDE/9A8B7C6D"
[H/pre]
This is about the signature with key ID 9A8B7C6D for the above key