[Announce] release candidate for 1.4.1 available

Werner Koch wk at gnupg.org
Thu Feb 3 12:48:26 CET 2005


We are pleased to announce the availability of a release candidate for
the forthcoming 1.4.1 version of gnupg:

 ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-1.4.1rc1.tar.bz2  (2709k)

A binary for Windows is also available:

 ftp://ftp.gnupg.org/gcrypt/alpha/binary/gnupg-w32cli-1.4.1rc1.exe (1377k)

Please try these versions out and report any problems.  The installer
used for the Windows binary package is pretty basic right now but
nevertheless a first step. In particular, selecting the language to
use still needs manual interaction.  We hope to improve it over time.

Checksums are:

323445ee8e0c1de97243c646538d9f5dae5567ff  gnupg-1.4.1rc1.tar.bz2
cda3e84f89dd7a0fd7df59e4c142e7bbb9669cb2  gnupg-w32cli-1.4.1rc1.exe

Noteworthy changes since 1.4.0:

 * New --rfc2440-text option which controls how text is handled in
   signatures.  This is in response to some problems seen with
   certain PGP/MIME mail clients and GnuPG version 1.4.0.  More
   details about this are available at

 * New "import-unusable-sigs" and "export-unusable-sigs" tags for
   --import-options and --export-options.  These are on by
   default, and cause GnuPG to not import or export key signatures
   that are not usable (e.g. expired signatures).

 * New experimental HTTP, HTTPS, FTP, and FTPS keyserver helper
   that uses the cURL library <http://curl.haxx.se> to retrieve
   keys.  This is disabled by default, but may be enabled with the
   configure option --with-libcurl.  Without this option, the
   existing HTTP code is used for HTTP, and HTTPS, FTP, and FTPS
   are not supported.

 * When running a --card-status or --card-edit and a public key is
   available, missing secret key stubs will be created on the fly.
   Details of the key are listed too.

 * The implicit packet dumping in double verbose mode is now send
   to stderr and not to stdout.

 * [W32] The algorithm for the default home directory changed:
   First we look at the environment variable GNUPGHOME, if this one
   is not set, we check whether the registry entry
   {HKCU,HKLM}\Software\GNU\GnuPG:HomeDir has been set. If this
   fails we use a GnuPG directory below the standard application
   data directory (APPDATA) of the current user. Only in the case
   that this directory cannot be determined, the old default of
   c:\gnupg will be used.  The option --homedir still overrides all
   of them.

 * [W32] The locale selection under Windows changed. You need to
   enter the locale in the registry at HKCU\Software\GNU\GnuPG:Lang. 
   For German you would use "de".  If it is not set, GnupG falls
   back to HKLM.  The languages files "*.mo" are expected in a
   directory named "gnupg.nls" below the installation directory;
   that directory must be stored in the registry at the same key as
   above with the name "Install Directory".

Happy Hacking,

  David, Timo, Werner

Werner Koch                                      <wk at gnupg.org>
The GnuPG Experts                                http://g10code.com
Free Software Foundation Europe                  http://fsfeurope.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : /pipermail/attachments/20050203/005c5657/attachment.pgp

More information about the Gnupg-devel mailing list