1 Noteworthy changes in version 0.9.10
2 ------------------------------------
4 * Some strange new options to help pgpgpg
6 * Cleaned up the dox a bit.
9 Noteworthy changes in version 0.9.9
10 -----------------------------------
12 * New options --[no-]utf8-strings.
14 * New edit-menu commands "enable" and "disable" for entire keys.
16 * You will be asked for a filename if gpg cannot deduce one.
18 * Changes to support libtool which is needed for the development
21 * New script tools/lspgpot to help transferring assigned
22 trustvalues from PGP to GnuPG.
24 * New commands --lsign-key and made --sign-key a shortcut for --edit
27 * New options (#122--126 ;-) --[no-]default-recipient[-self],
28 --disable-{cipher,pubkey}-algo. See the man page.
30 * Enhanced info output in case of multiple recipients and fixed exit code.
32 * New option --allow-non-selfsigned-uid to work around a problem with
33 the German IN way of separating signing and encryption keys.
36 Noteworthy changes in version 0.9.8
37 -----------------------------------
39 * New subcommand "delsig" in the edit menu.
41 * The name of the output file is not anymore the one which is
42 embedded in the processed message, but the used filename with
43 the extension stripped. To revert to the old behaviour you can
44 use the option --use-embedded-filename.
46 * Another hack to cope with pgp2 generated detached signatures.
48 * latin-2 character set works (--charset=iso-8859-2).
50 * New option --with-key-data to list the public key parameters.
51 New option -N to insert notations and a --set-policy-url.
52 A couple of other options to allow reseting of options.
54 * Better support for HPUX.
57 Noteworthy changes in version 0.9.7
58 -----------------------------------
60 * Add some work arounds for a bugs in pgp 2 which led to bad signatures
61 when used with canoncial texts in some cases.
63 * Enhanced some status outputs.
65 Noteworthy changes in version 0.9.6
66 -----------------------------------
68 * Twofish is now statically linked by default. The experimental 128 bit
69 version is now disabled. Full support will be available as soon as
70 the OpenPGP WG has decided on an interpretation of rfc2440.
72 * Dropped support for the ancient Blowfish160 which is not OpenPGP.
74 * Merged gpgm and gpg into one binary.
76 * Add "revsig" and "revkey" commands to the edit menu. It is now
77 possible to revoke signature and subkeys.
80 Noteworthy changes in version 0.9.5
81 -----------------------------------
83 * New command "lsign" in the keyedit menu to create non-exportable
84 signatures. Removed --trusted-keys option.
86 * A bunch of changes to the key validation code.
88 * --list-trust-path now has an optional --with-colons format.
90 * New command --recv-keys to import keys from an keyserver.
93 Noteworthy changes in version 0.9.4
94 -----------------------------------
96 * New configure option --enable-static-rnd=[egd|linux|unix|none]
97 to select a random gathering module for static linking.
99 * The original text is now verbatim copied to a cleartext signed message.
101 * Bugfixes but there are still a couple of bugs.
104 Noteworthy changes in version 0.9.3
105 -----------------------------------
107 * Changed the internal design of getkey which now allows a
108 efficient lookup of multiple keys and add a word match mode.
110 * New options --[no-]encrypt-to.
112 * Some changes to the configure stuff. Switched to automake 1.4.
113 Removed intl/ from CVS, autogen.sh now uses gettextize.
115 * Preferences now include Twofish. Removed preference to Blowfish with
116 a special hack to suppress the "not listed in preferences" warning;
117 this is to allow us to switch completely to Twofish in the near future.
119 * Changed the locking stuff.
121 * Print all user ids of a good signature.
124 Noteworthy changes in version 0.9.2
125 -----------------------------------
127 * add some additional time warp checks.
129 * Option --keyserver and command --send-keys to utilize HKP servers.
131 * Upgraded to zlib 1.1.3 and fixed an inflate bug
133 * More cleanup on the cleartext signatures.
136 Noteworthy changes in version 0.9.1
137 -----------------------------------
139 * Polish language support.
141 * When querying the passphrase, the key ID of the primary key is
142 displayed along with the one of the used secondary key.
144 * Fixed a bug occurring when decrypting pgp 5 encrypted messages,
145 fixed an infinite loop bug in the 3DES code and in the code
146 which looks for trusted signatures.
148 * Fixed a bug in the mpi library which caused signatures not to
151 * Rewrote the handling of cleartext signatures; the code is now
152 better maintainable (I hope so).
154 * New status output VALIDSIG only for valid signatures together
155 with the fingerprint of the signer's key.
158 Noteworthy changes in version 0.9.0
159 -----------------------------------
161 * --export does now only exports rfc2440 compatible keys; the
162 old behaviour is available with --export-all.
163 Generation of v3 ElGamal (sign and encrypt) keys is not longer
166 * Fixed the uncompress bug.
168 * Rewrote the rndunix module. There are two environment variables
169 used for debugging now: GNUPG_RNDUNIX_DBG give the file to write
170 debugging information (use "-" for stdout) and if GNUPG_RNDUNIX_DBGALL
171 is set, all programs which are only tried are also printed.
173 * New option --escape-from-lines to "dash-escape" "From " lines to
174 prevent mailers to change them to ">From ". This is not enabled by
175 default because it is not in compliance with rfc2440 - however, you
179 Noteworthy changes in version 0.4.5
180 -----------------------------------
182 * The keyrings and the trustdb is now locked, so that
183 other GnuPG processes won't damage these files. You
184 may want to put the option --lock-once into your options file.
186 * The latest self-signatures are now used; this enables --import
187 to see updated preferences etc.
189 * Import of subkeys should now work.
191 * Random gathering modules may now be loaded as extensions. Add
192 such a module for most Unices but it is very experimental!
194 * Brazilian language support.
197 Noteworthy changes in version 0.4.4
198 -----------------------------------
200 * Fixed the way the key expiration time is stored. If you have
201 an expiration time on your key you should fix it with --edit-key
202 and the command "expire". I apologize for this inconvenience.
204 * Add option --charset to support "koi8-r" encoding of user ids.
207 * Preferences should now work again. You should run
208 "gpgm --check-trustdb \*" to rebuild all preferences.
210 * Checking of certificates should now work but this needs a lot
211 of testing. Key validation values are now cached in the
212 trustdb; they should be recalculated as needed, but you may
213 use --check-trustdb or --update-trustdb to do this.
215 * Spanish translation by Urko Lusa.
217 * Patch files are from now on signed. See the man page
218 for the new option --not-dash-escaped.
220 * New syntax: --edit-key <userID> [<commands>]
221 If you run it without --batch the commands are executed and then
222 you are put into normal mode unless you use "quit" or "save" as
223 one of the commands. When in batch mode, the program quits after
224 the last command, so you have to use "save" if you did some changes.
225 It does not yet work completely, but may be used to list so the
229 Noteworthy changes in version 0.4.3
230 -----------------------------------
232 * Fixed the gettext configure bug.
234 * Kludge for RSA keys: keyid and length of a RSA key are
235 correctly reported, but you get an error if you try to use
236 this key (If you do not have the non-US version).
238 * Experimental support for keyrings stored in a GDBM database.
239 This is *much* faster than a standard keyring. You will notice
240 that the import gets slower with time; the reason is that all
241 new keys are used to verify signatures of previous inserted
242 keys. Use "--keyring gnupg-gdbm:<name-of-gdbm-file>". This is
243 not (yet) supported for secret keys.
245 * A Russian language file in the distribution (alternatives are in
246 the contrib directory of the FTP servers)
248 * commandline option processing now works as expected for GNU programs
249 with the exception that you can't mix options and normal arguments.
251 * Now --list-key lists all matching keys. This is needed in some
255 Noteworthy changes in version 0.4.2
256 -----------------------------------
258 * This is only a snapshot: There are still a few bugs.
260 * Fixed this huge memory leak.
262 * Redesigned the trust database: You should run "gpgm --check-trustdb".
263 New command --update-trustdb, which adds new key from the public
264 keyring into your trustdb
266 * Fixed a bug in the armor code, leading to invalid packet errors.
267 (a workaround for this was to use --no-armor). The shorten line
268 length (64 instead of 72) fixes a problem with pgp5 and keyservers.
270 * comment packets are not anymore generated. "--export" filters
271 them out. One Exception: The comment packets in a secret keyring
272 are still used because they carry the factorization of the public
275 * --import now only looks for KEYBLOCK headers, so you can now simply
276 remove the "- " in front of such a header if someone accidently signed
277 such a message or the keyblock is part of a cleartext signed message.
279 * --with-colons now lists the key expiration time and not anymore
282 * Some keyblocks created with old releases have a wrong sequence
283 of packets, so that the keyservers don't accept these keys.
284 Simply using "--edit-key" fixes the problem.
286 * New option --force-v3-sigs to generate signed messages which are
289 * Add some code to support DLD (for non ELF systems) - but this is
290 not tested because my BSD box is currently broken.
292 * New command "expire" in the edit-key menu.
296 Noteworthy changes in version 0.4.1
297 -----------------------------------
298 * A secondary key is used when the primary key is specified but cannot
299 be used for the operation (if it is a sign-only key).
301 * GNUPG can now handle concatenated armored messages: There is still a
302 bug if different kinds of messages are mixed.
304 * Iterated+Salted passphrases now work. If want to be sure that PGP5
305 is able to handle them you may want to use the options
306 "--s2k-mode 3 --s2k-cipher-algo cast5 --s2k-digest-algo sha1"
307 when changing a passphrase.
309 * doc/OpenPGP talks about OpenPGP compliance, doc/HACKING gives
310 a few hints about the internal structure.
312 * Checked gnupg against the August 1998 draft (07) and I believe
313 it is in compliance with this document (except for one point).
315 * Fixed some bugs in the import merging code and rewrote some
316 code for the trustdb.
319 Noteworthy changes in version 0.4.0
320 -----------------------------------
321 * Triple DES is now supported. Michael Roth did this piece of
322 needed work. We have now all the coded needed to be OpenPGP
325 * Added a simple rpm spec file (see INSTALL).
327 * detached and armored signatures are now using "PGP SIGNATURE",
328 except when --rfc1991 is used.
330 * All times which are not in the yyy-mm-dd format are now printed
334 Noteworthy changes in version 0.3.5
335 -----------------------------------
336 * New option --throw-keyid to create anonymous enciphered messages.
337 If gpg detects such a message it tires all available secret keys
338 in turn so decode it. This is a gnupg extension and not in OpenPGP
339 but it has been discussed there and afaik some products use this
340 scheme too (Suggested by Nimrod Zimmerman).
342 * Fixed a bug with 5 byte length headers.
344 * --delete-[secret-]key is now also available in gpgm.
346 * cleartext signatures are not anymore converted to LF only.
348 * Fixed a trustdb problem. Run "gpgm --check-trustdb" to fix old
351 * Building in another directory should now work.
353 * Weak key detection mechanism (Niklas Hernaeus).
356 Noteworthy changes in version 0.3.4
357 -----------------------------------
358 * New options --comment and --set-filename; see g10/OPTIONS
360 * yes/no, y/n localized.
364 Noteworthy changes in version 0.3.3
365 -----------------------------------
366 * IMPORTANT: I found yet another bug in the way the secret keys
367 are encrypted - I did it the way pgp 2.x did it, but OpenPGP
368 and pgp 5.x specify another (in some aspects simpler) method.
369 To convert your secret keys you have to do this:
370 1. Build the new release but don't install it and keep
371 a copy of the old program.
372 2. Disable the network, make sure that you are the only
373 user, be sure that there are no Trojan horses etc ....
374 3. Use your old gpg (version 0.3.[12]) and set the
375 passphrases of ALL your secret keys to empty!
376 (gpg --change-passphrase your-user-id).
377 4. Save your ownertrusts (see the next point)
378 5. rm ~/.gnupg/trustdb.gpg
379 6. install the new version of gpg (0.3.3)
380 7. For every secret key call "gpg --edit-key your-user-id",
381 enter "passwd" at the prompt, follow the instructions and
382 change your password back, enter "save" to store it.
383 8. Restore the ownertrust (see next point).
385 * The format of the trust database has changed; you must delete
386 the old one, so gnupg can create a new one.
387 IMPORTANT: Use version 0.3.[12] to save your assigned ownertrusts
388 ("gpgm --list-ownertrust >saved-trust"); then build this new version
389 and restore the ownertrust with this new version
390 ("gpgm --import-ownertrust saved-trust"). Please note that
391 --list-ownertrust has been renamed to --export-ownertrust in this
392 release and it does now only export defined ownertrusts.
394 * The command --edit-key now provides a commandline driven menu
395 which can be used for various tasks. --sign-key is only an
396 an alias to --edit-key and maybe removed in future: use the
397 command "sign" of this new menu - you can select which user ids
400 * Alternate user ids can now be created an signed.
402 * Owner trust values can now be changed with --edit-key (trust)
404 * GNUPG can now run as a coprocess; this enables sophisticated
405 frontends. tools/shmtest.c is a simple sample implementation.
406 This needs some more work: all tty_xxx() are to be replaced
407 by cpr_xxx() and some changes in the display logics is needed.
409 * Removed options --gen-prime and --gen-random.
411 * Removed option --add-key; use --edit-key instead.
413 * Removed option --change-passphrase; use --edit-key instead.
415 * Signatures are now checked even if the output file could not
416 be created. Command "--verify" tries to find the detached data.
418 * gpg now disables core dumps.
420 * compress and symmetric cipher preferences are now used.
421 Because there is no 3DES yet, this is replaced by Blowfish.
423 * We have added the Twofish as an experimental cipher algorithm.
424 Many thanks to Matthew Skala for doing this work.
425 Twofish is the AES submission from Schneier et al.; see
426 "www.counterpane.com/twofish.html" for more information.
428 * Started with a help system: If you enter a question mark at some
429 prompt; you should get a specific help for this prompt.
431 * There is no more backup copy of the secret keyring.
433 * A lot of new bugs. I think this release is not as stable as
437 Noteworthy changes in version 0.3.2
438 -----------------------------------
439 * Fixed some bugs when using --textmode (-seat)
441 * Now displays the trust status of a positive verified message.
443 * Keyrings are now scanned in the sequence they are added with
444 --[secret-]keyring. Note that the default keyring is implicitly
445 added as the very first one unless --no-default-keyring is used.
447 * Fixed setuid and dlopen bug.
449 Noteworthy changes in version 0.3.1
450 -----------------------------------
451 * Partial headers are now written in the OpenPGP format if
452 a key in a v4 packet is used.
454 * Removed some unused options, removed the gnupg.sig stuff.
456 * Key lookup by name now returns a key which can be used for
459 * New options --list-ownertrust (gpgm) to make a backup copy
460 of the ownertrust values you assigned.
462 * clear signature headers are now in compliance with OpenPGP.
464 Noteworthy changes in version 0.3.0
465 -----------------------------------
467 * New option --emulate-checksum-bug. If your passphrase does not
468 work anymore, use this option and --change-passphrase to rewrite
471 * More complete v4 key support: Preferences and expiration time
472 is set into the self signature.
474 * Key generation defaults to DSA/ElGamal keys, so that new keys are
475 interoperable with pgp5
477 * DSA key generation is faster and key generation does not anymore
478 remove entropy from the random generator (the primes are public
479 parameters, so there is really no need for a cryptographic secure
480 prime number generator which we had used).
482 * A complete new structure for representing the key parameters.
484 * Removed most public key knowledge into the cipher library.
486 * Support for dynamic loading of new algorithms.
488 * Moved tiger to an extension module.
491 Noteworthy changes in version 0.2.19
492 ------------------------------------
494 * Replaced /dev/urandom in checks with new tool mk-tdata.
496 * Some assembler file cleanups; some more functions for the Alpha.
498 * Tiger has now the OpenPGP assigned number 6. Because the OID has
499 changed, old signatures using this algorithm can't be verified.
501 * gnupg now encrypts the compressed packed and not any longer in the
502 reverse order; anyway it can decrypt both versions. Thanks to Tom
503 for telling me this (not security related) bug.
505 * --add-key works and you are now able to generate subkeys.
507 * It is now possible to generate ElGamal keys in v4 packets to create
510 * Some new features for better integration into MUAs.
513 Noteworthy changes in version 0.2.18
514 ------------------------------------
516 * Splitted cipher/random.c, add new option "--disable-dev-random"
517 to configure to support the development of a random source for
518 other systems. Prepared sourcefiles rand-unix.c, rand-w32.c
519 and rand-dummy.c (which is used to allow compilation on systems
520 without a random source).
522 * Fixed a small bug in the key generation (it was possible that 48 bits
523 of a key were not taken from the random pool)
525 * Add key generation for DSA and v4 signatures.
527 * Add a function trap_unaligned(), so that a SIGBUS is issued on
528 Alphas and not the slow emulation code is used. And success: rmd160
531 * Enhanced the formatting facility of argparse and changed the use of
532 \r,\v to @ because gettext does not like it.
534 * New option "--compress-algo 1" to allow the creation of compressed
535 messages which are readable by PGP and "--print-md" (gpgm) to make
536 speed measurement easier.
539 Noteworthy changes in version 0.2.17
540 ------------------------------------
542 * Comment packets are now of private type 61.
544 * Passphrase code still used a 160 bit blowfish key, added a
545 silly workaround. Please change your passphrase again - sorry.
547 * Conventional encryption now uses a type 3 packet to describe the
550 * The new algorithm number for Blowfish is 20, 16 is still used for
551 encryption only; for signing it is only used when it is in a v3 packet,
552 so that GNUPG keys are still valid.
555 Noteworthy changes in version 0.2.16
556 ------------------------------------
558 * Add experimental support for the TIGER/192 message digest algorithm.
559 (But there is only a dummy ASN OID).
561 * Standard cipher is now Blowfish with 128 bit key in OpenPGP's CFB
562 mode. I renamed the old cipher to Blowfish160. Because the OpenPGP
563 group refused to assign me a number for Blowfish160, I have to
564 drop support for this in the future. You should use
565 "--change-passphrase" to recode your current passphrase with 128
569 Noteworthy changes in version 0.2.15
570 ------------------------------------
572 * Fixed a bug with the old checksum calculation for secret keys.
573 If you run the program without --batch, a warning does inform
574 you if your secret key needs to be converted; simply use
575 --change-passphrase to recalculate the checksum. Please do this
576 soon, as the compatible mode will be removed sometime in the future.
578 * CAST5 works (using the PGP's special CFB mode).
580 * Again somewhat more PGP 5 compatible.
582 * Some new test cases
584 Noteworthy changes in version 0.2.14
585 ------------------------------------
587 * Changed the internal handling of keyrings.
589 * Add support to list PGP 5 keyrings with subkeys
591 * Timestamps of signatures are now verified.
593 * A expiration time can now be specified during key generation.
595 * Some speedups for Blowfish and SHA-1, rewrote SHA-1 transform.
596 Reduced the amount of random bytes needed for key generation in
600 Noteworthy changes in version 0.2.13
601 ------------------------------------
603 * Verify of DSA signatures works.
605 * Re-implemented the slower random number generator.
608 Noteworthy changes in version 0.2.12
609 ------------------------------------
611 * --delete-key checks that there is no secret key. The new
612 option --delete-secret-key maybe used to delete a secret key.
614 * "-kv" now works as expected. Options "--list-{keys,sigs]"
615 and "--check-sigs" are now working.
617 * New options "--verify" and "--decrypt" to better support integration
618 into MUAs (partly done for Mutt).
620 * New option "--with-colons" to make parsing of key lists easier.
622 Noteworthy changes in version 0.2.11
623 ------------------------------------
625 * GPG now asks for a recipient's name if option "-r" is not used.
627 * If there is no good trust path, the program asks whether to use
628 the public keys anyway.
630 * "--delete-key" works for public keys. What semantics shall I use
631 when there is a secret key too? Delete the secret key or leave him
632 and auto-regenerate the public key, next time the secret key is used?
634 Noteworthy changes in version 0.2.10
635 ------------------------------------
637 * Code for the alpha is much faster (about 20 times); the data
638 was misaligned and the kernel traps this, so nearly all time
639 was used by system to trap the misalignments and to write
640 syslog messages. Shame on me and thanks to Ralph for
641 pointing me at this while drinking some beer yesterday.
643 * Changed some configure options and add an option
644 --disable-m-guard to remove the memory checking code
645 and to compile everything with optimization on.
647 * New environment variable GNUPGHOME, which can be used to set
648 another homedir than ~/.gnupg. Changed default homedir for
649 Windoze version to c:/gnupg.
651 * Fixed detached signatures; detached PGP signatures caused a SEGV.
653 * The Windoze version works (as usual w/o a strong RNG).
656 Noteworthy changes in version 0.2.9
657 -----------------------------------
661 * Added a simple man page.
663 * Switched to automake1.2f and a newer gettext.
665 Noteworthy changes in version 0.2.8
666 -----------------------------------
668 * Changed the name to GNUPG, the binaries are called gpg and gpgm.
669 You must rename rename the directory "~/.g10" to ~/.gnupg/, rename
670 {pub,sec}ring.g10 to {pub,sec}ring.gpg, trustdb.g10 to trustdb.gpg
671 and g10.sig to gnupg.sig.
673 * New or changed passphrases are now salted.
676 Noteworthy changes in version 0.2.7
677 -----------------------------------
679 * New command "gen-revoke" to create a key revocation certificate.
681 * New option "homedir" to set the homedir (which defaults to "~/.g10").
682 This directory is created if it does not exists (only the last
683 part of the name and not the complete hierarchy)
685 * Command "import" works. (Try: "finger gcrypt@ftp.guug.de|g10 --import")
687 * New commands "dearmor/enarmor" for g10maint. These are mainly
688 used for internal test purposes.
690 * Option --version now conforming to the GNU standards and lists
691 the available ciphers, message digests and public key algorithms.
693 * Assembler code for m68k (not tested).
695 * "make check" works.
697 Noteworthy changes in version 0.2.6
698 -----------------------------------
700 * Option "--export" works.
703 Noteworthy changes in version 0.2.5
704 -----------------------------------
706 * Added zlib for systems which don't have it.
707 Use "./configure --with-zlib" to link with the static version.
709 * Generalized some more functions and rewrote the encoding of
710 message digests into MPIs.
712 * Enhanced the checkit script
715 Noteworthy changes in version 0.2.4
716 -----------------------------------
718 * nearly doubled the speed of the ElGamal signature verification.
720 * backup copies of keyrings are created.
722 * assembler stuff for Pentium; gives about 15% better performance.
724 * fixed a lot of bugs.
727 Noteworthy changes in version 0.2.3
728 -----------------------------------
730 * Found a bug in the calculation of ELG fingerprints. This is now
731 fixed, but all existing fingerprints and keyids for ELG keys
732 are not any more valid.
734 * armor should now work; including clear signed text.
736 * moved some options to the new program g10maint
738 * It's now 64 bit clean and runs fine on an alpha--linux.
740 * Key generation is much faster now. I fixed this by using not
741 so strong random number for the primes (this was a bug because the
742 ElGamal primes are public parameters and it does not make sense
743 to generate them from strong random). The real secret is the x value
744 which is still generated from strong (okay: /dev/random) random bits.
746 * added option "--status-fd": see g10/OPTIONS
748 * We have secure memory on systems which support mlock().
749 It is not complete yet, because we do not have signal handler
750 which does a cleanup in very case.
751 We should also check the ulimit for the user in the case
752 that the admin does not have set a limit on locked pages.
754 * started with internationalization support.
756 * The logic to handle the web of trust is now implemented. It is
757 has some bugs; but I'm going to change the algorithm anyway.
758 It works by calculating the trustlevel on the fly. It may ask
759 you to provide trust parameters if the calculated trust probability
760 is too low. I will write a paper which discusses this new approach.
762 * a couple of changes to the configure script.
764 * New option "--quick-random" which uses a much quicker random
765 number generator. Keys generated while this option is in effect
766 are flags with "INSECURE!" in the user-id. This is a development
769 * Read support for new version packets (OpenPGP).
771 * Comment packets are now of correct OpenPGP type 16. Old comment
772 packets written by G10 are detected because they always start with
773 a hash which is an invalid version byte.
775 * The string "(INSECURE!)" is appended to a new user-id if this
776 is generated on a system without a good random number generator.