Mac GNU Privacy Guard Changelog
What's new in Mac GNU Privacy Guard 1.4.9
Mar 24, 2009- Improved AES encryption performance by more than 20% (on ia32). Decryption is also a bit faster.
- Fixed possible memory corruption bug in 1.4.8 while importing OpenPGP keys.
New in Mac GNU Privacy Guard 2.0.10.2 (Jan 14, 2009)
- [gpg] New keyserver helper gpg2keys_kdns as generic DNS CERT lookup. Run with --help for a short description. Requires the ADNS library.
- [gpg] New mechanisms "local" and "nodefault" for --auto-key-locate. Fixed a few problems with this option.
- [gpg] New command --locate-keys.
- [gpg] New options --with-sig-list and --with-sig-check.
- [gpg] The option "-sat" is no longer an alias for --clearsign.
- [gpg] The option --fixed-list-mode is now implicitly used and obsolete.
- [gpg] New control statement %ask-passphrase for the unattended key generation.
- [gpg] The algorithm to compute the SIG_ID status has been changed.
- [gpgsm] Now uses AES by default.
- [gpgsm] Made --output option work with --export-secret-key-p12.
- [gpg-agent] Terminate process if the own listening socket is not anymore served by ourself.
- [scdaemon] Made it more robust on W32.
- [gpg-connect-agent] Accept commands given as command line arguments.
- [w32] Initialized the socket subsystem for all keyserver helpers.
- [w32] The sysconf directory has been moved from a subdirectory of the installation directory to %CSIDL_COMMON_APPDATA%/GNU/etc/gnupg.
- [w32] The gnupg2.nls directory is not anymore used. The standard locale directory is now used.
- [w32] Fixed a race condition between gpg and gpgsm in the use of temporary file names.
- The gpg-preset-passphrase mechanism works again. An arbitrary string may now be used for a custom cache ID.
- Admin PINs are cached again (bug in 2.0.9).
- Support for version 2 OpenPGP cards.
- Libgcrypt 1.4 is now required.
New in Mac GNU Privacy Guard 2.0.10 RC1 (Jan 12, 2009)
- MacGPG2 now uses Stéphane Corthésy's gpg-agent launchd patch for use with Leopard and above. For MacOS versions prior, a login item is now used.
- MacGPG2 no longer needs login or logout scripts in order to function correctly and these will be disabled.
- Under most circumstances, MacGPG2 no longer needs to interact with the ~/.MacOSX/environment.plist file and any unneeded entries will be automatically removed.