2 * Add some work arounds for a bugs in pgp 2 which led to bad signatures
3 when used with canoncial texts in some cases.
5 * Enhanced some status outputs.
8 Noteworthy changes in version 0.9.6
9 -----------------------------------
11 * Twofish is now statically linked by default. The experimental 128 bit
12 version is now disabled. Full support will be available as soon as
13 the OpenPGP WG has decided on an interpretation of rfc2440.
15 * Dropped support for the ancient Blowfish160 which is not OpenPGP.
17 * Merged gpgm and gpg into one binary.
19 * Add "revsig" and "revkey" commands to the edit menu. It is now
20 possible to revoke signature and subkeys.
23 Noteworthy changes in version 0.9.5
24 -----------------------------------
26 * New command "lsign" in the keyedit menu to create non-exportable
27 signatures. Removed --trusted-keys option.
29 * A bunch of changes to the key validation code.
31 * --list-trust-path now has an optional --with-colons format.
33 * New command --recv-keys to import keys from an keyserver.
36 Noteworthy changes in version 0.9.4
37 -----------------------------------
39 * New configure option --enable-static-rnd=[egd|linux|unix|none]
40 to select a random gathering module for static linking.
42 * The original text is now verbatim copied to a cleartext signed message.
44 * Bugfixes but there are still a couple of bugs.
47 Noteworthy changes in version 0.9.3
48 -----------------------------------
50 * Changed the internal design of getkey which now allows a
51 efficient lookup of multiple keys and add a word match mode.
53 * New options --[no-]encrypt-to.
55 * Some changes to the configure stuff. Switched to automake 1.4.
56 Removed intl/ from CVS, autogen.sh now uses gettextize.
58 * Preferences now include Twofish. Removed preference to Blowfish with
59 a special hack to suppress the "not listed in preferences" warning;
60 this is to allow us to switch completely to Twofish in the near future.
62 * Changed the locking stuff.
64 * Print all user ids of a good signature.
67 Noteworthy changes in version 0.9.2
68 -----------------------------------
70 * add some additional time warp checks.
72 * Option --keyserver and command --send-keys to utilize HKP servers.
74 * Upgraded to zlib 1.1.3 and fixed an inflate bug
76 * More cleanup on the cleartext signatures.
79 Noteworthy changes in version 0.9.1
80 -----------------------------------
82 * Polish language support.
84 * When querying the passphrase, the key ID of the primary key is
85 displayed along with the one of the used secondary key.
87 * Fixed a bug occurring when decrypting pgp 5 encrypted messages,
88 fixed an infinite loop bug in the 3DES code and in the code
89 which looks for trusted signatures.
91 * Fixed a bug in the mpi library which caused signatures not to
94 * Rewrote the handling of cleartext signatures; the code is now
95 better maintainable (I hope so).
97 * New status output VALIDSIG only for valid signatures together
98 with the fingerprint of the signer's key.
101 Noteworthy changes in version 0.9.0
102 -----------------------------------
104 * --export does now only exports rfc2440 compatible keys; the
105 old behaviour is available with --export-all.
106 Generation of v3 ElGamal (sign and encrypt) keys is not longer
109 * Fixed the uncompress bug.
111 * Rewrote the rndunix module. There are two environment variables
112 used for debugging now: GNUPG_RNDUNIX_DBG give the file to write
113 debugging information (use "-" for stdout) and if GNUPG_RNDUNIX_DBGALL
114 is set, all programs which are only tried are also printed.
116 * New option --escape-from-lines to "dash-escape" "From " lines to
117 prevent mailers to change them to ">From ". This is not enabled by
118 default because it is not in compliance with rfc2440 - however, you
122 Noteworthy changes in version 0.4.5
123 -----------------------------------
125 * The keyrings and the trustdb is now locked, so that
126 other GnuPG processes won't damage these files. You
127 may want to put the option --lock-once into your options file.
129 * The latest self-signatures are now used; this enables --import
130 to see updated preferences etc.
132 * Import of subkeys should now work.
134 * Random gathering modules may now be loaded as extensions. Add
135 such a module for most Unices but it is very experimental!
137 * Brazilian language support.
140 Noteworthy changes in version 0.4.4
141 -----------------------------------
143 * Fixed the way the key expiration time is stored. If you have
144 an expiration time on your key you should fix it with --edit-key
145 and the command "expire". I apologize for this inconvenience.
147 * Add option --charset to support "koi8-r" encoding of user ids.
150 * Preferences should now work again. You should run
151 "gpgm --check-trustdb \*" to rebuild all preferences.
153 * Checking of certificates should now work but this needs a lot
154 of testing. Key validation values are now cached in the
155 trustdb; they should be recalculated as needed, but you may
156 use --check-trustdb or --update-trustdb to do this.
158 * Spanish translation by Urko Lusa.
160 * Patch files are from now on signed. See the man page
161 for the new option --not-dash-escaped.
163 * New syntax: --edit-key <userID> [<commands>]
164 If you run it without --batch the commands are executed and then
165 you are put into normal mode unless you use "quit" or "save" as
166 one of the commands. When in batch mode, the program quits after
167 the last command, so you have to use "save" if you did some changes.
168 It does not yet work completely, but may be used to list so the
172 Noteworthy changes in version 0.4.3
173 -----------------------------------
175 * Fixed the gettext configure bug.
177 * Kludge for RSA keys: keyid and length of a RSA key are
178 correctly reported, but you get an error if you try to use
179 this key (If you do not have the non-US version).
181 * Experimental support for keyrings stored in a GDBM database.
182 This is *much* faster than a standard keyring. You will notice
183 that the import gets slower with time; the reason is that all
184 new keys are used to verify signatures of previous inserted
185 keys. Use "--keyring gnupg-gdbm:<name-of-gdbm-file>". This is
186 not (yet) supported for secret keys.
188 * A Russian language file in the distribution (alternatives are in
189 the contrib directory of the FTP servers)
191 * commandline option processing now works as expected for GNU programs
192 with the exception that you can't mix options and normal arguments.
194 * Now --list-key lists all matching keys. This is needed in some
198 Noteworthy changes in version 0.4.2
199 -----------------------------------
201 * This is only a snapshot: There are still a few bugs.
203 * Fixed this huge memory leak.
205 * Redesigned the trust database: You should run "gpgm --check-trustdb".
206 New command --update-trustdb, which adds new key from the public
207 keyring into your trustdb
209 * Fixed a bug in the armor code, leading to invalid packet errors.
210 (a workaround for this was to use --no-armor). The shorten line
211 length (64 instead of 72) fixes a problem with pgp5 and keyservers.
213 * comment packets are not anymore generated. "--export" filters
214 them out. One Exception: The comment packets in a secret keyring
215 are still used because they carry the factorization of the public
218 * --import now only looks for KEYBLOCK headers, so you can now simply
219 remove the "- " in front of such a header if someone accidently signed
220 such a message or the keyblock is part of a cleartext signed message.
222 * --with-colons now lists the key expiration time and not anymore
225 * Some keyblocks created with old releases have a wrong sequence
226 of packets, so that the keyservers don't accept these keys.
227 Simply using "--edit-key" fixes the problem.
229 * New option --force-v3-sigs to generate signed messages which are
232 * Add some code to support DLD (for non ELF systems) - but this is
233 not tested because my BSD box is currently broken.
235 * New command "expire" in the edit-key menu.
239 Noteworthy changes in version 0.4.1
240 -----------------------------------
241 * A secondary key is used when the primary key is specified but cannot
242 be used for the operation (if it is a sign-only key).
244 * GNUPG can now handle concatenated armored messages: There is still a
245 bug if different kinds of messages are mixed.
247 * Iterated+Salted passphrases now work. If want to be sure that PGP5
248 is able to handle them you may want to use the options
249 "--s2k-mode 3 --s2k-cipher-algo cast5 --s2k-digest-algo sha1"
250 when changing a passphrase.
252 * doc/OpenPGP talks about OpenPGP compliance, doc/HACKING gives
253 a few hints about the internal structure.
255 * Checked gnupg against the August 1998 draft (07) and I believe
256 it is in compliance with this document (except for one point).
258 * Fixed some bugs in the import merging code and rewrote some
259 code for the trustdb.
262 Noteworthy changes in version 0.4.0
263 -----------------------------------
264 * Triple DES is now supported. Michael Roth did this piece of
265 needed work. We have now all the coded needed to be OpenPGP
268 * Added a simple rpm spec file (see INSTALL).
270 * detached and armored signatures are now using "PGP SIGNATURE",
271 except when --rfc1991 is used.
273 * All times which are not in the yyy-mm-dd format are now printed
277 Noteworthy changes in version 0.3.5
278 -----------------------------------
279 * New option --throw-keyid to create anonymous enciphered messages.
280 If gpg detects such a message it tires all available secret keys
281 in turn so decode it. This is a gnupg extension and not in OpenPGP
282 but it has been discussed there and afaik some products use this
283 scheme too (Suggested by Nimrod Zimmerman).
285 * Fixed a bug with 5 byte length headers.
287 * --delete-[secret-]key is now also available in gpgm.
289 * cleartext signatures are not anymore converted to LF only.
291 * Fixed a trustdb problem. Run "gpgm --check-trustdb" to fix old
294 * Building in another directory should now work.
296 * Weak key detection mechanism (Niklas Hernaeus).
299 Noteworthy changes in version 0.3.4
300 -----------------------------------
301 * New options --comment and --set-filename; see g10/OPTIONS
303 * yes/no, y/n localized.
307 Noteworthy changes in version 0.3.3
308 -----------------------------------
309 * IMPORTANT: I found yet another bug in the way the secret keys
310 are encrypted - I did it the way pgp 2.x did it, but OpenPGP
311 and pgp 5.x specify another (in some aspects simpler) method.
312 To convert your secret keys you have to do this:
313 1. Build the new release but don't install it and keep
314 a copy of the old program.
315 2. Disable the network, make sure that you are the only
316 user, be sure that there are no Trojan horses etc ....
317 3. Use your old gpg (version 0.3.[12]) and set the
318 passphrases of ALL your secret keys to empty!
319 (gpg --change-passphrase your-user-id).
320 4. Save your ownertrusts (see the next point)
321 5. rm ~/.gnupg/trustdb.gpg
322 6. install the new version of gpg (0.3.3)
323 7. For every secret key call "gpg --edit-key your-user-id",
324 enter "passwd" at the prompt, follow the instructions and
325 change your password back, enter "save" to store it.
326 8. Restore the ownertrust (see next point).
328 * The format of the trust database has changed; you must delete
329 the old one, so gnupg can create a new one.
330 IMPORTANT: Use version 0.3.[12] to save your assigned ownertrusts
331 ("gpgm --list-ownertrust >saved-trust"); then build this new version
332 and restore the ownertrust with this new version
333 ("gpgm --import-ownertrust saved-trust"). Please note that
334 --list-ownertrust has been renamed to --export-ownertrust in this
335 release and it does now only export defined ownertrusts.
337 * The command --edit-key now provides a commandline driven menu
338 which can be used for various tasks. --sign-key is only an
339 an alias to --edit-key and maybe removed in future: use the
340 command "sign" of this new menu - you can select which user ids
343 * Alternate user ids can now be created an signed.
345 * Owner trust values can now be changed with --edit-key (trust)
347 * GNUPG can now run as a coprocess; this enables sophisticated
348 frontends. tools/shmtest.c is a simple sample implementation.
349 This needs some more work: all tty_xxx() are to be replaced
350 by cpr_xxx() and some changes in the display logics is needed.
352 * Removed options --gen-prime and --gen-random.
354 * Removed option --add-key; use --edit-key instead.
356 * Removed option --change-passphrase; use --edit-key instead.
358 * Signatures are now checked even if the output file could not
359 be created. Command "--verify" tries to find the detached data.
361 * gpg now disables core dumps.
363 * compress and symmetric cipher preferences are now used.
364 Because there is no 3DES yet, this is replaced by Blowfish.
366 * We have added the Twofish as an experimental cipher algorithm.
367 Many thanks to Matthew Skala for doing this work.
368 Twofish is the AES submission from Schneier et al.; see
369 "www.counterpane.com/twofish.html" for more information.
371 * Started with a help system: If you enter a question mark at some
372 prompt; you should get a specific help for this prompt.
374 * There is no more backup copy of the secret keyring.
376 * A lot of new bugs. I think this release is not as stable as
380 Noteworthy changes in version 0.3.2
381 -----------------------------------
382 * Fixed some bugs when using --textmode (-seat)
384 * Now displays the trust status of a positive verified message.
386 * Keyrings are now scanned in the sequence they are added with
387 --[secret-]keyring. Note that the default keyring is implicitly
388 added as the very first one unless --no-default-keyring is used.
390 * Fixed setuid and dlopen bug.
392 Noteworthy changes in version 0.3.1
393 -----------------------------------
394 * Partial headers are now written in the OpenPGP format if
395 a key in a v4 packet is used.
397 * Removed some unused options, removed the gnupg.sig stuff.
399 * Key lookup by name now returns a key which can be used for
402 * New options --list-ownertrust (gpgm) to make a backup copy
403 of the ownertrust values you assigned.
405 * clear signature headers are now in compliance with OpenPGP.
407 Noteworthy changes in version 0.3.0
408 -----------------------------------
410 * New option --emulate-checksum-bug. If your passphrase does not
411 work anymore, use this option and --change-passphrase to rewrite
414 * More complete v4 key support: Preferences and expiration time
415 is set into the self signature.
417 * Key generation defaults to DSA/ElGamal keys, so that new keys are
418 interoperable with pgp5
420 * DSA key generation is faster and key generation does not anymore
421 remove entropy from the random generator (the primes are public
422 parameters, so there is really no need for a cryptographic secure
423 prime number generator which we had used).
425 * A complete new structure for representing the key parameters.
427 * Removed most public key knowledge into the cipher library.
429 * Support for dynamic loading of new algorithms.
431 * Moved tiger to an extension module.
434 Noteworthy changes in version 0.2.19
435 ------------------------------------
437 * Replaced /dev/urandom in checks with new tool mk-tdata.
439 * Some assembler file cleanups; some more functions for the Alpha.
441 * Tiger has now the OpenPGP assigned number 6. Because the OID has
442 changed, old signatures using this algorithm can't be verified.
444 * gnupg now encrypts the compressed packed and not any longer in the
445 reverse order; anyway it can decrypt both versions. Thanks to Tom
446 for telling me this (not security related) bug.
448 * --add-key works and you are now able to generate subkeys.
450 * It is now possible to generate ElGamal keys in v4 packets to create
453 * Some new features for better integration into MUAs.
456 Noteworthy changes in version 0.2.18
457 ------------------------------------
459 * Splitted cipher/random.c, add new option "--disable-dev-random"
460 to configure to support the development of a random source for
461 other systems. Prepared sourcefiles rand-unix.c, rand-w32.c
462 and rand-dummy.c (which is used to allow compilation on systems
463 without a random source).
465 * Fixed a small bug in the key generation (it was possible that 48 bits
466 of a key were not taken from the random pool)
468 * Add key generation for DSA and v4 signatures.
470 * Add a function trap_unaligned(), so that a SIGBUS is issued on
471 Alphas and not the slow emulation code is used. And success: rmd160
474 * Enhanced the formatting facility of argparse and changed the use of
475 \r,\v to @ because gettext does not like it.
477 * New option "--compress-algo 1" to allow the creation of compressed
478 messages which are readable by PGP and "--print-md" (gpgm) to make
479 speed measurement easier.
482 Noteworthy changes in version 0.2.17
483 ------------------------------------
485 * Comment packets are now of private type 61.
487 * Passphrase code still used a 160 bit blowfish key, added a
488 silly workaround. Please change your passphrase again - sorry.
490 * Conventional encryption now uses a type 3 packet to describe the
493 * The new algorithm number for Blowfish is 20, 16 is still used for
494 encryption only; for signing it is only used when it is in a v3 packet,
495 so that GNUPG keys are still valid.
498 Noteworthy changes in version 0.2.16
499 ------------------------------------
501 * Add experimental support for the TIGER/192 message digest algorithm.
502 (But there is only a dummy ASN OID).
504 * Standard cipher is now Blowfish with 128 bit key in OpenPGP's CFB
505 mode. I renamed the old cipher to Blowfish160. Because the OpenPGP
506 group refused to assign me a number for Blowfish160, I have to
507 drop support for this in the future. You should use
508 "--change-passphrase" to recode your current passphrase with 128
512 Noteworthy changes in version 0.2.15
513 ------------------------------------
515 * Fixed a bug with the old checksum calculation for secret keys.
516 If you run the program without --batch, a warning does inform
517 you if your secret key needs to be converted; simply use
518 --change-passphrase to recalculate the checksum. Please do this
519 soon, as the compatible mode will be removed sometime in the future.
521 * CAST5 works (using the PGP's special CFB mode).
523 * Again somewhat more PGP 5 compatible.
525 * Some new test cases
527 Noteworthy changes in version 0.2.14
528 ------------------------------------
530 * Changed the internal handling of keyrings.
532 * Add support to list PGP 5 keyrings with subkeys
534 * Timestamps of signatures are now verified.
536 * A expiration time can now be specified during key generation.
538 * Some speedups for Blowfish and SHA-1, rewrote SHA-1 transform.
539 Reduced the amount of random bytes needed for key generation in
543 Noteworthy changes in version 0.2.13
544 ------------------------------------
546 * Verify of DSA signatures works.
548 * Re-implemented the slower random number generator.
551 Noteworthy changes in version 0.2.12
552 ------------------------------------
554 * --delete-key checks that there is no secret key. The new
555 option --delete-secret-key maybe used to delete a secret key.
557 * "-kv" now works as expected. Options "--list-{keys,sigs]"
558 and "--check-sigs" are now working.
560 * New options "--verify" and "--decrypt" to better support integration
561 into MUAs (partly done for Mutt).
563 * New option "--with-colons" to make parsing of key lists easier.
565 Noteworthy changes in version 0.2.11
566 ------------------------------------
568 * GPG now asks for a recipient's name if option "-r" is not used.
570 * If there is no good trust path, the program asks whether to use
571 the public keys anyway.
573 * "--delete-key" works for public keys. What semantics shall I use
574 when there is a secret key too? Delete the secret key or leave him
575 and auto-regenerate the public key, next time the secret key is used?
577 Noteworthy changes in version 0.2.10
578 ------------------------------------
580 * Code for the alpha is much faster (about 20 times); the data
581 was misaligned and the kernel traps this, so nearly all time
582 was used by system to trap the misalignments and to write
583 syslog messages. Shame on me and thanks to Ralph for
584 pointing me at this while drinking some beer yesterday.
586 * Changed some configure options and add an option
587 --disable-m-guard to remove the memory checking code
588 and to compile everything with optimization on.
590 * New environment variable GNUPGHOME, which can be used to set
591 another homedir than ~/.gnupg. Changed default homedir for
592 Windoze version to c:/gnupg.
594 * Fixed detached signatures; detached PGP signatures caused a SEGV.
596 * The Windoze version works (as usual w/o a strong RNG).
599 Noteworthy changes in version 0.2.9
600 -----------------------------------
604 * Added a simple man page.
606 * Switched to automake1.2f and a newer gettext.
608 Noteworthy changes in version 0.2.8
609 -----------------------------------
611 * Changed the name to GNUPG, the binaries are called gpg and gpgm.
612 You must rename rename the directory "~/.g10" to ~/.gnupg/, rename
613 {pub,sec}ring.g10 to {pub,sec}ring.gpg, trustdb.g10 to trustdb.gpg
614 and g10.sig to gnupg.sig.
616 * New or changed passphrases are now salted.
619 Noteworthy changes in version 0.2.7
620 -----------------------------------
622 * New command "gen-revoke" to create a key revocation certificate.
624 * New option "homedir" to set the homedir (which defaults to "~/.g10").
625 This directory is created if it does not exists (only the last
626 part of the name and not the complete hierarchy)
628 * Command "import" works. (Try: "finger gcrypt@ftp.guug.de|g10 --import")
630 * New commands "dearmor/enarmor" for g10maint. These are mainly
631 used for internal test purposes.
633 * Option --version now conforming to the GNU standards and lists
634 the available ciphers, message digests and public key algorithms.
636 * Assembler code for m68k (not tested).
638 * "make check" works.
640 Noteworthy changes in version 0.2.6
641 -----------------------------------
643 * Option "--export" works.
646 Noteworthy changes in version 0.2.5
647 -----------------------------------
649 * Added zlib for systems which don't have it.
650 Use "./configure --with-zlib" to link with the static version.
652 * Generalized some more functions and rewrote the encoding of
653 message digests into MPIs.
655 * Enhanced the checkit script
658 Noteworthy changes in version 0.2.4
659 -----------------------------------
661 * nearly doubled the speed of the ElGamal signature verification.
663 * backup copies of keyrings are created.
665 * assembler stuff for Pentium; gives about 15% better performance.
667 * fixed a lot of bugs.
670 Noteworthy changes in version 0.2.3
671 -----------------------------------
673 * Found a bug in the calculation of ELG fingerprints. This is now
674 fixed, but all existing fingerprints and keyids for ELG keys
675 are not any more valid.
677 * armor should now work; including clear signed text.
679 * moved some options to the new program g10maint
681 * It's now 64 bit clean and runs fine on an alpha--linux.
683 * Key generation is much faster now. I fixed this by using not
684 so strong random number for the primes (this was a bug because the
685 ElGamal primes are public parameters and it does not make sense
686 to generate them from strong random). The real secret is the x value
687 which is still generated from strong (okay: /dev/random) random bits.
689 * added option "--status-fd": see g10/OPTIONS
691 * We have secure memory on systems which support mlock().
692 It is not complete yet, because we do not have signal handler
693 which does a cleanup in very case.
694 We should also check the ulimit for the user in the case
695 that the admin does not have set a limit on locked pages.
697 * started with internationalization support.
699 * The logic to handle the web of trust is now implemented. It is
700 has some bugs; but I'm going to change the algorithm anyway.
701 It works by calculating the trustlevel on the fly. It may ask
702 you to provide trust parameters if the calculated trust probability
703 is too low. I will write a paper which discusses this new approach.
705 * a couple of changes to the configure script.
707 * New option "--quick-random" which uses a much quicker random
708 number generator. Keys generated while this option is in effect
709 are flags with "INSECURE!" in the user-id. This is a development
712 * Read support for new version packets (OpenPGP).
714 * Comment packets are now of correct OpenPGP type 16. Old comment
715 packets written by G10 are detected because they always start with
716 a hash which is an invalid version byte.
718 * The string "(INSECURE!)" is appended to a new user-id if this
719 is generated on a system without a good random number generator.