[Announce]GnuPG 1.3.0 released (development)

[David Shaw]

-----BEGIN PGP SIGNED MESSAGE-----

Hello!

The first release from the new development branch of GnuPG is ready
for public consumption.  This is a branch to create what will be GnuPG
1.4 someday.  It will change much more frequently than the 1.2.x
"stable" branch, which will mainly be updated for bug fix reasons.

I encourage the more GnuPG-familiar user to try this release (and the
ones that will follow in the 1.3.x branch), and report back any
problems to gnupg-devel at gnupg.org.  In return, you get the latest code
with the latest features.  However, it is always important to keep in
mind that this is still development code - please do not use it on
anything mission-critical.  Critical applications should always use
the 1.2.x stable branch.

You may notice the smaller tarball size for this release - that is due
to the translations other than de being removed.  You may also notice
the smaller size of the gpg binary, and that is due to some of the
keyserver modifications.  See the list below for more on these
changes.

The files are available from:

  ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-1.3.0.tar.gz (1432k)
  ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-1.3.0.tar.gz.sig

MD5 checksums for the files are:

  2dcd23aae21e1ff08ffc258d6f075d64  gnupg-1.3.0.tar.gz
  006384951e566ffa4581251b538af154  gnupg-1.3.0.tar.gz.sig

Noteworthy changes in version 1.3.0 (2002-10-18)
- ------------------------------------------------

    * The last piece of internal keyserver support has been removed,
      and now all keyserver access is done via the keyserver plugins.
      There is also a newer keyserver protocol used between GnuPG and
      the plugins, so plugins from earlier versions of GnuPG may not
      work properly.

    * The HKP keyserver plugin supports the new machine-readable key
      listing format for those keyservers that provide it.

    * When using a HKP keyserver with multiple DNS records (such as
      wwwkeys.pgp.net which has the addresses of multiple servers
      around the world), try all records until one succeeds.  Note
      that it depends on the LDAP library used whether the LDAP
      keyserver plugin does this as well.

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

    * Translations other than de are no longer distributed with the
      development branch.  This is due to the frequent text changes
      during development, which cause the translations to rapidly go
      out of date.

Happy Hacking,

  The GnuPG team (David, Stefan, Timo and Werner)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3 (GNU/Linux)

iQEVAwUBPbARc4ccwqs8s7QVAQGXKAgAo9UqRZ0HdH/HEiX1wRMJsNHWYL7E9Mxc
ftYiThLyEvhZ/W0tTFDqsyqtd4fazzyuUgy7ECKl0nJLGdCM7whXnIyELQmqGxVB
XOOiZ0RRMoBz0QbqsEkB46KWI+VeZkAxw7WK9Buib7UeC8BnUVIYHGpMItxPMlDa
3pCOg7gnaV450ad+24KkzMOt1uZ+TFYLSQmgUxczJ8Y1WMsh7LIsvIniWmIQWVFs
MvMvx3i8Bdt2dO2H/jW8ezaPDQt6WcY84BZQeNRcZ6xD9bs3u6Cr96kNA41NPuM2
CmgqU5L2YAsJ1YE+ZmmrzxmlqWOOjQcRgmao9n9GYSQw72sc+ofsPw==
=uhVf
-----END PGP SIGNATURE-----