Preparing a release candidate.

AUTHORS

@@ -31,6 +31,10 @@ Jacobo Tarri'o Barreiro <jtarrio@iname.com> Translations [gl]
 
 Janusz Aleksander Urbanowicz <alex@bofh.torun.pl> Translations [po]
 
+Jedi Lin <Jedi@idej.org> Translations [zh-tw]
+
+Jouni Hiltunen <jouni.hiltunen@kolumbus.fi> Translations [fi]
+
 Magda Procha'zkova'  <magda@math.muni.cz> Translations [cs]
 
 Michael Roth  <mroth@nessie.de>  Assignment

ChangeLog

@@ -1,3 +1,9 @@
+2003-01-07  Werner Koch  <wk@gnupg.org>
+
+        Released 1.2.2rc1.
+	
+	* configure.ac (ALL_LINGUAS): Added fi and zh_TW.
+
 2003-01-06  David Shaw  <dshaw@jabberwocky.com>
 
 	* NEWS: Add notes about disabled keys and trustdb tweaks.

NEWS

@@ -25,6 +25,8 @@ Noteworthy changes in version 1.2.2 (unreleased)
     * Minor trustdb changes to make the trust calculations match
       common usage.
 
+    * New translations: Finnish and Traditional Chinese.
+
 
 Noteworthy changes in version 1.2.1 (2002-10-25)
 ------------------------------------------------

configure.ac

@@ -24,13 +24,14 @@ AC_PREREQ(2.52)
 
 # 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.2-cvs, bug-gnupg@gnu.org)
