-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 NotDashEscaped: You need GnuPG to verify this message This is a patch file to create version 1.2.1 from 1.2.0. Please check the signature of this patch file: zcat somepath/gnupg-1.2.0-1.2.1.diff.gz | gpg --verify Change to directory gnupg-1.2.0 (or however you renamed it) and give this command: zcat somepath/gnupg-1.2.0-1.2.1.diff.gz | patch -p1 It is a good idea to rename your current directory to gnupg-1.2.1 now. Prereq: 1.2.0 diff -urpP gnupg-1.2.0/VERSION gnupg-1.2.1/VERSION --- gnupg-1.2.0/VERSION Sat Sep 21 10:35:50 2002 +++ gnupg-1.2.1/VERSION Fri Oct 25 10:07:29 2002 @@ -1 +1 @@ -1.2.0 +1.2.1 diff -urpP gnupg-1.2.0/ChangeLog gnupg-1.2.1/ChangeLog --- gnupg-1.2.0/ChangeLog Sat Sep 21 09:46:26 2002 +++ gnupg-1.2.1/ChangeLog Fri Oct 25 09:47:33 2002 @@ -1,3 +1,65 @@ +2002-10-25 Werner Koch + + Released 0.2.1. + +2002-10-24 Werner Koch + + * configure.ac (GPGKEYS_LDAP,GPGKEYS_HKP): Add $EXEEXT. + +2002-10-21 Werner Koch + + * configure.ac (try_gettext): Remove special case for cygwin. + This removes all the DOS specific macros and let Cygwin work like + a real OS. Needs a couple of changes elsewhere but after all, + GnuPG presents itself much more like a Posix program and can be + used in a full Cygwin environment; e.g. used along with mutt. + Changes suggested by Volker Quetschke. + + * acinclude.m4 (GNUPG_SYS_NM_PARSE): Allow for underscore in test + symbols. Useful for Cygwin builds. + (GNUPG_SYS_SYMBOL_UNDERSCORE): Don't hardwire to yes for Cygwin. + +2002-10-17 Werner Koch + + Released 1.2.1rc1. + + * README: Add an installation note for Darwin 6.1. + +2002-10-16 David Shaw + + * README: Some typo fixes from Florian Weimer, and bump version + number. + +2002-10-15 David Shaw + + * NEWS: Some 1.2.1 notes. + +2002-10-12 Werner Koch + + * configure.ac (NAME_OF_DEV_URANDOM): Don't use /dev/srandom for + NetBSD. Noted by Christian Biere. + +2002-10-07 David Shaw + + * configure.ac: OpenLDAP 2.0.27 changed the dependencies again. + Add a "LDAPLIBS" variable so users can try and suggest the right + dependencies for their platform. + +2002-10-02 David Shaw + + * configure.ac: Make "new" the default for TIGER. Still use + --enable-new-tiger to select new from autoconf. + + * configure.ac: Use a new option (--enable-new-tiger) to enable + TIGER with the correct OID. + +2002-09-25 David Shaw + + * THANKS: Remove duplicate. + + * configure.ac: Add NETLIBS to EGDLIBS when using EGD as EGD uses + sockets. + 2002-09-21 Werner Koch Released 1.2.0. diff -urpP gnupg-1.2.0/Makefile.in gnupg-1.2.1/Makefile.in --- gnupg-1.2.0/Makefile.in Sat Sep 21 10:32:22 2002 +++ gnupg-1.2.1/Makefile.in Fri Oct 25 09:55:51 2002 @@ -95,6 +95,7 @@ DEPDIR = @DEPDIR@ DLLTOOL = @DLLTOOL@ DOCBOOK_TO_MAN = @DOCBOOK_TO_MAN@ DOCBOOK_TO_TEXI = @DOCBOOK_TO_TEXI@ +EGDLIBS = @EGDLIBS@ FAQPROG = @FAQPROG@ GENCAT = @GENCAT@ GLIBC21 = @GLIBC21@ diff -urpP gnupg-1.2.0/NEWS gnupg-1.2.1/NEWS --- gnupg-1.2.0/NEWS Sat Sep 21 09:46:19 2002 +++ gnupg-1.2.1/NEWS Fri Oct 25 09:39:32 2002 @@ -1,3 +1,25 @@ +Noteworthy changes in version 1.2.1 (2002-10-25) +------------------------------------------------ + + * The library dependencies for OpenLDAP seem to change fairly + frequently, and GnuPG's configure script cannot guess all the + combinations. Use ./configure LDAPLIBS="-L libdir -l libs" to + override the script and use the libraries selected. + + * Secret keys generated with --export-secret-subkeys are now + indicated in key listings with a '#' after the "sec", and in + --with-colons listings by showing no capabilities (no lowercase + characters). + + * --trusted-key has been un-obsoleted, as it is useful for adding + ultimately trusted keys from the config file. It is identical + to using --edit and "trust" to change a key to ultimately + trusted. + + * The usual bug fixes as well as fixes to build problems on some + systems. + + Noteworthy changes in version 1.2.0 (2002-09-21) ------------------------------------------------ diff -urpP gnupg-1.2.0/README gnupg-1.2.1/README --- gnupg-1.2.0/README Wed Sep 11 07:31:06 2002 +++ gnupg-1.2.1/README Thu Oct 17 14:49:47 2002 @@ -1,7 +1,7 @@ GnuPG - The GNU Privacy Guard ------------------------------- - Version 1.2 + Version 1.2.1 Copyright 1998, 1999, 2000, 2001, 2002 Free Software Foundation, Inc. @@ -33,11 +33,11 @@ compatible with PGP2 versions. PGP 2.x uses IDEA (which is patented worldwide). - The default algorithms are DSA and ElGamal. ElGamal for signing - is still available, but because of the larger size of such - signatures it is deprecated (Please note that the GnuPG - implementation of ElGamal signatures is *not* insecure). Symmetric - algorithms are: AES, 3DES, Blowfish, CAST5 and Twofish + The default algorithms are DSA and ElGamal, but RSA is also + supported. ElGamal for signing is available, but because of the + larger size of such signatures it is deprecated (Please note that + the GnuPG implementation of ElGamal signatures is *not* insecure). + Symmetric algorithms are: AES, 3DES, Blowfish, CAST5 and Twofish. Digest algorithms available are MD5, RIPEMD160 and SHA1. @@ -46,8 +46,8 @@ Please read the file INSTALL and the sections in this file related to the installation. Here is a quick summary: - 1) Check that you have unmodified sources. The below on how - to do this. Don't skip it - this is an important step! + 1) Check that you have unmodified sources. See below on how to do + this. Don't skip it - this is an important step! 2) Unpack the TAR. With GNU tar you can do it this way: "tar xzvf gnupg-x.y.z.tar.gz" @@ -92,7 +92,7 @@ $ gpg --fingerprint 0x57548DCD - with the elsewhere published fingerprint + with the fingerprint published elsewhere. Please note, that you have to use an old version of GnuPG to do all this stuff. *Never* use the version which you are going @@ -547,9 +547,10 @@ make. Try gmake or grab the sources from a GNU archive and install them. - On some OSF you may get unresolved externals. This is a libtool - problem and the workaround is to manually remove all the "-lc -lz" - but the last one from the linker line and execute them manually. + On some OSF systems you may get unresolved externals. This is a + libtool problem and the workaround is to manually remove all the + "-lc -lz" but the last one from the linker line and execute them + manually. On some architectures you see warnings like: longlong.h:175: warning: function declaration isn't a prototype @@ -562,23 +563,25 @@ Specific problems on some machines ---------------------------------- - * IBM RS/6000 running AIX: + * Apple Darwin 6.1: - Due to a change in gcc (since version 2.8) the MPI stuff may - not build. In this case try to run configure using: - CFLAGS="-g -O2 -mcpu=powerpc" ./configure + ./configure --with-libiconv-prefix=/sw * Compaq C V6.2 for alpha: You may want to use the option "-msg-disable ptrmismatch1" to get rid of the sign/unsigned char mismatch warnings. + * IBM RS/6000 running AIX: + + Due to a change in gcc (since version 2.8) the MPI stuff may + not build. In this case try to run configure using: + CFLAGS="-g -O2 -mcpu=powerpc" ./configure + * SVR4.2 (ESIX V4.2 cc) Due to problems with the ESIX as, you probably want to do CFLAGS="-O -K pentium" ./configure --disable-asm - Reported by Reinhard Wobst. - The Random Device diff -urpP gnupg-1.2.0/THANKS gnupg-1.2.1/THANKS --- gnupg-1.2.0/THANKS Tue Sep 10 08:42:25 2002 +++ gnupg-1.2.1/THANKS Mon Oct 21 16:04:04 2002 @@ -199,6 +199,7 @@ Thomas Mikkelsen tbm@image.dk Ulf Möller 3umoelle@informatik.uni-hamburg.de Urko Lusa ulusa@euskalnet.net Vincent P. Broman broman@spawar.navy.mil +Volker Quetschke quetschke@scytek.de W Lewis wiml@hhhh.org Walter Hofmann Walter.Hofmann@physik.stud.uni-erlangen.de Walter Koch koch@hsp.de @@ -208,7 +209,6 @@ Wim Vandeputte bunbun@reptile.rug.ac Winona Brown win@huh.org Yosiaki IIDA iida@ring.gr.jp Yoshihiro Kajiki kajiki@ylug.org - disastry@saiknes.lv nbecker@hns.com Thanks to the German Unix User Group for sponsoring this project, diff -urpP gnupg-1.2.0/acinclude.m4 gnupg-1.2.1/acinclude.m4 --- gnupg-1.2.0/acinclude.m4 Sat Jun 29 14:15:02 2002 +++ gnupg-1.2.1/acinclude.m4 Mon Oct 21 15:29:47 2002 @@ -570,8 +570,8 @@ changequote([,])dnl fi # Make sure that we snagged all the symbols we need. - if egrep ' nm_test_var$' "$ac_nlist" >/dev/null; then - if egrep ' nm_test_func$' "$ac_nlist" >/dev/null; then + if egrep ' _?nm_test_var$' "$ac_nlist" >/dev/null; then + if egrep ' _?nm_test_func$' "$ac_nlist" >/dev/null; then cat < conftest.c #ifdef __cplusplus extern "C" { @@ -579,7 +579,7 @@ extern "C" { EOF # Now generate the symbol file. - sed 's/^.* \(.*\)$/extern char \1;/' < "$ac_nlist" >> conftest.c + sed 's/^.* _\?\(.*\)$/extern char \1;/' < "$ac_nlist" >> conftest.c cat <> conftest.c #if defined (__STDC__) && __STDC__ @@ -601,7 +601,7 @@ dld_preloaded_symbols[] = changequote([,])dnl { EOF - sed 's/^\(.*\) \(.*\)$/ {"\1", (__ptr_t) \&\2},/' < "$ac_nlist" >> conftest.c + sed 's/^_\?\(.*\) _\?\(.*\)$/ {"\1", (__ptr_t) \&\2},/' < "$ac_nlist" >> conftest.c cat <<\EOF >> conftest.c {0, (__ptr_t) 0} }; @@ -661,7 +661,7 @@ AC_CHECK_TOOL(AS, as, false) AC_DEFUN(GNUPG_SYS_SYMBOL_UNDERSCORE, [tmp_do_check="no" case "${target}" in - i386-emx-os2 | i[3456]86-pc-os2*emx | i386-pc-msdosdjgpp | *-*-cygwin) + i386-emx-os2 | i[3456]86-pc-os2*emx | i386-pc-msdosdjgpp) ac_cv_sys_symbol_underscore=yes ;; *) diff -urpP gnupg-1.2.0/aclocal.m4 gnupg-1.2.1/aclocal.m4 --- gnupg-1.2.0/aclocal.m4 Sat Sep 21 10:32:14 2002 +++ gnupg-1.2.1/aclocal.m4 Fri Oct 25 09:55:40 2002 @@ -574,8 +574,8 @@ changequote([,])dnl fi # Make sure that we snagged all the symbols we need. - if egrep ' nm_test_var$' "$ac_nlist" >/dev/null; then - if egrep ' nm_test_func$' "$ac_nlist" >/dev/null; then + if egrep ' _?nm_test_var$' "$ac_nlist" >/dev/null; then + if egrep ' _?nm_test_func$' "$ac_nlist" >/dev/null; then cat < conftest.c #ifdef __cplusplus extern "C" { @@ -583,7 +583,7 @@ extern "C" { EOF # Now generate the symbol file. - sed 's/^.* \(.*\)$/extern char \1;/' < "$ac_nlist" >> conftest.c + sed 's/^.* _\?\(.*\)$/extern char \1;/' < "$ac_nlist" >> conftest.c cat <> conftest.c #if defined (__STDC__) && __STDC__ @@ -605,7 +605,7 @@ dld_preloaded_symbols[] = changequote([,])dnl { EOF - sed 's/^\(.*\) \(.*\)$/ {"\1", (__ptr_t) \&\2},/' < "$ac_nlist" >> conftest.c + sed 's/^_\?\(.*\) _\?\(.*\)$/ {"\1", (__ptr_t) \&\2},/' < "$ac_nlist" >> conftest.c cat <<\EOF >> conftest.c {0, (__ptr_t) 0} }; @@ -665,7 +665,7 @@ AC_CHECK_TOOL(AS, as, false) AC_DEFUN(GNUPG_SYS_SYMBOL_UNDERSCORE, [tmp_do_check="no" case "${target}" in - i386-emx-os2 | i[3456]86-pc-os2*emx | i386-pc-msdosdjgpp | *-*-cygwin) + i386-emx-os2 | i[3456]86-pc-os2*emx | i386-pc-msdosdjgpp) ac_cv_sys_symbol_underscore=yes ;; *) diff -urpP gnupg-1.2.0/checks/Makefile.in gnupg-1.2.1/checks/Makefile.in --- gnupg-1.2.0/checks/Makefile.in Sat Sep 21 10:35:44 2002 +++ gnupg-1.2.1/checks/Makefile.in Fri Oct 25 10:07:22 2002 @@ -97,6 +97,7 @@ DEPDIR = @DEPDIR@ DLLTOOL = @DLLTOOL@ DOCBOOK_TO_MAN = @DOCBOOK_TO_MAN@ DOCBOOK_TO_TEXI = @DOCBOOK_TO_TEXI@ +EGDLIBS = @EGDLIBS@ FAQPROG = @FAQPROG@ GENCAT = @GENCAT@ GLIBC21 = @GLIBC21@ diff -urpP gnupg-1.2.0/cipher/ChangeLog gnupg-1.2.1/cipher/ChangeLog --- gnupg-1.2.0/cipher/ChangeLog Tue Sep 17 08:48:49 2002 +++ gnupg-1.2.1/cipher/ChangeLog Mon Oct 21 15:35:17 2002 @@ -1,3 +1,30 @@ +2002-10-21 Werner Koch + + * rndw32.c [__CYGWIN32__]: Don't include winioctl.h - it is not + required anymore. + + * random.c (read_seed_file,update_random_seed_file): Use binary + mode for __CYGWIN__. + +2002-10-12 Werner Koch + + * rndunix.c (my_popen): Make sure that stdin and stderr are + connected to a file. This is to avoid NetBSD to complain about + set{u,g}id programs invoked with fd 0, 2 closed. Reported by + Cristian Biere. + (start_gatherer): Likewise. Reordered code. + +2002-10-02 David Shaw + + * tiger.c (tiger_get_info): Select the OID to use for TIGER at + compile time. + +2002-09-26 Werner Koch + + * tiger.c (tiger_get_info): Use a regular OID. Note that this + breaks all TIGER generated signatures; if we want to do something + about it we have to do it in ../g10/sig-check.c . + 2002-09-17 Werner Koch * rndw32.c (SIZEOF_DISK_PERFORMANCE_STRUCT): Increased to 256. diff -urpP gnupg-1.2.0/cipher/Makefile.in gnupg-1.2.1/cipher/Makefile.in --- gnupg-1.2.0/cipher/Makefile.in Sat Sep 21 10:34:03 2002 +++ gnupg-1.2.1/cipher/Makefile.in Fri Oct 25 10:05:39 2002 @@ -95,6 +95,7 @@ DEPDIR = @DEPDIR@ DLLTOOL = @DLLTOOL@ DOCBOOK_TO_MAN = @DOCBOOK_TO_MAN@ DOCBOOK_TO_TEXI = @DOCBOOK_TO_TEXI@ +EGDLIBS = @EGDLIBS@ FAQPROG = @FAQPROG@ GENCAT = @GENCAT@ GLIBC21 = @GLIBC21@ diff -urpP gnupg-1.2.0/cipher/random.c gnupg-1.2.1/cipher/random.c --- gnupg-1.2.0/cipher/random.c Fri Aug 30 16:33:55 2002 +++ gnupg-1.2.1/cipher/random.c Mon Oct 21 15:33:04 2002 @@ -311,9 +311,9 @@ mix_pool(byte *pool) RMD160_CONTEXT md; rmd160_init( &md ); - #if DIGESTLEN != 20 +#if DIGESTLEN != 20 #error must have a digest length of 20 for ripe-md-160 - #endif +#endif /* loop over the pool */ pend = pool + POOLSIZE; memcpy(hashbuf, pend - DIGESTLEN, DIGESTLEN ); @@ -367,11 +367,11 @@ read_seed_file(void) if( !seed_file_name ) return 0; - #ifdef HAVE_DOSISH_SYSTEM +#if defined(HAVE_DOSISH_SYSTEM) || defined(__CYGWIN__) fd = open( seed_file_name, O_RDONLY | O_BINARY ); - #else +#else fd = open( seed_file_name, O_RDONLY ); - #endif +#endif if( fd == -1 && errno == ENOENT) { allow_seed_file_update = 1; return 0; @@ -457,12 +457,12 @@ update_random_seed_file() mix_pool(rndpool); rndstats.mixrnd++; mix_pool(keypool); rndstats.mixkey++; - #ifdef HAVE_DOSISH_SYSTEM +#if defined(HAVE_DOSISH_SYSTEM) || defined(__CYGWIN__) fd = open( seed_file_name, O_WRONLY|O_CREAT|O_TRUNC|O_BINARY, S_IRUSR|S_IWUSR ); - #else +#else fd = open( seed_file_name, O_WRONLY|O_CREAT|O_TRUNC, S_IRUSR|S_IWUSR ); - #endif +#endif if( fd == -1 ) { log_info(_("can't create `%s': %s\n"), seed_file_name, strerror(errno) ); return; diff -urpP gnupg-1.2.0/cipher/rndunix.c gnupg-1.2.1/cipher/rndunix.c --- gnupg-1.2.0/cipher/rndunix.c Sun Aug 4 22:00:32 2002 +++ gnupg-1.2.1/cipher/rndunix.c Sat Oct 12 14:50:10 2002 @@ -391,10 +391,17 @@ my_popen(struct RI *entry) if (entry->pid == (pid_t) 0) { struct passwd *passwd; + int fd; /* We are the child. Make the read side of the pipe be stdout */ if (dup2(pipedes[STDOUT_FILENO], STDOUT_FILENO) < 0) exit(127); + /* Connect the other standard handles to the bit bucket. */ + if ((fd = open ("/dev/null", O_RDWR)) != -1) { + dup2 (fd, STDIN_FILENO); + dup2 (fd, STDERR_FILENO); + close (fd); + } /* Now that everything is set up, give up our permissions to make * sure we don't read anything sensitive. If the getpwnam() fails, @@ -405,7 +412,7 @@ my_popen(struct RI *entry) setuid(gatherer_uid); - /* Close the pipe descriptors */ + /* Close the pipe descriptors. */ close(pipedes[STDIN_FILENO]); close(pipedes[STDOUT_FILENO]); @@ -659,28 +666,6 @@ start_gatherer( int pipefd ) } dbgall = !!getenv("GNUPG_RNDUNIX_DBGALL"); } - /* close all files but the ones we need */ - { int nmax, n1, n2, i; - #ifdef _SC_OPEN_MAX - if( (nmax=sysconf( _SC_OPEN_MAX )) < 0 ) { - #ifdef _POSIX_OPEN_MAX - nmax = _POSIX_OPEN_MAX; - #else - nmax = 20; /* assume a reasonable value */ - #endif - } - #else - nmax = 20; /* assume a reasonable value */ - #endif - n1 = fileno( stderr ); - n2 = dbgfp? fileno( dbgfp ) : -1; - for(i=0; i < nmax; i++ ) { - if( i != n1 && i != n2 && i != pipefd ) - close(i); - } - errno = 0; - } - /* Set up the buffer */ @@ -705,7 +690,39 @@ start_gatherer( int pipefd ) signal(SIGCHLD, SIG_DFL); #endif - fclose(stderr); /* Arrghh!! It's Stuart code!! */ + fflush (stderr); + /* Arrghh!! It's Stuart code!! */ + /* (close all files but the ones we need) */ + { int nmax, n1, i; + #ifdef _SC_OPEN_MAX + if( (nmax=sysconf( _SC_OPEN_MAX )) < 0 ) { + #ifdef _POSIX_OPEN_MAX + nmax = _POSIX_OPEN_MAX; + #else + nmax = 20; /* assume a reasonable value */ + #endif + } + #else + nmax = 20; /* assume a reasonable value */ + #endif + { + int fd; + if ((fd = open ("/dev/null", O_RDWR)) != -1) { + dup2 (fd, STDIN_FILENO); + dup2 (fd, STDOUT_FILENO); + dup2 (fd, STDERR_FILENO); + close (fd); + } + } + n1 = dbgfp? fileno (dbgfp) : -1; + for(i=0; i < nmax; i++ ) { + if (i != STDIN_FILENO && i != STDOUT_FILENO && i != STDERR_FILENO + && i != n1 && i != pipefd ) + close(i); + } + errno = 0; + } + for(;;) { GATHER_MSG msg; diff -urpP gnupg-1.2.0/cipher/rndw32.c gnupg-1.2.1/cipher/rndw32.c --- gnupg-1.2.0/cipher/rndw32.c Tue Sep 17 08:48:53 2002 +++ gnupg-1.2.1/cipher/rndw32.c Mon Oct 21 15:35:26 2002 @@ -70,9 +70,6 @@ #include #include -#ifdef __CYGWIN32__ -# include -#endif #include "types.h" diff -urpP gnupg-1.2.0/cipher/tiger.c gnupg-1.2.1/cipher/tiger.c --- gnupg-1.2.0/cipher/tiger.c Sat Aug 3 10:50:38 2002 +++ gnupg-1.2.1/cipher/tiger.c Sat Oct 12 11:39:29 2002 @@ -897,21 +897,19 @@ tiger_get_info( int algo, size_t *contex ) { #ifdef HAVE_U64_TYPEDEF - /* 40: SEQUENCE { - * 12: SEQUENCE { - * 8: OCTET STRING :54 49 47 45 52 31 39 32 - * 0: NULL - * : } - * 24: OCTET STRING - * : } - * - * By replacing the 5th byte (0x04) with 0x16 we would have; - * 8: IA5String 'TIGER192' - * Fixme: We should use a registered OID. - */ + +#ifdef USE_OLD_TIGER + /* This is the old fake OID */ static byte asn[18] = - { 0x30, 0x28, 0x30, 0x0c, 0x04, 0x08, 0x54, 0x49, 0x47, - 0x45, 0x52, 0x31, 0x39, 0x32, 0x05, 0x00, 0x04, 0x18 }; + { 0x30, 0x28, 0x30, 0x0c, 0x04, 0x08, 0x54, 0x49, 0x47, + 0x45, 0x52, 0x31, 0x39, 0x32, 0x05, 0x00, 0x04, 0x18 }; +#else /* !USE_OLD_TIGER */ + /* This is the new correct OID */ + static byte asn[19] = /* Object ID is 1.3.6.1.4.1.11591.12.2 */ + { 0x30, 0x29, 0x30, 0x0d, 0x06, 0x09, 0x2b, 0x06, + 0x01, 0x04, 0x01, 0xda, 0x47, 0x0c, 0x02, + 0x05, 0x00, 0x04, 0x18 }; +#endif if( algo != 6 ) return NULL; diff -urpP gnupg-1.2.0/config.h.in gnupg-1.2.1/config.h.in --- gnupg-1.2.0/config.h.in Sat Sep 21 10:33:20 2002 +++ gnupg-1.2.1/config.h.in Fri Oct 25 09:57:04 2002 @@ -428,6 +428,9 @@ /* define to use the experimental external HKP keyserver interface */ #undef USE_EXTERNAL_HKP +/* Define to use the old fake OID for TIGER digest support */ +#undef USE_OLD_TIGER + /* set this to limit filenames to the 8.3 format */ #undef USE_ONLY_8DOT3 diff -urpP gnupg-1.2.0/configure gnupg-1.2.1/configure --- gnupg-1.2.0/configure Sat Sep 21 10:32:56 2002 +++ gnupg-1.2.1/configure Fri Oct 25 09:56:46 2002 @@ -1,6 +1,6 @@ #! /bin/sh # Guess values for system-dependent variables and create Makefiles. -# Generated by GNU Autoconf 2.53 for gnupg 1.2.0. +# Generated by GNU Autoconf 2.53 for gnupg 1.2.1. # # Report bugs to . # @@ -256,8 +256,8 @@ SHELL=${CONFIG_SHELL-/bin/sh} # Identity of this package. PACKAGE_NAME='gnupg' PACKAGE_TARNAME='gnupg' -PACKAGE_VERSION='1.2.0' -PACKAGE_STRING='gnupg 1.2.0' +PACKAGE_VERSION='1.2.1' +PACKAGE_STRING='gnupg 1.2.1' PACKAGE_BUGREPORT='bug-gnupg@gnu.org' ac_unique_file="g10/g10.c" @@ -762,7 +762,7 @@ if test "$ac_init_help" = "long"; then # Omit some internal or obsolete options to make the list less imposing. # This message is too long to be a string in the A/UX 3.1 sh. cat <<_ACEOF -\`configure' configures gnupg 1.2.0 to adapt to many kinds of systems. +\`configure' configures gnupg 1.2.1 to adapt to many kinds of systems. Usage: $0 [OPTION]... [VAR=VALUE]... @@ -829,7 +829,7 @@ fi if test -n "$ac_init_help"; then case $ac_init_help in - short | recursive ) echo "Configuration of gnupg 1.2.0:";; + short | recursive ) echo "Configuration of gnupg 1.2.1:";; esac cat <<\_ACEOF @@ -842,6 +842,7 @@ Optional Features: --disable-asm do not use assembler modules --enable-m-guard enable memory guard facility --enable-tiger enable experimental TIGER digest support + --enable-new-tiger enable new-style experimental TIGER digest support --disable-exec disable all external program execution --disable-photo-viewers disable photo ID viewers --disable-keyserver-helpers disable all external keyserver support @@ -943,7 +944,7 @@ fi test -n "$ac_init_help" && exit 0 if $ac_init_version; then cat <<\_ACEOF -gnupg configure 1.2.0 +gnupg configure 1.2.1 generated by GNU Autoconf 2.53 Copyright 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001, 2002 @@ -958,7 +959,7 @@ cat >&5 <<_ACEOF This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. -It was created by gnupg $as_me 1.2.0, which was +It was created by gnupg $as_me 1.2.1, which was generated by GNU Autoconf 2.53. Invocation command line was $ $0 $@ @@ -1236,6 +1237,9 @@ ac_compiler_gnu=$ac_cv_c_compiler_gnu +# Set development_version to yes if the minor number is odd or you +# feel that the default check for a development version is not +# sufficient. development_version=no ALL_LINGUAS="ca cs da de eo el es et fr gl id it ja nl pl pt_BR pt sv tr" @@ -1878,6 +1882,32 @@ cat >>confdefs.h <<\_ACEOF #define USE_TIGER 1 _ACEOF + +cat >>confdefs.h <<\_ACEOF +#define USE_OLD_TIGER 1 +_ACEOF + +else + echo "$as_me:$LINENO: checking whether to enable new-style experimental TIGER digest support" >&5 +echo $ECHO_N "checking whether to enable new-style experimental TIGER digest support... $ECHO_C" >&6 + # Check whether --enable-new-tiger or --disable-new-tiger was given. +if test "${enable_new_tiger+set}" = set; then + enableval="$enable_new_tiger" + use_new_tiger=$enableval +else + use_new_tiger=no +fi; + echo "$as_me:$LINENO: result: $use_new_tiger" >&5 +echo "${ECHO_T}$use_new_tiger" >&6 + if test "$use_new_tiger" = yes ; then + TIGER_O=tiger.o + + +cat >>confdefs.h <<\_ACEOF +#define USE_TIGER 1 +_ACEOF + + fi fi echo "$as_me:$LINENO: checking whether to enable external program execution" >&5 @@ -1987,7 +2017,7 @@ fi; echo "${ECHO_T}$try_hkp" >&6 if test "$try_hkp" = yes ; then - GPGKEYS_HKP="gpgkeys_hkp" + GPGKEYS_HKP="gpgkeys_hkp$EXEEXT" cat >>confdefs.h <<\_ACEOF #define USE_EXTERNAL_HKP 1 @@ -3941,7 +3971,7 @@ MPI_OPT_FLAGS="" try_gettext=yes case "${target}" in - *-*-mingw32*|*-*-cygwin*) + *-*-mingw32*) # special stuff for Windoze NT ac_cv_have_dev_random=no @@ -4154,8 +4184,8 @@ if { (eval echo "$as_me:$LINENO: \"$ac_c fi # Make sure that we snagged all the symbols we need. - if egrep ' nm_test_var$' "$ac_nlist" >/dev/null; then - if egrep ' nm_test_func$' "$ac_nlist" >/dev/null; then + if egrep ' _?nm_test_var$' "$ac_nlist" >/dev/null; then + if egrep ' _?nm_test_func$' "$ac_nlist" >/dev/null; then cat < conftest.c #ifdef __cplusplus extern "C" { @@ -4163,7 +4193,7 @@ extern "C" { EOF # Now generate the symbol file. - sed 's/^.* \(.*\)$/extern char \1;/' < "$ac_nlist" >> conftest.c + sed 's/^.* _\?\(.*\)$/extern char \1;/' < "$ac_nlist" >> conftest.c cat <> conftest.c #if defined (__STDC__) && __STDC__ @@ -4183,7 +4213,7 @@ struct { dld_preloaded_symbols[] = { EOF - sed 's/^\(.*\) \(.*\)$/ {"\1", (__ptr_t) \&\2},/' < "$ac_nlist" >> conftest.c + sed 's/^_\?\(.*\) _\?\(.*\)$/ {"\1", (__ptr_t) \&\2},/' < "$ac_nlist" >> conftest.c cat <<\EOF >> conftest.c {0, (__ptr_t) 0} }; @@ -4240,7 +4270,7 @@ echo "${ECHO_T}$ac_result" >&6 tmp_do_check="no" case "${target}" in - i386-emx-os2 | i345686-pc-os2*emx | i386-pc-msdosdjgpp | *-*-cygwin) + i386-emx-os2 | i345686-pc-os2*emx | i386-pc-msdosdjgpp) ac_cv_sys_symbol_underscore=yes ;; *) @@ -4570,16 +4600,18 @@ fi # Try and link a LDAP test program to weed out unusable LDAP -# libraries. -lldap [-llber [-lresolv]] is for OpenLDAP. -lldapssl41 -# is for Mozilla LDAP. +# libraries. -lldap [-llber [-lresolv]] is for OpenLDAP. OpenLDAP in +# general is terrible with creating weird dependencies. If all else +# fails, the user can play guess-the-dependency by using something +# like LDAPLIBS="-lfoo" ./configure if test "$try_ldap" = yes ; then - for LDAPLIBS in "-lldap" "-lldap -llber" "-lldap -llber -lresolv" "-lldapssl41"; do + for MY_LDAPLIBS in ${LDAPLIBS+"$LDAPLIBS"} "-lldap" "-lldap -llber" "-lldap -llber -lresolv"; do _ldap_save_libs=$LIBS - LIBS="$LDAPLIBS $NETLIBS $LIBS" + LIBS="$MY_LDAPLIBS $NETLIBS $LIBS" - echo "$as_me:$LINENO: checking whether LDAP via \"$LDAPLIBS\" is present and sane" >&5 -echo $ECHO_N "checking whether LDAP via \"$LDAPLIBS\" is present and sane... $ECHO_C" >&6 + echo "$as_me:$LINENO: checking whether LDAP via \"$MY_LDAPLIBS\" is present and sane" >&5 +echo $ECHO_N "checking whether LDAP via \"$MY_LDAPLIBS\" is present and sane... $ECHO_C" >&6 cat >conftest.$ac_ext <<_ACEOF #line $LINENO "configure" #include "confdefs.h" @@ -4675,7 +4707,8 @@ _ACEOF if test "$gnupg_cv_func_ldap_init" = yes || \ test "$gnupg_cv_func_ldaplber_init" = yes ; then - GPGKEYS_LDAP="gpgkeys_ldap" + GPGKEYS_LDAP="gpgkeys_ldap$EXEEXT" + LDAPLIBS=$MY_LDAPLIBS fi LIBS=$_ldap_save_libs @@ -4760,7 +4793,7 @@ case "${target}" in PRINTABLE_OS_NAME="MingW32" ;; *-*-cygwin*) - PRINTABLE_OS_NAME="Cygwin32" + PRINTABLE_OS_NAME="Cygwin" ;; i?86-emx-os2 | i?86-*-os2*emx ) PRINTABLE_OS_NAME="OS/2" @@ -4792,7 +4825,7 @@ _ACEOF NAME_OF_DEV_RANDOM="/dev/random" NAME_OF_DEV_URANDOM="/dev/urandom" case "${target}" in - *-openbsd* | *-netbsd*) + *-openbsd*) NAME_OF_DEV_RANDOM="/dev/srandom" NAME_OF_DEV_URANDOM="/dev/urandom" ;; @@ -12778,6 +12811,8 @@ cat >>confdefs.h <<\_ACEOF #define USE_RNDEGD 1 _ACEOF + EGDLIBS=$NETLIBS + ;; rndw32) @@ -13539,7 +13574,7 @@ _ASBOX } >&5 cat >&5 <<_CSEOF -This file was extended by gnupg $as_me 1.2.0, which was +This file was extended by gnupg $as_me 1.2.1, which was generated by GNU Autoconf 2.53. Invocation command line was CONFIG_FILES = $CONFIG_FILES @@ -13604,7 +13639,7 @@ _ACEOF cat >>$CONFIG_STATUS <<_ACEOF ac_cs_version="\\ -gnupg config.status 1.2.0 +gnupg config.status 1.2.1 configured by $0, generated by GNU Autoconf 2.53, with options \\"`echo "$ac_configure_args" | sed 's/[\\""\`\$]/\\\\&/g'`\\" @@ -13902,6 +13937,7 @@ s,@GENCAT@,$GENCAT,;t t s,@MKINSTALLDIRS@,$MKINSTALLDIRS,;t t s,@INTL_LIBTOOL_SUFFIX_PREFIX@,$INTL_LIBTOOL_SUFFIX_PREFIX,;t t s,@LIBOBJS@,$LIBOBJS,;t t +s,@EGDLIBS@,$EGDLIBS,;t t s,@MPI_EXTRA_ASM_OBJS@,$MPI_EXTRA_ASM_OBJS,;t t s,@MPI_SFLAGS@,$MPI_SFLAGS,;t t s,@ENABLE_LOCAL_ZLIB_TRUE@,$ENABLE_LOCAL_ZLIB_TRUE,;t t diff -urpP gnupg-1.2.0/configure.ac gnupg-1.2.1/configure.ac --- gnupg-1.2.0/configure.ac Sat Sep 21 10:19:15 2002 +++ gnupg-1.2.1/configure.ac Fri Oct 25 09:55:03 2002 @@ -18,15 +18,16 @@ dnl along with this program; if not, wri dnl Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA dnl dnl (Process this file with autoconf to produce a configure script.) -dnlAC_REVISION($Revision: 1.25.2.3 $)dnl +dnlAC_REVISION($Revision: 1.25.2.13 $)dnl AC_PREREQ(2.52) -# Remember to change the version number immediately *after* a release. +# Remember to change the version number immediately *after* a release +# and remove the "-cvs" or "rc" suffix immediately *before* a release. +AC_INIT(gnupg, 1.2.1, bug-gnupg@gnu.org) # Set development_version to yes if the minor number is odd or you # feel that the default check for a development version is not # sufficient. -AC_INIT(gnupg, 1.2.0, bug-gnupg@gnu.org) development_version=no ALL_LINGUAS="ca cs da de eo el es et fr gl id it ja nl pl pt_BR pt sv tr" @@ -143,6 +144,17 @@ AC_MSG_RESULT($use_tiger) if test "$use_tiger" = yes ; then AC_SUBST(TIGER_O,tiger.o) AC_DEFINE(USE_TIGER,1,[Define to include experimental TIGER digest support]) + AC_DEFINE(USE_OLD_TIGER,1,[Define to use the old fake OID for TIGER digest support]) +else + AC_MSG_CHECKING([whether to enable new-style experimental TIGER digest support]) + AC_ARG_ENABLE(new-tiger, + [ --enable-new-tiger enable new-style experimental TIGER digest support], + use_new_tiger=$enableval, use_new_tiger=no) + AC_MSG_RESULT($use_new_tiger) + if test "$use_new_tiger" = yes ; then + AC_SUBST(TIGER_O,tiger.o) + AC_DEFINE(USE_TIGER,1,[Define to include experimental TIGER digest support]) + fi fi AC_MSG_CHECKING([whether to enable external program execution]) @@ -201,7 +213,7 @@ if test "$use_exec" = yes ; then AC_MSG_RESULT($try_hkp) if test "$try_hkp" = yes ; then - GPGKEYS_HKP="gpgkeys_hkp" + GPGKEYS_HKP="gpgkeys_hkp$EXEEXT" AC_DEFINE(USE_EXTERNAL_HKP,1,[define to use the experimental external HKP keyserver interface]) fi @@ -276,7 +288,7 @@ MPI_OPT_FLAGS="" try_gettext=yes case "${target}" in - *-*-mingw32*|*-*-cygwin*) + *-*-mingw32*) # special stuff for Windoze NT ac_cv_have_dev_random=no AC_DEFINE(USE_ONLY_8DOT3,1, @@ -356,15 +368,17 @@ AC_CHECK_FUNC(setsockopt, , AC_CHECK_LIB [NETLIBS="-lsocket $NETLIBS"])) # Try and link a LDAP test program to weed out unusable LDAP -# libraries. -lldap [-llber [-lresolv]] is for OpenLDAP. -lldapssl41 -# is for Mozilla LDAP. +# libraries. -lldap [-llber [-lresolv]] is for OpenLDAP. OpenLDAP in +# general is terrible with creating weird dependencies. If all else +# fails, the user can play guess-the-dependency by using something +# like LDAPLIBS="-lfoo" ./configure if test "$try_ldap" = yes ; then - for LDAPLIBS in "-lldap" "-lldap -llber" "-lldap -llber -lresolv" "-lldapssl41"; do + for MY_LDAPLIBS in ${LDAPLIBS+"$LDAPLIBS"} "-lldap" "-lldap -llber" "-lldap -llber -lresolv"; do _ldap_save_libs=$LIBS - LIBS="$LDAPLIBS $NETLIBS $LIBS" + LIBS="$MY_LDAPLIBS $NETLIBS $LIBS" - AC_MSG_CHECKING([whether LDAP via \"$LDAPLIBS\" is present and sane]) + AC_MSG_CHECKING([whether LDAP via \"$MY_LDAPLIBS\" is present and sane]) AC_TRY_LINK([#include ],[ldap_open("foobar",1234);], [gnupg_cv_func_ldap_init=yes],[gnupg_cv_func_ldap_init=no]) AC_MSG_RESULT([$gnupg_cv_func_ldap_init]) @@ -383,7 +397,8 @@ if test "$try_ldap" = yes ; then if test "$gnupg_cv_func_ldap_init" = yes || \ test "$gnupg_cv_func_ldaplber_init" = yes ; then - GPGKEYS_LDAP="gpgkeys_ldap" + GPGKEYS_LDAP="gpgkeys_ldap$EXEEXT" + LDAPLIBS=$MY_LDAPLIBS fi LIBS=$_ldap_save_libs @@ -423,7 +438,7 @@ case "${target}" in PRINTABLE_OS_NAME="MingW32" ;; *-*-cygwin*) - PRINTABLE_OS_NAME="Cygwin32" + PRINTABLE_OS_NAME="Cygwin" ;; i?86-emx-os2 | i?86-*-os2*emx ) PRINTABLE_OS_NAME="OS/2" @@ -453,7 +468,7 @@ AC_DEFINE_UNQUOTED(PRINTABLE_OS_NAME, "$ NAME_OF_DEV_RANDOM="/dev/random" NAME_OF_DEV_URANDOM="/dev/urandom" case "${target}" in - *-openbsd* | *-netbsd*) + *-openbsd*) NAME_OF_DEV_RANDOM="/dev/srandom" NAME_OF_DEV_URANDOM="/dev/urandom" ;; @@ -692,6 +707,8 @@ for rndmod in $random_modules "" ; do rndegd) AC_DEFINE(USE_RNDEGD,1, [Defined if the EGD based RNG should be used.]) + EGDLIBS=$NETLIBS + AC_SUBST(EGDLIBS) ;; rndw32) AC_DEFINE(USE_RNDW32,1, diff -urpP gnupg-1.2.0/doc/ChangeLog gnupg-1.2.1/doc/ChangeLog --- gnupg-1.2.0/doc/ChangeLog Fri Sep 20 17:19:59 2002 +++ gnupg-1.2.1/doc/ChangeLog Fri Oct 25 09:46:26 2002 @@ -1,3 +1,34 @@ +2002-10-25 Werner Koch + + * README.W32: Add blurb on how to create a ZIP file, changed + requirement for mingw32 to 0.3.2. + +2002-10-24 David Shaw + + * gpg.sgml: Document --refresh-keys. + +2002-10-19 David Shaw + + * gpg.sgml: Clarify --force-mdc, and document --disable-mdc. + +2002-10-17 Werner Koch + + * 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 + + * DETAILS (KEY_CREATED): Enhanced by fingerprint. + +2002-10-03 David Shaw + + * gpg.sgml: Note that '#' means secret-key-unavailable, and that + keyserver schemes are case-insensitive. + +2002-09-30 David Shaw + + * gpg.sgml: Note that --pgp2 disables --textmode when encrypting. + 2002-09-20 David Shaw * gpg.sgml: Some minor language cleanup. diff -urpP gnupg-1.2.0/doc/DETAILS gnupg-1.2.1/doc/DETAILS --- gnupg-1.2.0/doc/DETAILS Fri Sep 20 06:00:36 2002 +++ gnupg-1.2.1/doc/DETAILS Sat Oct 12 11:18:56 2002 @@ -335,11 +335,13 @@ more arguments in future versions. (only the first character should be checked) class: 2 hex digits with the signature class - KEY_CREATED + KEY_CREATED A key has been created type: 'B' = primary and subkey 'P' = primary 'S' = subkey + The fingerprint is one of the primary key for type B and P and + the one of the subkey for S. SESSION_KEY : The session key used to decrypt the message. This message will diff -urpP gnupg-1.2.0/doc/FAQ gnupg-1.2.1/doc/FAQ --- gnupg-1.2.0/doc/FAQ Fri Sep 20 17:10:36 2002 +++ gnupg-1.2.1/doc/FAQ Thu Oct 17 12:47:54 2002 @@ -2,38 +2,39 @@ GnuPG Frequently Asked Questions -Version: 1.5.7 -Last-Modified: Aug 21, 2002 +Version: 1.5.8 +Last-Modified: Oct 8, 2002 Maintained-by: David D. Scribner, This is the GnuPG FAQ. The latest HTML version is available here. -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. 1. GENERAL 1.1) What is GnuPG? 1.2) Is GnuPG compatible with PGP? + 1.3) Is GnuPG free to use for personal or commercial use? 2. SOURCES of INFORMATION - 2.1) Where can I find more information? + 2.1) Where can I find more information on GnuPG? 2.2) Where do I get GnuPG? 3. INSTALLATION 3.1) Which OSes does GnuPG run on? - 3.2) Which random gatherer should I use? + 3.2) Which random data gatherer should I use? 3.3) How do I include support for RSA and IDEA? 4. USAGE @@ -41,9 +42,10 @@ search in the mailing list archive. 4.2) Why does it sometimes take so long to create keys? 4.3) And it really takes long when I work on a remote system. Why? 4.4) What is the difference between options and commands? - 4.5) I can't delete a user ID because it is already deleted on my public - keyring? - 4.6) I can't delete the secret key because my public key disappeared? + 4.5) 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? + 4.6) I can't delete my secret key because the public key disappeared. + What can I do? 4.7) What are trust, validity and ownertrust? 4.8) How do I sign a patch file? 4.9) Where is the "encrypt-to-self" option? @@ -51,7 +53,7 @@ search in the mailing list archive. messages? 4.11) What does the "You are using the xxxx character set." mean? 4.12) How can a get list of key IDs used to encrypt a message? - 4.13) I can't decrypt my symmetrical only (-c) encrypted message with + 4.13) I can't decrypt my symmetrical-only (-c) encrypted messages with a new version of GnuPG. 4.14) How can I use GnuPG in an automated environment? 4.15) Which email-client can I use with GnuPG? @@ -68,12 +70,14 @@ search in the mailing list archive. 5.5) Why is PGP 5.x not able to verify my messages? 5.6) How do I transfer owner trust values from PGP to GnuPG? 5.7) PGP does not like my secret key. + 5.8) I just installed the most recent version of GnuPG and don't have a + ~/.gnupg/options file. Is this missing from the installation? 6. PROBLEMS and ERROR MESSAGES 6.1) Why do I get "gpg: Warning: using insecure memory!" 6.2) Large File Support doesn't work ... - 6.3) In the edit menu the trust values is not displayed correctly after - signing uids - why? + 6.3) In the edit menu the trust values are not displayed correctly after + signing uids. Why? 6.4) What does "skipping pubkey 1: already loaded" mean? 6.5) GnuPG 1.0.4 doesn't create ~/.gnupg ... 6.6) An ElGamal signature does not verify anymore since version 1.0.2 ... @@ -83,14 +87,17 @@ search in the mailing list archive. 6.9) What is the thing with "can't handle multiple signatures"? 6.10) If I submit a key to a keyserver, nothing happens ... 6.11) I get "gpg: waiting for lock ..." - 6.12) Older gpg's (e.g., 1.0) have problems with keys from newer gpgs ... + 6.12) Older gpg binaries (e.g., 1.0) have problems with keys from newer + gpg binaries ... 6.13) With 1.0.4, I get "this cipher algorithm is deprecated ..." - 6.14) Some dates are displayed as ????-??-??, why? + 6.14) Some dates are displayed as ????-??-??. Why? 6.15) I still have a problem. How do I report a bug? - 6.16) Why doesn't GnuPG support X509 certificates? + 6.16) Why doesn't GnuPG support X.509 certificates? 6.17) Why do national characters in my user ID look funny? 6.18) I get 'sed' errors when running ./configure on Mac OS X ... 6.19) Why does GnuPG 1.0.6 bail out on keyrings used with 1.0.7? + 6.20) I've upgraded to GnuPG version 1.0.7 and now it takes longer to load + my keyrings. What can I do? 7. ADVANCED TOPICS 7.1) How does this whole thing work? @@ -121,30 +128,39 @@ search in the mailing list archive. 1.2) 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 5.1 for details. + the OpenPGP standard. But there are some interoperability problems. + See question 5.1 for details. + +1.3) 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. 2. SOURCES of INFORMATION -2.1) Where can I find more information? +2.1) Where can I find more information on GnuPG? - Here's a list of on-line resources: + On-line resources: The documentation page is located at . - 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. - On you'll find an online archive of the + At 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.: - GnuPG-users: , - GnuPG-devel: . + gnupg-users: , + gnupg-devel: . *PLEASE:* Before posting to a list, read this FAQ and the available @@ -154,7 +170,7 @@ search in the mailing list archive. The GnuPG source distribution contains a subdirectory: - ./doc + ./doc where some additional documentation is located (mainly interesting for hackers, not the casual user). @@ -162,24 +178,26 @@ search in the mailing list archive. 2.2) Where do I get GnuPG? You can download the GNU Privacy Guard from its primary FTP server - ftp.gnupg.org or from one of the mirrors: + or from one of the mirrors: - + - 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. 3. INSTALLATION 3.1) 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: - + -3.2) Which random gatherer should I use? +3.2) 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 @@ -188,61 +206,61 @@ search in the mailing list archive. systems. Also Solaris users with the SUNWski package installed have a /dev/random. In these cases, use the configure option: - --enable-static-rnd=linux + --enable-static-rnd=linux In addition, there's also the kernel random device by Andi Maier - , but it's still beta. Use at your + , 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 - to obtain egd. Use: + to obtain EGD. Use: - --enable-static-rnd=egd + --enable-static-rnd=egd here. If the above options do not work, you can use the random number - generator "unix". This is *very* slow and should be avoiced. The + generator "unix". This is *very* slow and should be avoided. The random quality isn't very good so don't use it on sensitive data. 3.3) 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 . Look for: - idea.c + idea.c - 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: - load-extension idea + load-extension idea 4. USAGE 4.1) 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: - gpg --fingerprint + gpg --fingerprint 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 @@ -270,12 +288,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. @@ -290,49 +308,53 @@ search in the mailing list archive. 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: - gpg [--option something] [--option2] [--option3 something] --command file + gpg [--option something] [--option2] [--option3 something] --command file 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: - gpg -r alice -o secret.txt -e test.txt + gpg -r alice -o secret.txt -e test.txt If you write the options out in full, it is easier to read: - gpg --recipient alice --output secret.txt --encrypt test.txt + gpg --recipient alice --output secret.txt --encrypt test.txt - 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: - gpg --armor --recipient alice --output secret.txt --encrypt test.txt + gpg --armor --recipient alice --output secret.txt --encrypt test.txt If you imagine square brackets around the optional parts, it becomes a bit clearer: - gpg [--armor] [--recipient alice] [--output secret.txt] --encrypt test.txt + gpg [--armor] [--recipient alice] [--output secret.txt] --encrypt test.txt The optional parts can be rearranged any way you want: - gpg --output secret.txt --recipient alice --armor --encrypt test.txt + gpg --output secret.txt --recipient alice --armor --encrypt test.txt 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". *The exception:* 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". - gpg [--options] --sign --encrypt foo.txt + *The exception to using only one command:* signing and encrypting + at the same time. For this you can combine both commands, such as in: -4.5) I can't delete a user ID because it is already deleted on my public - keyring? + gpg [--options] --sign --encrypt foo.txt + +4.5) 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 @@ -341,43 +363,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. -4.6) I can't delete the secret key because my public key disappeared? +4.6) 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"). 4.7) 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. 4.8) 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). 4.9) 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". @@ -389,54 +414,57 @@ search in the mailing list archive. 4.11) 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. 4.12) How can a get list of key IDs used to encrypt a message? - 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 }' -4.13) I can't decrypt my symmetrical only (-c) encrypted message with +4.13) 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. 4.14) 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: - If you want to do automatic signing, create a signing - subkey for your key (edit menu, choose "addkey" and the DSA). + 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). Make sure that you use a passphrase (needed by the current implementation). gpg --export-secret-subkeys --no-comment foo >secring.auto Copy secring.auto and the public keyring to a test directory. Change to this directory. 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. Copy secring.auto to a floppy and carry it to the target box. On the target machine: - Install secring.auto as secret keyring. - Now you can start your new service. It is a good idea to - install some intrusion detection system so that you hopefully + Install secring.auto as the secret keyring. + 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. @@ -444,26 +472,69 @@ search in the mailing list archive. 4.15) 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. - - The following list is probably not exhaustive: + as the capabilities of your addressee. As well, support may be + native to the MUA, or provided via "plug-ins" or external tools. - 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. + The following list is not exhaustive: - ASCII: Emacs/{VM,GNUS}/MailCrypt, Mutt(Unix), Pine(Unix), and - probably many more. - - Good overviews of OpenPGP-support can be found at - http://cryptorights.org/pgp-users/pgp-mail-clients.html - and http://www.geocities.com/openpgp/courrier_en.html. + 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 + + 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. + + 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) + + Good overviews of OpenPGP-support can be found at: + , + and + . 4.16) Can't we have a gpg library? @@ -471,7 +542,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 ftp://ftp.guug.de/pub/gcrypt/alpha/gpgme. + trick. You'll find it at . 4.17) I have successfully generated a revocation certificate, but I don't understand how to send it to the key servers. @@ -479,11 +550,11 @@ search in the mailing list archive. Most keyservers don't accept a 'bare' revocation certificate. You have to import the certificate into gpg first: - gpg --import my-revocation.asc + gpg --import my-revocation.asc then send the revoked key to the keyservers: - gpg --keyserver certserver.pgp.com --send-keys mykeyid + gpg --keyserver certserver.pgp.com --send-keys mykeyid (or use a keyserver web interface for this). @@ -496,7 +567,7 @@ search in the mailing list archive. If you want to put your keyrings somewhere else, use: - --homedir /my/path/ + --homedir /my/path/ 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 @@ -515,7 +586,7 @@ search in the mailing list archive. supported by GnuPG as it is patented (see 3.3), but if you have a modified version of PGP you can try this: - gpg --rfc1991 --cipher-algo 3des ... + gpg --rfc1991 --cipher-algo 3des ... 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. @@ -525,12 +596,12 @@ search in the mailing list archive. PGP 5.x and higher You need to provide two additional options: - --compress-algo 1 --cipher-algo cast5 + --compress-algo 1 --cipher-algo cast5 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: - compress-algo 1 + compress-algo 1 into your ~/.gnupg/options file - this does not affect normal GnuPG operation. @@ -544,7 +615,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 3.3 about how to add IDEA support to GnuPG and read - http://www.gnupg.org/gph/en/pgp2x.html to perform the migration. + to perform the migration. 5.3) (removed) @@ -572,7 +643,7 @@ search in the mailing list archive. There is a script in the tools directory to help you. After you have imported the PGP keyring you can give this command: - $ lspgpot pgpkeyring | gpg --import-ownertrust + $ lspgpot pgpkeyring | gpg --import-ownertrust where pgpkeyring is the original keyring and not the GnuPG keyring you might have created in the first step. @@ -584,7 +655,7 @@ search in the mailing list archive. PGP is not really OpenPGP aware. A workaround is to export the secret keys with this command: - $ gpg --export-secret-keys --no-comment -a your-key-id + $ gpg --export-secret-keys --no-comment -a your-key-id Another possibility is this: by default, GnuPG encrypts your secret key using the Blowfish symmetric algorithm. Older PGPs will only @@ -592,8 +663,8 @@ search in the mailing list archive. following method you can re-encrypt your secret gpg key with a different algo: - $ gpg --s2k-cipher-algo=CAST5 --s2k-digest-algo=SHA1 \ - --compress-algo=1 --edit-key + $ gpg --s2k-cipher-algo=CAST5 --s2k-digest-algo=SHA1 \ + --compress-algo=1 --edit-key Then use passwd to change the password (just change it to the same thing, but it will encrypt the key with CAST5 this time). @@ -602,8 +673,16 @@ search in the mailing list archive. For PGP 6.x the following options work to export a key: - $ gpg --s2k-cipher-algo 3des --compress-algo 1 --rfc1991 \ - --export-secret-keys + $ gpg --s2k-cipher-algo 3des --compress-algo 1 --rfc1991 \ + --export-secret-keys + +5.8) 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. 6. PROBLEMS and ERROR MESSAGES @@ -617,22 +696,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: + + chmod u+s /path/to/gpg + + or + + chmod 4755 /path/to/gpg + + 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: - filepriv -f plock /path/to/gpg + filepriv -f plock /path/to/gpg If you can't or don't want to install GnuPG setuid(root), you can use the option "--no-secmem-warning" or put: - no-secmem-warning + no-secmem-warning in your ~/.gnupg/options 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: - gpg: Please note that you don't have secure memory + gpg: Please note that you don't have secure memory 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 @@ -640,14 +731,14 @@ search in the mailing list archive. 6.2) 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. -6.3) In the edit menu the trust values is not displayed correctly after - signing uids - why? +6.3) 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 @@ -703,23 +794,24 @@ search in the mailing list archive. 6.11) 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. -6.12) Older gpg's (e.g., 1.0) have problems with keys from newer gpgs ... +6.12) 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: - cipher-algo cast5 + cipher-algo cast5 into your options file. @@ -730,10 +822,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. -6.14) Some dates are displayed as ????-??-??, why? +6.14) 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. @@ -745,13 +837,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 - http://bugs.guug.de/Reporting.html. + . -6.16) Why doesn't GnuPG support X509 certificates? +6.16) 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. @@ -771,7 +863,7 @@ search in the mailing list archive. Until then, find the line setting CDPATH in the configure script and place a: - unset CDPATH + unset CDPATH statement below it. @@ -780,7 +872,15 @@ search in the mailing list archive. 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: - http://www.gnupg.org/developer/gpg-woody-fix.txt + http://www.gnupg.org/developer/gpg-woody-fix.txt + +6.20) 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. 7. ADVANCED TOPICS @@ -789,7 +889,7 @@ search in the mailing list archive. To generate a secret/public keypair, run: - gpg --gen-key + gpg --gen-key and choose the default values. @@ -802,7 +902,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 @@ -836,11 +936,11 @@ search in the mailing list archive. person it says it comes from. You should be very sure that is really that person: You should verify the key fingerprint with: - gpg --fingerprint user-id + gpg --fingerprint user-id - 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 @@ -877,37 +977,37 @@ search in the mailing list archive. You can see the validity (calculated trust value) using this command. - gpg --list-keys --with-colons + gpg --list-keys --with-colons If the first field is "pub" or "uid", the second field shows you the trust: - 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 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: - gpg --list-ownertrust + gpg --list-ownertrust The first field is the fingerprint of the primary key, the second field is the assigned value: - - = 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. Keep these values confidential because they express your opinions about others. PGP stores this information with the keyring thus it @@ -928,18 +1028,18 @@ search in the mailing list archive. information which is prefixed with information about the checked item. - "key 12345678.3456" + "key 12345678.3456" 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. - "uid 12345678.3456/ACDE" + "uid 12345678.3456/ACDE" 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. - "sig 12345678.3456/ACDE/9A8B7C6D" + "sig 12345678.3456/ACDE/9A8B7C6D" 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 diff -urpP gnupg-1.2.0/doc/Makefile.in gnupg-1.2.1/doc/Makefile.in --- gnupg-1.2.0/doc/Makefile.in Sat Sep 21 10:35:34 2002 +++ gnupg-1.2.1/doc/Makefile.in Fri Oct 25 10:07:12 2002 @@ -95,6 +95,7 @@ DEPDIR = @DEPDIR@ DLLTOOL = @DLLTOOL@ DOCBOOK_TO_MAN = @DOCBOOK_TO_MAN@ DOCBOOK_TO_TEXI = @DOCBOOK_TO_TEXI@ +EGDLIBS = @EGDLIBS@ FAQPROG = @FAQPROG@ GENCAT = @GENCAT@ GLIBC21 = @GLIBC21@ diff -urpP gnupg-1.2.0/doc/README.W32 gnupg-1.2.1/doc/README.W32 --- gnupg-1.2.0/doc/README.W32 Sun Jun 30 10:02:57 2002 +++ gnupg-1.2.1/doc/README.W32 Fri Oct 25 09:46:38 2002 @@ -1,4 +1,5 @@ -This is a binary version of GnuPG for MS-Windows 95, 98, WNT and W2000. +This is a binary version of GnuPG for MS-Windows 95, 98, WNT, W2000 +and XP. A FAQ comes with this package and a probably more recent one can be found online at http://www.gnupg.org/faq.html. See @@ -9,8 +10,8 @@ questions - but please read the FAQ firs Installation instructions: -------------------------- 1. Unpack the ZIP archive (alright, you already did this). - 2. Copy "gpg.exe" and "gpgv.exe" to some place where you - usually store your binaries. + 2. Copy "gpg.exe", "gpgv.exe" and "gpgkeys_ldap.exe" to a place + where you usually store your binaries. 3. Create a directory "c:\gnupg" (or any other as you like) 4. If you did not use the default directory "c:\gnupg", you should enter a string with the directory into the Registry @@ -72,7 +73,7 @@ Instructions are at the top of this file To build it, you need the MingW32/CPD kit, which is available at - ftp://ftp.gnupg.org/people/werner/cpd/mingw32-cpd-0.3.0.tar.gz + ftp://ftp.gnupg.org/people/werner/cpd/mingw32-cpd-0.3.2.tar.gz ftp://ftp.gnupg.org/people/werner/cpd/gcc-core-2.95.2.tar.gz ftp://ftp.gnupg.org/people/werner/cpd/binutils-2.9.1.tar.gz @@ -86,8 +87,11 @@ After you have installed this environmen $ mingw32 strip g10/gpg.exe $ cp g10/gpg.exe /some_windows_drive/ -And everything hopefully works. - +And everything hopefully works. If there is a make problem in the +"po" directory you can eiterignore it or do a "touch po/all". To +build the distribtion ZIP file, you have to create a directory +"dist-w32" and run "scripts/mk-w32-dist" right after a successul make +run. Don't forget that MS-Windows ist just a temporary workaround until you can switch to a GNU system ;-) @@ -95,6 +99,3 @@ you can switch to a GNU system ;-) Be the source always with you. Werner - - - diff -urpP gnupg-1.2.0/doc/faq.html gnupg-1.2.1/doc/faq.html --- gnupg-1.2.0/doc/faq.html Fri Sep 20 17:10:37 2002 +++ gnupg-1.2.1/doc/faq.html Thu Oct 17 12:47:51 2002 @@ -7,8 +7,8 @@

