gnupg (TODO doc/ChangeLog doc/faq.raw g10/ChangeLog
g10/ccid-driver.c)
cvs user wk
cvs at cvs.gnupg.org
Thu Jan 27 11:21:54 CET 2005
Date: Thursday, January 27, 2005 @ 11:30:28
Author: wk
Path: /cvs/gnupg/gnupg
Modified: TODO doc/ChangeLog doc/faq.raw g10/ChangeLog g10/ccid-driver.c
Updated to the version from 1.2.7.
-------------------+
TODO | 5
doc/ChangeLog | 4
doc/faq.raw | 993 ++++++++++++++++++++++++++++++++++------------------
g10/ChangeLog | 8
g10/ccid-driver.c | 4
5 files changed, 676 insertions(+), 338 deletions(-)
Index: gnupg/TODO
diff -u gnupg/TODO:1.175 gnupg/TODO:1.176
--- gnupg/TODO:1.175 Fri Oct 15 18:08:15 2004
+++ gnupg/TODO Thu Jan 27 11:30:28 2005
@@ -1,3 +1,8 @@
+* BACKUP Filename requires a status message. !!!!
+
+* Delete a card key as well as a wiping.
+
+
* From: Nicolas Sierro
Date: Thu, 17 Jun 2004 12:31:24 +0200
Index: gnupg/doc/ChangeLog
diff -u gnupg/doc/ChangeLog:1.91 gnupg/doc/ChangeLog:1.92
--- gnupg/doc/ChangeLog:1.91 Thu Jan 20 12:42:03 2005
+++ gnupg/doc/ChangeLog Thu Jan 27 11:30:27 2005
@@ -1,3 +1,7 @@
+2005-01-27 Werner Koch <wk at g10code.com>
+
+ * faq.raw: Updated to the version from 1.2.7.
+
2005-01-18 Werner Koch <wk at g10code.com>
* gnupg-w32.reg: Remove the entry for the home directory.
Index: gnupg/doc/faq.raw
diff -u gnupg/doc/faq.raw:1.3 gnupg/doc/faq.raw:1.4
--- gnupg/doc/faq.raw:1.3 Fri Aug 23 10:43:46 2002
+++ gnupg/doc/faq.raw Thu Jan 27 11:30:27 2005
@@ -7,120 +7,159 @@
[$usenetheader=
]
[$maintainer=David D. Scribner, <faq 'at' gnupg.org>]
-[$hGPG=http://www.gnupg.org]
+[$hGPGHTTP=http://www.gnupg.org]
+[$hGPGFTP=ftp://ftp.gnupg.org]
+[$hVERSION=1.2.2]
[H body bgcolor=#ffffff text=#000000 link=#1f00ff alink=#ff0000 vlink=#9900dd]
-[H H1]GnuPG Frequently Asked Questions[H /H1]
+[H h1]GnuPG Frequently Asked Questions[H /h1]
[H p]
-Version: 1.5.7[H br]
-Last-Modified: Aug 21, 2002[H br]
+Version: 1.6.3[H br]
+Last-Modified: Jul 30, 2003[H br]
Maintained-by: [$maintainer]
[H /p]
This is the GnuPG FAQ. The latest HTML version is available
-[H a href=[$hGPG]/faq.html]here[H/a].
+[H a href=[$hGPGHTTP]/documentation/faqs.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]
+[H hr]
<C>
-[H HR]
+[H hr]
<S> GENERAL
<Q> What is GnuPG?
- [H a href=[$hGPG]]GnuPG[H /a] stands for GNU Privacy Guard and
+ [H a href=[$hGPGHTTP]]GnuPG[H /a] stands for GNU Privacy Guard and
is GNU's tool for secure communication and data storage. It can be
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.gnupg.org/rfc2440.html]RFC 2440[H/a].
+ 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.
<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.
+
+<Q> What conventions are used in this FAQ?
+
+ Although GnuPG is being developed for several operating systems
+ (often in parallel), the conventions used in this FAQ reflect a
+ UNIX shell environment. For Win32 users, references to a shell
+ prompt (`$') should be interpreted as a command prompt (`>'),
+ directory names separated by a forward slash (`/') may need to be
+ converted to a back slash (`\'), and a tilde (`~') represents a
+ user's "home" directory (reference question <Rhomedir> for an example).
+
+ Some command-lines presented in this FAQ are too long to properly
+ display in some browsers for the web page version of this file, and
+ have been split into two or more lines. For these commands please
+ remember to enter the entire command-string on one line or the
+ command will error, or at minimum not give the desired results.
+
+ Please keep in mind that this FAQ contains information that may not
+ apply to your particular version, as new features and bug fixes are
+ added on a continuing basis (reference the NEWS file included with
+ the source or package for noteworthy changes between versions). One
+ item to note is that starting with GnuPG version 1.1.92 the file
+ containing user options and settings has been renamed from "options"
+ to "gpg.conf". Information in the FAQ that relates to the options
+ file may be interchangable with the newer gpg.conf file in many
+ instances. See question <Roptions> for details.
<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.
-
- [H LI]On [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.
+ [H ul]
+ [H li]The documentation page is located at [H a href=[$hGPGHTTP]/documentation/]<[$hGPGHTTP]/documentation/>[H/a].
+ 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]At [H a href=[$hGPGHTTP]/documentation/mailing-lists.html]<[$hGPGHTTP]/documentation/mailing-lists.html>[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
- documentation. In addition, search the list archive - maybe your
- question has already been discussed. This way you help people focus
- on topics that have not yet been resolved.
-
- [H LI]The GnuPG source distribution contains a subdirectory:
-
- [H PRE]
- ./doc
- [H /PRE]
+ [H b]PLEASE:[H /b]
+ Before posting to a list, read this FAQ and the available documentation.
+ In addition, search the list archive - maybe your question has already
+ been discussed. This way you help people focus on topics that have not
+ yet been resolved.
+
+ [H li]The GnuPG source distribution contains a subdirectory:
+
+ [H samp]
+ ./doc
+ [H /samp]
where some additional documentation is located (mainly interesting
for hackers, not the casual user).
- [H /UL]
+ [H /ul]
<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=[$hGPGFTP]/gcrypt/]<[$hGPGFTP]/gcrypt/>[H /a] or from one of the mirrors:
- [H a href=[$hGPG]/mirrors.html]
- <[$hGPG]/mirror.html>
+ [H a href=[$hGPGHTTP]/download/mirrors.html]
+ <[$hGPGHTTP]/download/mirrors.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 [$hVERSION]. 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>
+ [H a href=[$hGPGHTTP]/download/supported_systems.html]
+ <[$hGPGHTTP]/download/supported_systems.html>
[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
@@ -129,72 +168,79 @@
systems. Also Solaris users with the SUNWski package installed have
a /dev/random. In these cases, use the configure option:
- [H pre]
- --enable-static-rnd=linux
- [H/pre]
+ [H samp]
+ --enable-static-rnd=linux
+ [H /samp]
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/SUNrand/]<http://www.cosy.sbg.ac.at/~andi/SUNrand/>[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:
+ random data. See the download page [H a href=[$hGPGHTTP]/download/]<[$hGPGHTTP]/download/>[H /a]
+ to obtain EGD. Use:
- [H pre]
- --enable-static-rnd=egd
- [H/pre]
+ [H samp]
+ --enable-static-rnd=egd
+ [H /samp]
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.
-
- 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:
+ 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
+ [H a href=ftp://ftp.gnupg.dk/pub/contrib-dk/]<ftp://ftp.gnupg.dk/pub/contrib-dk/>[H /a]. Look for:
[H pre]
- idea.c
+ idea.c.gz (c module)
+ idea.c.gz.sig (signature file)
[H /pre]
- Compilation directives are in the headers of these files. Then add
- the following line to your ~/.gnupg/options:
-
[H pre]
- load-extension idea
+ ideadll.zip (c module and win32 dll)
+ ideadll.zip.sig (signature file)
[H /pre]
+ Compilation directives are in the headers of these files. You will
+ then need to add the following line to your ~/.gnupg/gpg.conf or
+ ~/.gnupg/options file:
+
+ [H samp]
+ load-extension idea
+ [H /samp]
+
<S> USAGE
<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>
- [H /pre]
+ [H samp]
+ $ gpg --fingerprint <user ID>
+ [H /samp]
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 +268,12 @@
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.
@@ -236,69 +282,73 @@
If you do a 'gpg --help', you will get two separate lists. The first
is a list of commands. The second is a list of options. Whenever you
- run GPG, you [H B]must[H /B] pick exactly one command (with one exception,
- see below). You [H B]may[H /B] pick one or more options. The command should,
+ run GPG, you [H b]must[H /b] pick exactly one command (with one exception,
+ see below). You [H b]may[H /b] pick one or more options. The command should,
just by convention, come at the end of the argument list, after all
the options. If the command takes a file (all the basic ones do),
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
- [H/pre]
+ [H samp]
+ $ gpg [--option something] [--option2] [--option3 something] --command file
+ [H /samp]
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
- 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:
-
- [H pre]
- gpg -r alice -o secret.txt -e test.txt
- [H/pre]
+ 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 option.
+ 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 samp]
+ $ gpg -r alice -o secret.txt -e test.txt
+ [H /samp]
If you write the options out in full, it is easier to read:
- [H pre]
- 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:
-
- [H pre]
- gpg --armor --recipient alice --output secret.txt --encrypt test.txt
- [H/pre]
+ [H samp]
+ $ gpg --recipient alice --output secret.txt --encrypt test.txt
+ [H /samp]
+
+ 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 samp]
+ $ gpg --armor --recipient alice --output secret.txt --encrypt test.txt
+ [H /samp]
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
- [H/pre]
+ [H samp]
+ $ gpg [--armor] [--recipient alice] [--output secret.txt] --encrypt test.txt
+ [H /samp]
The optional parts can be rearranged any way you want:
- [H pre]
- gpg --output secret.txt --recipient alice --armor --encrypt test.txt
- [H/pre]
+ [H samp]
+ $ gpg --output secret.txt --recipient alice --armor --encrypt test.txt
+ [H /samp]
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:
-
- [H pre]
- gpg [--options] --sign --encrypt foo.txt
- [H/pre]
+ 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 samp]
+ $ gpg [--options] --sign --encrypt foo.txt
+ [H /samp]
-<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 +357,50 @@
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
- having the public key. Normally it shoud never happen that the
+ therefore it is not possible to select a secret key without
+ having the public key. Normally it should 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").
+
+ If you've lost your public key and need to recreate it instead
+ for continued use with your secret key, you may be able to use
+ gpgsplit as detailed in question <Rgpgsplit>.
<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,87 +412,142 @@
<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.
-
-<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 }'
- [H /pre]
-
-<Q> I can't decrypt my symmetrical only (-c) encrypted message 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.
+ 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 I get list of key IDs used to encrypt a message?
+
+ [H samp]
+ $ gpg --batch --decrypt --list-only --status-fd 1 2>/dev/null |
+ awk '/^\[GNUPG:\] ENC_TO / { print $3 }'
+ [H /samp]
+
+<Q> Why can't I decrypt files encrypted as symmetrical-only (-c) with
+ a version of GnuPG prior to 1.0.1.
+
+ There was a bug in GnuPG versions prior to 1.0.1 which affected files
+ 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 files you should run gpg with the option "--emulate-3des-s2k-bug",
+ decrypt the file and encrypt it again without this option.
+
+ NOTE: This option was removed in GnuPG development version 1.1.0 and later
+ updates, so you will need to use a version between 1.0.1 and 1.0.7 to
+ re-encrypt any affected files.
<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] Make sure that you use a passphrase (needed by the current
+ [H ol]
+ [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
+ [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
unused subkeys.
- [H LI] Copy secring.auto to a floppy and carry it to the target box.
- [H /OL]
+ [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 ol]
+ [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.
- [H /OL]
+ [H /ol]
<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
+
+ N - Native, P - Plug-in, T - External Tool
+ [H /pre]
- ASCII: Emacs/{VM,GNUS}/MailCrypt, Mutt(Unix), Pine(Unix), and
- probably many more.
+ 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 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].
+ Good overviews of OpenPGP-support can be found at:[H br]
+ [H a href=http://www.openpgp.fr.st/courrier_en.html]<http://www.openpgp.fr.st/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].
+
+ Users of Win32 MUAs that lack OpenPGP support may look into
+ using GPGrelay [H a href=http://gpgrelay.sourceforge.net]<http://gpgrelay.sourceforge.net>[H /a], a small
+ email-relaying server that uses GnuPG to enable many email clients
+ to send and receive emails that conform to PGP-MIME (RFC 2015).
<Q> Can't we have a gpg library?
@@ -443,7 +555,7 @@
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=[$hGPGFTP]/gcrypt/alpha/gpgme]<[$hGPGFTP]/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.
@@ -451,18 +563,19 @@
Most keyservers don't accept a 'bare' revocation certificate. You
have to import the certificate into gpg first:
- [H pre]
- gpg --import my-revocation.asc
- [H /pre]
+ [H samp]
+ $ gpg --import my-revocation.asc
+ [H /samp]
then send the revoked key to the keyservers:
- [H pre]
- gpg --keyserver certserver.pgp.com --send-keys mykeyid
- [H /pre]
+ [H samp]
+ $ gpg --keyserver certserver.pgp.com --send-keys mykeyid
+ [H /samp]
(or use a keyserver web interface for this).
+<Dhomedir>
<Q> How do I put my keyring in a different directory?
GnuPG keeps several files in a special homedir directory. These
@@ -470,17 +583,87 @@
and others. GnuPG will always create and use these files. On unices,
the homedir is usually ~/.gnupg; on Windows "C:\gnupg\".
- If you want to put your keyrings somewhere else, use:
+ If you want to put your keyrings somewhere else, use the option:
- [H pre]
- --homedir /my/path/
- [H /pre]
+ [H samp]
+ --homedir /my/path/
+ [H /samp]
to make GnuPG create all its files in that directory. Your keyring
will be "/my/path/pubring.gpg". This way you can store your secrets
on a floppy disk. Don't use "--keyring" as its purpose is to specify
additional keyring files.
+<Q> How do I verify signed packages?
+
+ Before you can verify the signature that accompanies a package,
+ you must first have the vendor, organisation, or issueing person's
+ key imported into your public keyring. To prevent GnuPG warning
+ messages the key should also be validated (or locally signed).
+
+ You will also need to download the detached signature file along
+ with the package. These files will usually have the same name as
+ the package, with either a binary (.sig) or ASCII armor (.asc)
+ extension.
+
+ Once their key has been imported, and the package and accompanying
+ signature files have been downloaded, use:
+
+ [H samp]
+ $ gpg --verify sigfile signed-file
+ [H /samp]
+
+ If the signature file has the same base name as the package file,
+ the package can also be verified by specifying just the signature
+ file, as GnuPG will derive the package's file name from the name
+ given (less the .sig or .asc extension). For example, to verify a
+ package named foobar.tar.gz against its detached binary signature
+ file, use:
+
+ [H samp]
+ $ gpg --verify foobar.tar.gz.sig
+ [H /samp]
+
+<Q> How do I export a keyring with only selected signatures (keys)?
+
+ If you're wanting to create a keyring with only a subset of keys
+ selected from a master keyring (for a club, user group, or company
+ department for example), simply specify the keys you want to export:
+
+ [H samp]
+ $ gpg --armor --export key1 key2 key3 key4 > keys1-4.asc
+ [H /samp]
+
+<Dgpgsplit>
+<Q> I still have my secret key, but lost my public key. What can I do?
+
+ All OpenPGP secret keys have a copy of the public key inside them,
+ and in a worst-case scenario, you can create yourself a new public
+ key using the secret key.
+
+ A tool to convert a secret key into a public one has been included
+ (it's actually a new option for gpgsplit) and is available with GnuPG
+ versions 1.2.1 or later (or can be found in CVS). It works like this:
+
+ [H samp]
+ $ gpgsplit --no-split --secret-to-public secret.gpg >publickey.gpg
+ [H /samp]
+
+ One should first try to export the secret key and convert just this
+ one. Using the entire secret keyring should work too. After this has
+ been done, the publickey.gpg file can be imported into GnuPG as usual.
+
+<Q> Clearsigned messages sent from my web-mail account have an invalid
+ signature. Why?
+
+ Check to make sure the settings for your web-based email account
+ do not use HTML formatting for the pasted clearsigned message. This can
+ alter the message with embedded HTML markup tags or spaces, resulting
+ in an invalid signature. The recipient may be able to copy the signed
+ message block to a text file for verification, or the web email
+ service may allow you to attach the clearsigned message as a file
+ if plaintext messages are not an option.
+
<S> COMPATIBILITY ISSUES
@@ -489,34 +672,34 @@
It depends on the PGP version.
- [H UL]
- [H LI]PGP 2.x[H br]
+ [H ul]
+ [H li]PGP 2.x[H br]
You can't do that because PGP 2.x normally uses IDEA which is not
supported by GnuPG as it is patented (see <Ridea>), but if you have a
modified version of PGP you can try this:
- [H pre]
- gpg --rfc1991 --cipher-algo 3des ...
- [H/pre]
+ [H samp]
+ $ gpg --rfc1991 --cipher-algo 3des ...
+ [H /samp]
Please don't pipe the data to encrypt to gpg but provide it using a
filename; otherwise, PGP 2 will not be able to handle it.
As for conventional encryption, you can't do this for PGP 2.
- [H LI]PGP 5.x and higher[H br]
+ [H li]PGP 5.x and higher[H br]
You need to provide two additional options:
- [H pre]
- --compress-algo 1 --cipher-algo cast5
- [H/pre]
+ [H samp]
+ --compress-algo 1 --cipher-algo cast5
+ [H /samp]
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
- [H/pre]
+ [H samp]
+ compress-algo 1
+ [H /samp]
into your ~/.gnupg/options file - this does not affect normal GnuPG
operation.
@@ -531,7 +714,7 @@
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=[$hGPGHTTP]/gph/en/pgp2x.html]<[$hGPGHTTP]/gph/en/pgp2x.html>[H /a] to perform the migration.
<Q> (removed)
@@ -559,9 +742,9 @@
There is a script in the tools directory to help you. After you have
imported the PGP keyring you can give this command:
- [H pre]
- $ lspgpot pgpkeyring | gpg --import-ownertrust
- [H /pre]
+ [H samp]
+ $ lspgpot pgpkeyring | gpg --import-ownertrust
+ [H /samp]
where pgpkeyring is the original keyring and not the GnuPG keyring
you might have created in the first step.
@@ -573,9 +756,9 @@
PGP is not really OpenPGP aware. A workaround is to export the
secret keys with this command:
- [H pre]
- $ gpg --export-secret-keys --no-comment -a your-key-id
- [H /pre]
+ [H samp]
+ $ gpg --export-secret-keys --no-comment -a your-KeyID
+ [H /samp]
Another possibility is this: by default, GnuPG encrypts your secret
key using the Blowfish symmetric algorithm. Older PGPs will only
@@ -583,10 +766,10 @@
following method you can re-encrypt your secret gpg key with a
different algo:
- [H pre]
- $ gpg --s2k-cipher-algo=CAST5 --s2k-digest-algo=SHA1 \
- --compress-algo=1 --edit-key <username>
- [H /pre]
+ [H samp]
+ $ gpg --s2k-cipher-algo=CAST5 --s2k-digest-algo=SHA1
+ --compress-algo=1 --edit-key <username>
+ [H /samp]
Then use passwd to change the password (just change it to the same
thing, but it will encrypt the key with CAST5 this time).
@@ -595,10 +778,86 @@
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>
- [H /pre]
+ [H samp]
+ $ gpg --s2k-cipher-algo 3des --compress-algo 1 --rfc1991
+ --export-secret-keys <KeyID>
+ [H /samp]
+
+<Doptions>
+<Q> GnuPG no longer installs a ~/.gnupg/options file. Is it missing?
+
+ No. The ~/.gnupg/options file has been renamed to ~/.gnupg/gpg.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.
+ An existing options file can be renamed to gpg.conf for users upgrading,
+ or receiving the message that the "old default options file" is ignored
+ (occurs if both a gpg.conf and an options file are found).
+
+<Q> How do you export GnuPG keys for use with PGP?
+
+ This has come up fairly often, so here's the HOWTO:
+
+ PGP can (for most key types) use secret keys generated by GnuPG. The
+ problems that come up occasionally are generally because GnuPG
+ 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
+ usable with any version.
+
+ These instructions should work for GnuPG 1.0.7 and later, and PGP
+ 7.0.3 and later.
+
+ Start by editing the key. Most of this line is not really necessary
+ as the default values are correct, but it does not hurt to repeat the
+ values, as this will override them in case you have something else set
+ in your options file.
+
+ [H samp]
+ $ gpg --s2k-cipher-algo cast5 --s2k-digest-algo sha1 --s2k-mode 3
+ --simple-sk-checksum --edit KeyID
+ [H /samp]
+
+ Turn off some features. Set the list of preferred ciphers, hashes,
+ and compression algorithms to things that PGP can handle. (Yes, I
+ know this is an odd list of ciphers, but this is what PGP itself uses,
+ minus IDEA).
+
+ [H samp]
+ > setpref S9 S8 S7 S3 S2 S10 H2 H3 Z1 Z0
+ [H /samp]
+
+ Now put the list of preferences onto the key.
+
+ [H samp]
+ > updpref
+ [H /samp]
+
+ Finally we must decrypt and re-encrypt the key, making sure that we
+ encrypt with a cipher that PGP likes. We set this up in the --edit
+ line above, so now we just need to change the passphrase to make it
+ take effect. You can use the same passphrase if you like, or take
+ this opportunity to actually change it.
+
+ [H samp]
+ > passwd
+ [H /samp]
+
+ Save our work.
+
+ [H samp]
+ > save
+ [H /samp]
+
+ Now we can do the usual export:
+
+ [H samp]
+ $ gpg --export KeyID > mypublickey.pgp[H br]
+ $ gpg --export-secret-key KeyID > mysecretkey.pgp
+ [H /samp]
+
+ Thanks to David Shaw for this information!
<S> PROBLEMS and ERROR MESSAGES
@@ -612,28 +871,45 @@
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 samp]
+ $ chmod u+s /path/to/gpg
+ [H /samp]
+
+ or
+
+ [H samp]
+ $ chmod 4755 /path/to/gpg
+ [H /samp]
+
+ 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
- [H /pre]
+ [H samp]
+ $ filepriv -f plock /path/to/gpg
+ [H /samp]
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
- [H /pre]
+ [H samp]
+ no-secmem-warning
+ [H /samp]
- in your ~/.gnupg/options file (this disables the warning).
+ in your ~/.gnupg/options or ~/.gnupg/gpg.conf file (this disables
+ the warning).
On some systems (e.g., Windows) GnuPG does not lock memory pages
and older GnuPG versions (<=1.0.4) issue the warning:
- [H pre]
- gpg: Please note that you don't have secure memory
- [H /pre]
+ [H samp]
+ gpg: Please note that you don't have secure memory
+ [H /samp]
This warning can't be switched off by the above option because it
was thought to be too serious an issue. However, it confused users
@@ -641,14 +917,14 @@
<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,25 +980,26 @@
<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
- [H /pre]
+ [H samp]
+ cipher-algo cast5
+ [H /samp]
into your options file.
@@ -733,10 +1010,10 @@
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 +1025,13 @@
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.
@@ -772,11 +1049,11 @@
This will be fixed after GnuPG has been upgraded to autoconf-2.50.
Until then, find the line setting CDPATH in the configure script
- and place a:
+ and place an:
- [H pre]
- unset CDPATH
- [H /pre]
+ [H samp]
+ unset CDPATH
+ [H /samp]
statement below it.
@@ -785,9 +1062,55 @@
There is a small bug in 1.0.6 which didn't parse trust packets
correctly. You may want to apply this patch if you can't upgrade:
- [H pre]
- http://www.gnupg.org/developer/gpg-woody-fix.txt
- [H /pre]
+ [H a href=http://www.gnupg.org/developer/gpg-woody-fix.txt]<http://www.gnupg.org/developer/gpg-woody-fix.txt>[H /a]
+
+<Q> I 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.
+
+<Q> Doesn't a fully trusted user ID on a key prevent warning messages
+ when encrypting to other IDs on the key?
+
+ No. That was actually a key validity bug in GnuPG 1.2.1 and earlier
+ versions. As part of the development of GnuPG 1.2.2, a bug was
+ discovered in the key validation code. This bug causes keys with
+ more than one user ID to give all user IDs on the key the amount of
+ validity given to the most-valid key. The bug has been fixed in GnuPG
+ release 1.2.2, and upgrading is the recommended fix for this problem.
+ More information and a patch for a some pre-1.2.2 versions of GnuPG
+ can be found at:
+
+ [H a href=http://lists.gnupg.org/pipermail/gnupg-announce/2003q2/000268.html]<http://lists.gnupg.org/pipermail/gnupg-announce/2003q2/000268.html>[H /a]
+
+<Q> I just compiled GnuPG from source on my GNU/Linux RPM-based system
+ and it's not working. Why?
+
+ Many GNU/Linux distributions that are RPM-based will install a
+ version of GnuPG as part of its standard installation, placing the
+ binaries in the /usr/bin directory. Later, compiling and installing
+ GnuPG from source other than from a source RPM won't normally
+ overwrite these files, as the default location for placement of
+ GnuPG binaries is in /usr/local/bin unless the '--prefix' switch
+ is used during compile to specify an alternate location. Since the
+ /usr/bin directory more than likely appears in your path before
+ /usr/local/bin, the older RPM-version binaries will continue to
+ be used when called since they were not replaced.
+
+ To resolve this, uninstall the RPM-based version with 'rpm -e gnupg'
+ before installing the binaries compiled from source. If dependency
+ errors are displayed when attempting to uninstall the RPM (such as
+ when Red Hat's up2date is also installed, which uses GnuPG), uninstall
+ the RPM with 'rpm -e gnupg --nodeps' to force the uninstall. Any
+ dependent files should be automatically replaced during the install
+ of the compiled version. If the default /usr/local/bin directory is
+ used, some packages such as SuSE's Yast Online Update may need to be
+ configured to look for GnuPG binaries in the /usr/local/bin directory,
+ or symlinks can be created in /usr/bin that point to the binaries
+ located in /usr/local/bin.
<S> ADVANCED TOPICS
@@ -796,9 +1119,9 @@
To generate a secret/public keypair, run:
- [H pre]
- gpg --gen-key
- [H/pre]
+ [H samp]
+ $ gpg --gen-key
+ [H /samp]
and choose the default values.
@@ -811,7 +1134,7 @@
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
@@ -845,16 +1168,16 @@
person it says it comes from. You should be very sure that is really
that person: You should verify the key fingerprint with:
- [H pre]
- 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.
+ [H samp]
+ $ gpg --fingerprint KeyID
+ [H /samp]
+
+ 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
+ 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
you specify the recipient (which public key you encrypt with) on the
command line instead of typing it interactively.
@@ -888,45 +1211,45 @@
You can see the validity (calculated trust value) using this
command.
- [H pre]
- gpg --list-keys --with-colons
- [H/pre]
+ [H samp]
+ $ gpg --list-keys --with-colons
+ [H /samp]
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
- [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
+ [H /pre]
The value in the "pub" record is the best one of all "uid" records.
You can get a list of the assigned trust values (how much you trust
the owner to correctly sign another person's key) with:
- [H pre]
- gpg --list-ownertrust
- [H/pre]
+ [H samp]
+ $ gpg --list-ownertrust
+ [H /samp]
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.
- [H/pre]
+ - = 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
about others. PGP stores this information with the keyring thus it
@@ -947,24 +1270,24 @@
information which is prefixed with information about the checked
item.
- [H pre]
- "key 12345678.3456"
- [H/pre]
+ [H samp]
+ "key 12345678.3456"
+ [H /samp]
This is about the key with key ID 12345678 and the internal number
3456, which is the record number of the so called directory record
in the trustdb.
- [H pre]
- "uid 12345678.3456/ACDE"
- [H/pre]
+ [H samp]
+ "uid 12345678.3456/ACDE"
+ [H /samp]
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"
- [H/pre]
+ [H samp]
+ "sig 12345678.3456/ACDE/9A8B7C6D"
+ [H /samp]
This is about the signature with key ID 9A8B7C6D for the above key
and user ID, if it is a signature which is direct on a key, the user
@@ -1003,17 +1326,17 @@
<S> ACKNOWLEDGEMENTS
Many thanks to Nils Ellmenreich for maintaining this FAQ file for
- a long time, Werner Koch for the original FAQ file, and to all
- posters to gnupg-users and gnupg-devel. They all provided most
- of the answers.
+ such a long time, Werner Koch for the original FAQ file, and to all
+ posters to gnupg-users and gnupg-devel. They all provided most of
+ the answers.
Also thanks to Casper Dik for providing us with a script to generate
this FAQ (he uses it for the excellent Solaris2 FAQ).
-[H HR]
+[H hr]
-Copyright (C) 2000-2002 Free Software Foundation, Inc.,
+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.
+any medium, provided this notice is preserved.
\ No newline at end of file
Index: gnupg/g10/ChangeLog
diff -u gnupg/g10/ChangeLog:1.688 gnupg/g10/ChangeLog:1.689
--- gnupg/g10/ChangeLog:1.688 Wed Jan 26 22:20:30 2005
+++ gnupg/g10/ChangeLog Thu Jan 27 11:30:27 2005
@@ -1,3 +1,9 @@
+2005-01-26 Werner Koch <wk at g10code.com>
+
+ * ccid-driver.c (parse_ccid_descriptor): Need the CSM workaround
+ also for newer firmware versions. Need to get a list of fixed
+ firmware versions and use that.
+
2005-01-26 David Shaw <dshaw at jabberwocky.com>
* keyserver.c (parse_keyserver_uri): Allow RFC-2732 IPv6 [literal
@@ -11135,7 +11141,7 @@
Copyright 1998, 1999, 2000, 2001, 2002, 2003,
- 2004 Free Software Foundation, Inc.
+ 2004, 2005 Free Software Foundation, Inc.
This file is free software; as a special exception the author gives
unlimited permission to copy and/or distribute it, with or without
Index: gnupg/g10/ccid-driver.c
diff -u gnupg/g10/ccid-driver.c:1.20 gnupg/g10/ccid-driver.c:1.21
--- gnupg/g10/ccid-driver.c:1.20 Tue Dec 28 08:30:57 2004
+++ gnupg/g10/ccid-driver.c Thu Jan 27 11:30:27 2005
@@ -52,7 +52,7 @@
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
* OF THE POSSIBILITY OF SUCH DAMAGE.
*
- * $Id: ccid-driver.c,v 1.20 2004/12/28 07:30:57 wk Exp $
+ * $Id: ccid-driver.c,v 1.21 2005/01/27 10:30:27 wk Exp $
*/
@@ -450,7 +450,7 @@
if (handle->id_vendor == VENDOR_SCM
/* FIXME: check whether it is the same
firmware version for all drivers. */
- && handle->bcd_device < 0x0513
+ && handle->bcd_device < 0x0519
&& handle->max_ifsd > 48)
{
DEBUGOUT ("enabling workaround for buggy SCM readers\n");
More information about the Gnupg-commits
mailing list