+AC_INIT(gnupg, 1.2.2rc1, 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.
 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"
+ALL_LINGUAS="ca cs da de eo el es et fi fr gl id it ja 
+             nl pl pt_BR pt sv tr zh_TW"
 
 PACKAGE=$PACKAGE_NAME
 VERSION=$PACKAGE_VERSION

doc/ChangeLog

@@ -1,3 +1,7 @@
+2003-01-07  David D. Scribner <dscribner@bigfoot.com>
+
+	* faq.raw: Update to version 1.6.1.  Applied by Werner Koch
+
 2003-01-06  David Shaw  <dshaw@jabberwocky.com>
 
 	* DETAILS: Document disabled flag in capabilities field.

doc/gpg.texi

@@ -477,6 +477,15 @@ Create ASCII armored output.
 @item -o, ---output @code{file}
 Write output to @code{file}.
 
+@item ---no-mangle-dos-filenames
+@itemx ---mangle-dos-filenames
+The Windows version of GPG replaces the extension of an output
+filename to avoid problems with filenames containing more than one
+dot. This is not necessary for newer Windows version and such
+---no-mangle-dos-filenames can be used to switch this feature off and 
+have GPG append the new extension. This otion has no effect on
+non-windows platforms.
+
 @item -u, ---local-user @code{name}
 Use @code{name} as the user ID to sign.
 This option is silently ignored for the list commands,
@@ -598,12 +607,24 @@ don't want to keep your secret keys (or one of them)
 online but still want to be able to check the validity of a given
 recipient's or signator's key. 
 
+@item ---trust-model @code{classic|always}
+Set what trust model GnuPG should follow. The models are:
+
+@table @asis
+@item classic
+This is the regular web-of-trust as used in PGP and GnuPG.
+
+@item always
+Skip key validation and assume that used keys are always fully
+trusted. You won't use this unless you have installed some external
+validation scheme. This option also suppresses the "[uncertain]" tag
+printed with signature checks when there is no evidence that the user
+ID is bound to the key.
+
+@end table
+
 @item ---always-trust
-Skip key validation and assume that used keys are always fully trusted.
+Identical to `---trust-model always'
-You won't use this unless you have installed some external validation
-scheme. This option also suppresses the "[uncertain]" tag printed
-with signature checks when there is no evidence that the user ID
-is bound to the key.
 
 @item ---keyserver @code{name}
 Use @code{name} as your keyserver. This is the server that ---recv-keys,
@@ -633,21 +654,19 @@ keyserver types, some common options are:
 
 @table @asis
 @item include-revoked
-When searching for a key, include keys that are marked on the
+When searching for a key with ---search-keys, include keys that are
-keyserver as revoked. Note that this option is always set when using
+marked on the keyserver as revoked. Note that this option is always
-the NAI HKP keyserver, as this keyserver does not differentiate
+set when using the NAI HKP keyserver, as this keyserver does not
-between revoked and unrevoked keys. When using the LDAP keyserver,
+differentiate between revoked and unrevoked keys.
-this applies to both searching (---search-keys) and receiving
-(---recv-keys).
 
 @item include-disabled
-When receiving or searching for a key, include keys that are marked on
+When searching for a key with ---search-keys, include keys that are
-the keyserver as disabled. Note that this option is not used with HKP
+marked on the keyserver as disabled. Note that this option is not
-keyservers, as they do not support disabling keys.
+used with HKP keyservers.
 
 @item include-subkeys
-When receiving a key, include subkeys in the search. Note that this
+When receiving a key, include subkeys as potential targets. Note that
-option is not used with HKP keyservers, as they do not support
+this option is not used with HKP keyservers, as they do not support
 retrieving keys by subkey id.
 
 @item use-temp-files
@@ -879,34 +898,53 @@ Force to write the version string in clear text
 signatures. Use this to overwrite a previous
 ---no-version from a config file.
 
-@item -N, ---notation-data @code{name=value}
+@item ---sig-notation @code{name=value}
+@itemx ---cert-notation @code{name=value}
+@itemx -N, ---notation-data @code{name=value}
 Put the name value pair into the signature as notation data.
-@code{name} must consist only of alphanumeric characters, digits
+@code{name} must consist only of printable characters or spaces, and
-or the underscore; the first character must not be a digit.
+must contain a '@@' character. This is to help prevent pollution of
-@code{value} may be any printable string; it will be encoded in UTF8,
+the IETF reserved notation namespace. The ---expert flag overrides the
-so you should check that your ---charset is set correctly.
+'@@' check. @code{value} may be any printable string; it will be
-If you prefix @code{name} with an exclamation mark, the notation
+encoded in UTF8, so you should check that your ---charset is set
-data will be flagged as critical (rfc2440:5.2.3.15).
+correctly. If you prefix @code{name} with an exclamation mark, the
+notation data will be flagged as critical (rfc2440:5.2.3.15).
+---sig-notation sets a notation for data signatures. --cert-notation
+sets a notation for key signatures (certifications). ---notation-data
+sets both.
+
+There are special codes that may be used in notation names. "%k" will
+be expanded into the key ID of the key being signed, "%K" for the long
+key ID of the key being signed, "%f" for the key fingerprint of the
+key being signed, "%s" for the key ID of the key making the signature,
+"%S" for the long key ID of the key making the signature, and "%%"
+results in a single "%". %k, %K, and %f are only meaningful when
+making a key signature (certification).
 
 @item ---show-notation
-Show key signature notations in the ---list-sigs or --check-sigs
+Show signature notations in the ---list-sigs or --check-sigs listings
-listings.
+as well as when verifying a signature with a notation in it.
 
 @item ---no-show-notation
-Do not show key signature notations in the ---list-sigs or --check-sigs
+Do not show signature notations.
-listings.
 
-@item ---set-policy-url @code{string}
+@item ---sig-policy-url @code{string}
-Use @code{string} as Policy URL for signatures (rfc2440:5.2.3.19).
+@itemx ---cert-policy-url @code{string}
-If you prefix it with an exclamation mark, the policy URL
+@itemx ---set-policy-url @code{string}
-packet will be flagged as critical.
+Use @code{string} as Policy URL for signatures (rfc2440:5.2.3.19). If
+you prefix it with an exclamation mark, the policy URL packet will be
+flagged as critical. ---sig-policy-url sets a a policy url for data
+signatures. ---cert-policy-url sets a policy url for key signatures
+(certifications). -set-policy-url sets both.
+
+The same %-expandos used for notation data are available here as well.
 
 @item ---show-policy-url
-Show any policy URLs set in the ---list-sigs or --check-sigs listings.
+Show policy URLs in the ---list-sigs or --check-sigs listings as well
+as when verifying a signature with a policy URL in it.
 
 @item ---no-show-policy-url
-Do not show any policy URLs set in the ---list-sigs or --check-sigs
+Do not show policy URLs.
-listings.
 
 @item ---set-filename @code{string}
 Use @code{string} as the name of file which is stored in
@@ -960,18 +998,16 @@ The default cipher is CAST5. This cipher is also used for
 conventional encryption if ---cipher-algo is not given.
 
 @item ---s2k-digest-algo @code{name}
-Use @code{name} as the digest algorithm used to mangle the
+Use @code{name} as the digest algorithm used to mangle the passphrases.
-passphrases. The default algorithm is RIPE-MD-160.
+The default algorithm is SHA-1. This digest algorithm is also used
-This digest algorithm is also used for conventional
+for conventional encryption if ---digest-algo is not given.
-encryption if ---digest-algo is not given.
 
 @item ---s2k-mode @code{n}
-Selects how passphrases are mangled. If @code{n} is 0
+Selects how passphrases are mangled. If @code{n} is 0 a plain
-a plain passphrase (which is not recommended) will be used,
+passphrase (which is not recommended) will be used, a 1 adds a salt to
-a 1 (default) adds a salt to the passphrase and
+the passphrase and a 3 (the default) iterates the whole process a
-a 3 iterates the whole process a couple of times.
+couple of times. Unless ---rfc1991 is used, this mode is also used for
-Unless ---rfc1991 is used, this mode is also used
+conventional encryption.
-for conventional encryption.
 
 @item ---simple-sk-checksum
 Secret keys are integrity protected by using a SHA-1 checksum. This
@@ -985,13 +1021,14 @@ happen is to change the passphrase on the key (even changing it to the
 same value is acceptable).
 
 @item ---compress-algo @code{n}
-Use compression algorithm @code{n}. Default is 2 which is RFC1950
+Use compression algorithm @code{n}. The value 2 is RFC1950 ZLIB
-compression. You may use 1 to use the old zlib version (RFC1951) which
+compression. The value 1 is RFC-1951 ZIP compression which is used by
-is used by PGP. 0 disables compression. The default algorithm may give
+PGP. 0 disables compression. If this option is not used, the default
-better results because the window size is not limited to 8K. If this
+behavior is to examine the recipient key preferences to see which
-is not used the OpenPGP behavior is used, i.e. the compression
+algorithms the recipient supports. If all else fails, ZIP is used for
-algorithm is selected from the preferences; note, that this can't be
+maximum compatibility. Note, however, that ZLIB may give better
-done if you do not encrypt the data.
+compression results if that is more important, as the compression
+window size is not limited to 8k.
 
 @item ---disable-cipher-algo @code{name}
 Never allow the use of @code{name} as cipher algorithm.
@@ -1094,9 +1131,9 @@ Resets the ---pgp2 option.
 Set up all options to be as PGP 6 compliant as possible. This
 restricts you to the ciphers IDEA (if the IDEA plugin is installed),
 3DES, and CAST5, the hashes MD5, SHA1 and RIPEMD160, and the
-compression algorithms none and ZIP. This also disables making
+compression algorithms none and ZIP. This also disables
-signatures with signing subkeys as PGP 6 does not understand
+---throw-keyid, and making signatures with signing subkeys as PGP 6
-signatures made by signing subkeys.
+does not understand signatures made by signing subkeys.
 
 This option implies `---disable-mdc --no-comment --escape-from-lines
 ---force-v3-sigs --no-ask-sig-expire --compress-algo 1'
@@ -1113,6 +1150,15 @@ TWOFISH.
 @item ---no-pgp7
 Resets the ---pgp7 option.
 
+@item ---pgp8
+Set up all options to be as PGP 8 compliant as possible. PGP 8 is a
+lot closer to the OpenPGP standard than previous versions of PGP, so
+all this does is disable ---throw-keyid and set --escape-from-lines and
+---compress-algo 1. The allowed algorithms list is the same as --pgp7.
+
+@item ---no-pgp8
+Resets the ---pgp8 option.
+
 @item ---openpgp
 Reset all packet, cipher and digest options to OpenPGP behavior. Use
 this option to reset all previous options like ---rfc1991,
@@ -1221,7 +1267,11 @@ enter batch mode.
 Suppress the warning about "using insecure memory".
 
 @item ---no-permission-warning
-Suppress the warning about unsafe file permissions.
+Suppress the warning about unsafe file permissions. Note that the
+file permission checks that GnuPG does are not intended to be
+authoritative, rather they simply warn about certain common permission
+problems. Do not assume that the lack of a warning means that your
+system is secure.
 
 @item ---no-mdc-warning
 Suppress the warning about missing MDC integrity protection.
@@ -1344,10 +1394,14 @@ Experimental use only.
 Sets up a named group, which is similar to aliases in email programs.
 Any time the group name is a receipient (-r or ---recipient), it will
 be expanded to the values specified.
+
 The values are @code{key IDs} or fingerprints, but any key description
 is accepted. Note that a value with spaces in it will be treated as
 two different values. Note also there is only one level of expansion
-- you cannot make an group that points to another group.
+- you cannot make an group that points to another group. When used
+from the command line, it may be necessary to quote the argument to
+this option to prevent the shell from treating it as multiple
+arguments.
 
 @item ---preserve-permissions
 Don't change the permissions of a secret keyring back to user
@@ -1539,6 +1593,30 @@ If you are going to verify detached signatures, make sure that the
 program knows about it; either be giving both filenames on the
 command line or using @samp{-} to specify stdin.
 
+@majorheading INTEROPERABILITY WITH OTHER OPENPGP PROGRAMS
+GnuPG tries to be a very flexible implementation of the OpenPGP
+standard. In particular, GnuPG implements many of the "optional"
+parts of the standard, such as the RIPEMD/160 hash, and the ZLIB
+compression algorithms. It is important to be aware that not all
+OpenPGP programs implement these optional algorithms and that by
+forcing their use via the ---cipher-algo, --digest-algo,
+---cert-digest-algo, or --compress-algo options in GnuPG, it is
+possible to create a perfectly valid OpenPGP message, but one that
+cannot be read by the intended recipient.
+
+For example, as of this writing, no version of official PGP supports
+the BLOWFISH cipher algorithm. If you use it, no PGP user will be
+able to decrypt your message. The same thing applies to the ZLIB
+compression algorithm. By default, GnuPG will do the right thing and
+create messages that are usable by any OpenPGP program. Only override
+this safe default if you know what you are doing.
+
+If you absolutely must override the safe default, you are far better
+off using the ---pgp2, --pgp6, or --pgp7 options. These options are
+safe as they do not force any particular algorithms in violation of
+OpenPGP, but rather reduce the available algorithms to a "PGP-safe"
+list.
+
 @majorheading BUGS
 On many systems this program should be installed as setuid(root). This
 is necessary to lock memory pages. Locking memory pages prevents the

g10/ChangeLog

@@ -5702,9 +5702,9 @@ Sat Jan 16 09:27:30 CET 1999  Werner Koch  <wk@isil.d.shuttle.de>
 	* g10.c: New option --keyserver
 	* mainproc.c (check_sig_and_print): Hook to import a pubkey.
 
-	* pref.c pref.h : Removed
+	* pref.c, pref.h : Removed
 
-	* hkp.c hkp.h: New
+	* hkp.c, hkp.h: New
 
 Wed Jan 13 14:10:15 CET 1999  Werner Koch  <wk@isil.d.shuttle.de>
 
@@ -7228,7 +7228,7 @@ Thu Feb 12 22:24:42 1998  Werner Koch  (wk@frodo)
 	* pubkey-enc.c (get_session_key): rewritten
 
 
- Copyright 1998,1999,2000,2001,2002 Free Software Foundation, Inc.
+ Copyright 1998,1999,2000,2001,2002,2003 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

g10/keydb.c

@@ -1,5 +1,5 @@
 /* keydb.c - key database dispatcher
- * Copyright (C) 2001, 2002 Free Software Foundation, Inc.
+ * Copyright (C) 2001, 2002, 2003 Free Software Foundation, Inc.
  *
  * This file is part of GnuPG.
  *

g10/openfile.c

@@ -1,5 +1,5 @@
 /* openfile.c
- * Copyright (C) 1998, 1999, 2000, 2001 Free Software Foundation, Inc.
+ * Copyright (C) 1998, 1999, 2000, 2001, 2003 Free Software Foundation, Inc.
  *
  * This file is part of GnuPG.
  *