From wk at gnupg.org Fri May 4 13:48:43 2007 From: wk at gnupg.org (Werner Koch) Date: Fri, 04 May 2007 13:48:43 +0200 Subject: Libgcrypt 1.3.0 (development) released Message-ID: <87r6pw95d0.fsf@wheatstone.g10code.de> Hello! 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 supporting it. * 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 configuration. 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: ftp://ftp.gnupg.org/gcrypt/alpha/libgcrypt/libgcrypt-1.3.0.tar.bz2 (922k) ftp://ftp.gnupg.org/gcrypt/alpha/libgcrypt/libgcrypt-1.3.0.tar.bz2.sig This file is bzip2 compressed. The SHA-1 checksum is: 38361925fef99715eccb8a1f73110ce2f3c3896a libgcrypt-1.3.0.tar.bz2 For help on developing with Libgcrypt you should send mail to the grcypt-devel mailing list [1]. 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 [2], or by donating money. Commercial support contracts for Libgcrypt are available [3], 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. Happy hacking, Werner [1] See http://www.gnupg.org/documentation/mailing-lists.html . [2] Note that copyright assignments to the FSF are required. [3] See the service directory at http://www.gnupg.org/service.html . -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 204 bytes Desc: not available Url : /pipermail/attachments/20070504/84497c9e/attachment.pgp From simon at josefsson.org Fri May 4 16:01:37 2007 From: simon at josefsson.org (Simon Josefsson) Date: Fri, 04 May 2007 16:01:37 +0200 Subject: Ming32 builds of libgcrypt 1.3.0 In-Reply-To: <87r6pw95d0.fsf@wheatstone.g10code.de> (Werner Koch's message of "Fri\, 04 May 2007 13\:48\:43 +0200") References: <87r6pw95d0.fsf@wheatstone.g10code.de> Message-ID: <876478662m.fsf@mocca.josefsson.org> FWIW, libgcrypt 1.3.0 builds fine under mingw32 for me. The self tests also passes. (modulo libtool and wine bugs that I know how to work around.) One question though: I notice that ./configure says rndw32 is used and that it turns the library into GPL. When building 1.2.4 it says it is using the 'default' random module, under mingw32, and there is no similar complaint. Is the 1.2.4 'default' mingw32 random module under GPL or LGPL? If that one was LGPL, would it be possible to optionally support using the 1.2.4 randomness module for mingw32 builds in 1.3.x? Thanks, Simon From wk at gnupg.org Fri May 4 19:06:01 2007 From: wk at gnupg.org (Werner Koch) Date: Fri, 04 May 2007 19:06:01 +0200 Subject: Ming32 builds of libgcrypt 1.3.0 In-Reply-To: <876478662m.fsf@mocca.josefsson.org> (Simon Josefsson's message of "Fri\, 04 May 2007 16\:01\:37 +0200") References: <87r6pw95d0.fsf@wheatstone.g10code.de> <876478662m.fsf@mocca.josefsson.org> Message-ID: <87fy6c7c3q.fsf@wheatstone.g10code.de> On Fri, 4 May 2007 16:01, simon at josefsson.org said: > FWIW, libgcrypt 1.3.0 builds fine under mingw32 for me. The self tests > also passes. (modulo libtool and wine bugs that I know how to work > around.) I actually did some manual tests on XP > One question though: I notice that ./configure says rndw32 is used and > that it turns the library into GPL. When building 1.2.4 it says it is > using the 'default' random module, under mingw32, and there is no At some point a bug slipped in which didn't trigged the GPL "warning" anymore. I fixed that yesterday and should do that also for 1.2.4. > GPL or LGPL? If that one was LGPL, would it be possible to optionally > support using the 1.2.4 randomness module for mingw32 builds in 1.3.x? No. The rndw32 is under the GPL and has been contributed by Peter Gutmann. I have currently no need to change that. Thus I have not even considered to ask Peter whether he would change the license. Feel free to ask him. Salam-Shalom, Werner From simon at josefsson.org Mon May 7 10:46:32 2007 From: simon at josefsson.org (Simon Josefsson) Date: Mon, 07 May 2007 10:46:32 +0200 Subject: Ming32 builds of libgcrypt 1.3.0 In-Reply-To: <87fy6c7c3q.fsf@wheatstone.g10code.de> (Werner Koch's message of "Fri\, 04 May 2007 19\:06\:01 +0200") References: <87r6pw95d0.fsf@wheatstone.g10code.de> <876478662m.fsf@mocca.josefsson.org> <87fy6c7c3q.fsf@wheatstone.g10code.de> Message-ID: <87r6ptrpg7.fsf@mocca.josefsson.org> Werner Koch writes: >> One question though: I notice that ./configure says rndw32 is used and >> that it turns the library into GPL. When building 1.2.4 it says it is >> using the 'default' random module, under mingw32, and there is no > > At some point a bug slipped in which didn't trigged the GPL "warning" > anymore. I fixed that yesterday and should do that also for 1.2.4. Ok. I assume then that 'default' in 1.2.4 means that rndw32 is used? >> GPL or LGPL? If that one was LGPL, would it be possible to optionally >> support using the 1.2.4 randomness module for mingw32 builds in 1.3.x? > > No. The rndw32 is under the GPL and has been contributed by Peter > Gutmann. I have currently no need to change that. Thus I have not even > considered to ask Peter whether he would change the license. Feel free > to ask him. I don't have a need to see this LGPL'ed. However, in GnuTLS4Win I should make it clear that because of this situation, the package is only available under the GPL. That wasn't clear to me before. /Simon From wk at gnupg.org Mon May 7 11:21:20 2007 From: wk at gnupg.org (Werner Koch) Date: Mon, 07 May 2007 11:21:20 +0200 Subject: Ming32 builds of libgcrypt 1.3.0 In-Reply-To: <87r6ptrpg7.fsf@mocca.josefsson.org> (Simon Josefsson's message of "Mon\, 07 May 2007 10\:46\:32 +0200") References: <87r6pw95d0.fsf@wheatstone.g10code.de> <876478662m.fsf@mocca.josefsson.org> <87fy6c7c3q.fsf@wheatstone.g10code.de> <87r6ptrpg7.fsf@mocca.josefsson.org> Message-ID: <87hcqpat0v.fsf@wheatstone.g10code.de> On Mon, 7 May 2007 10:46, simon at josefsson.org said: > Ok. I assume then that 'default' in 1.2.4 means that rndw32 is used? Yes. There is no other way to gather entropy under Windows. Salam-Shalom, Werner From tmcmahon2 at yahoo.com Sun May 27 23:22:45 2007 From: tmcmahon2 at yahoo.com (Torrey McMahon) Date: Sun, 27 May 2007 17:22:45 -0400 Subject: Solaris /dev/urandom issue Message-ID: <4659F6A5.4090003@yahoo.com> Using the configure script in gcrypt 1.2.4 I see that the solaris bits don't include /dev/urandom support. "configure" line 20974 *-solaris* | *-irix* | *-dec-osf* | *-netbsd* ) NAME_OF_DEV_RANDOM="/dev/random" NAME_OF_DEV_URANDOM="/dev/random" # DYNLINK_MOD_CFLAGS="-shared $CFLAGS_PIC" ;; Solaris includes /dev/urandom for a while now. Time to change this? Anywhere I can file a bug?