-Version: 1.5.7
-Last-Modified: Aug 21, 2002
+Version: 1.5.8
+Last-Modified: Oct 8, 2002
Maintained-by: David D. Scribner, <faq 'at' gnupg.org>

@@ -16,17 +16,17 @@ Maintained-by: David D. Scribner, <fa This is the GnuPG FAQ. The latest HTML version is available here.

-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.

@@ -36,9 +36,11 @@ search in the mailing list archive.
  • 1.2) Is GnuPG compatible with PGP? +
  • 1.3) Is GnuPG free to use for personal or commercial use? +

    2. SOURCES of INFORMATION

    -
  • 2.1) Where can I find more information? +
  • 2.1) Where can I find more information on GnuPG?
  • 2.2) Where do I get GnuPG? @@ -46,7 +48,7 @@ search in the mailing list archive.
  • 3.1) Which OSes does GnuPG run on? -
  • 3.2) Which random gatherer should I use? +
  • 3.2) Which random data gatherer should I use?
  • 3.3) How do I include support for RSA and IDEA? @@ -60,10 +62,11 @@ search in the mailing list archive.
  • 4.4) What is the difference between options and commands? -
  • 4.5) I can't delete a user ID because it is already deleted on my public - keyring? +
  • 4.5) 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? -
  • 4.6) I can't delete the secret key because my public key disappeared? +
  • 4.6) I can't delete my secret key because the public key disappeared. + What can I do?
  • 4.7) What are trust, validity and ownertrust? @@ -78,7 +81,7 @@ search in the mailing list archive.
  • 4.12) How can a get list of key IDs used to encrypt a message? -
  • 4.13) I can't decrypt my symmetrical only (-c) encrypted message with +
  • 4.13) I can't decrypt my symmetrical-only (-c) encrypted messages with a new version of GnuPG.
  • 4.14) How can I use GnuPG in an automated environment? @@ -108,14 +111,17 @@ search in the mailing list archive.
  • 5.7) PGP does not like my secret key. +
  • 5.8) I just installed the most recent version of GnuPG and don't have a + ~/.gnupg/options file. Is this missing from the installation? +

    6. PROBLEMS and ERROR MESSAGES

  • 6.1) Why do I get "gpg: Warning: using insecure memory!"
  • 6.2) Large File Support doesn't work ... -
  • 6.3) In the edit menu the trust values is not displayed correctly after - signing uids - why? +
  • 6.3) In the edit menu the trust values are not displayed correctly after + signing uids. Why?
  • 6.4) What does "skipping pubkey 1: already loaded" mean? @@ -134,15 +140,16 @@ search in the mailing list archive.
  • 6.11) I get "gpg: waiting for lock ..." -
  • 6.12) Older gpg's (e.g., 1.0) have problems with keys from newer gpgs ... +
  • 6.12) Older gpg binaries (e.g., 1.0) have problems with keys from newer + gpg binaries ...
  • 6.13) With 1.0.4, I get "this cipher algorithm is deprecated ..." -
  • 6.14) Some dates are displayed as ????-??-??, why? +
  • 6.14) Some dates are displayed as ????-??-??. Why?
  • 6.15) I still have a problem. How do I report a bug? -
  • 6.16) Why doesn't GnuPG support X509 certificates? +
  • 6.16) Why doesn't GnuPG support X.509 certificates?
  • 6.17) Why do national characters in my user ID look funny? @@ -150,6 +157,9 @@ search in the mailing list archive.
  • 6.19) Why does GnuPG 1.0.6 bail out on keyrings used with 1.0.7? +
  • 6.20) I've upgraded to GnuPG version 1.0.7 and now it takes longer to load + my keyrings. What can I do? +

    7. ADVANCED TOPICS

  • 7.1) How does this whole thing work? @@ -195,8 +205,19 @@ As such, it is aimed to be compatible wi

    In general, yes. GnuPG and newer PGP releases should be implementing -the OpenPGP standard. But there are some interoperability -problems. See question 5.1 for details. +the OpenPGP standard. But there are some interoperability problems. +See question 5.1 for details. +

    +

    +1.3) 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.

    @@ -204,26 +225,26 @@ problems. See question 5.1

    -2.1) Where can I find more information? +2.1) Where can I find more information on GnuPG?

    -Here's a list of on-line resources: +On-line resources: