wk at gnupg
May 4, 2007, 4:48 AM
Post #1 of 1
Libgcrypt 1.3.0 (development) released
We are pleased to announce the availability of Libgcrypt 1.3.0. This
is the first release of a series of development versions ebentually
leading to a new stable 1.4 series.
Libgcrypt is a general purpose library of cryptographic building
blocks. It is originally based on code used by GnuPG. It does not
provide any implementaion of OpenPGP or other protocols. Thorough
understanding of applied cryptography is required to use libgcrypt.
Changes relative to 1.2.4 are:
* Reading and writing the random seed file is now protected by a
fcntl style file lock on systems that provide this function.
* Support for SHA-224 and HMAC using SHA-384 and SHA-512.
* Support for the SEED cipher.
* Support for the Camellia cipher. Note that Camellia is disabled by
default, and that enabling it changes the license of libgcrypt from
LGPL to GPL.
* Support for OFB encryption mode.
* gcry_mpi_rshift does not anymore truncate the shift count.
* Reserved algorithm ranges for use by applications.
* Support for DSA2.
* The new function gcry_md_debug should be used instead of the
gcry_md_start_debug and gcry_md_stop_debug macros.
* New configure option --enable-random-daemon to support a system
wide random daemon. The daemon code is experimental and not yet
very well working. It will eventually allow to keep a global
random pool for the sake of short living processes.
* Non executable stack support is now used by default on systems
* Support for Microsoft Windows.
* Assembler support for the AMD64 architecture.
* New configure option --enable-mpi-path for optimized builds.
* Experimental support for ECDSA; should only be used for testing.
* New control code GCRYCTL_PRINT_CONFIG to print the build
Source code is hosted at the GnuPG FTP server and its mirrors as
listed at http://www.gnupg.org/download/mirrors.html . On the primary
server the source file and its digital signatures is:
This file is bzip2 compressed. The SHA-1 checksum is:
For help on developing with Libgcrypt you should send mail to the
grcypt-devel mailing list .
Improving Libgcrypt is costly, but you can help! We are looking for
organizations that find Libgcrypt useful and wish to contribute back.
You can contribute by reporting bugs, improve the software , or by
Commercial support contracts for Libgcrypt are available , and they
help finance continued maintenance. g10 Code GmbH, a Duesseldorf
based company, is currently funding Libgcrypt development. We are
always looking for interesting development projects.
 See http://www.gnupg.org/documentation/mailing-lists.html .
 Note that copyright assignments to the FSF are required.
 See the service directory at http://www.gnupg.org/service.html .