From torsten.rupp at gmx.net Mon Sep 1 09:50:30 2008 From: torsten.rupp at gmx.net (Torsten Rupp) Date: Mon, 1 Sep 2008 16:50:30 +0900 Subject: pk_encrypt/decrypt limited to <1024bit blocks Message-ID: <200809011650.21534.torsten.rupp@gmx.net> Hi, I just detected that the example tests/pubkey.c of libgcrypt 1.4.1 seems to have problems with encrypting/decrypting of data blocks with a size over 1016 bits. In the example a random number with 800 bits is created. This works fine. If I change the value e. g. to 1024 encryption or decryption does not work anymore. Is this a bug or a limitation? I detected this problem when I encrypted/decrypted data blocks with 2048 bit (and a 1024bit key-pair). Sometimes it seems to work, but sometimes it fail with the problem that the decrypted data is completely wrong. Torsten From wk at gnupg.org Mon Sep 1 10:34:41 2008 From: wk at gnupg.org (Werner Koch) Date: Mon, 01 Sep 2008 10:34:41 +0200 Subject: Release candidate for Libgcrypt 1.4.2 Message-ID: <87r684463i.fsf@wheatstone.g10code.de> Hi! I just did a release candidate for Libgcrypt: ftp://ftp.gnupg.org/gcrypt/alpha/libgcrypt/libgcrypt-1.4.2rc2.tar.bz2 ftp://ftp.gnupg.org/gcrypt/alpha/libgcrypt/libgcrypt-1.4.2rc2.tar.bz2.sig There are only a few changes: * The long missing gcry_mpi_lshift function has been added. * RSA key generation now supports a "transient-key" flag. This is only meaningful for RSA keys. This is a flag with no value. If given the RSA key is created using a faster and a somewhat less secure random number generator. This flag may be used for keys which are only used for a short time and do not require full cryptographic strength. Example: (genkey (rsa (nbits 4:1024)(transient-key))) * The keygrip computation for ECDSA has been implemented thus ECDSA is now fully supported. * A few macros have been replaced by functions for better type checking. * The thread initialization structure now carries version information. This will make it in future easier to add new thread related functions. This is implemented in a backward compatible way. * The manual describes more clearly how to initialize Libgcrypt. * The library may now be switched into a FIPS mode. * Interface changes relative to the 1.3.0 release: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ GCRYCTL_OPERATIONAL_P NEW. GCRYCTL_FIPS_MODE_P NEW. GCRYCTL_FORCE_FIPS_MODE NEW. gcry_cipher_setkey NEW: Replaces macro. gcry_cipher_setiv NEW: Replaces macro. gcry_cipher_setctr NEW: Replaces macro. gcry_mpi_lshift NEW. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Salam-Shalom, Werner -- Linux-Kongress 2008 + Hamburg + October 7-10 + www.linux-kongress.org Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. From wk at gnupg.org Mon Sep 1 11:04:38 2008 From: wk at gnupg.org (Werner Koch) Date: Mon, 01 Sep 2008 11:04:38 +0200 Subject: pk_encrypt/decrypt limited to <1024bit blocks In-Reply-To: <200809011650.21534.torsten.rupp@gmx.net> (Torsten Rupp's message of "Mon, 1 Sep 2008 16:50:30 +0900") References: <200809011650.21534.torsten.rupp@gmx.net> Message-ID: <87iqtg44pl.fsf@wheatstone.g10code.de> On Mon, 1 Sep 2008 09:50, torsten.rupp at gmx.net said: > is created. This works fine. If I change the value e. g. to 1024 > encryption or decryption does not work anymore. Is this a bug or a > limitation? That depends on your key size: You can't encrypt a 1024 bit value with a 1024 bit modulus if that value is karge than the modulus. Libgcrypt does not enforce this because it expects that pkcs#1 encoding is done by the caller or by passing the pkcs#1 flag. Without proper padding your encryption is weak. > I detected this problem when I encrypted/decrypted data blocks with > 2048 bit (and a 1024bit key-pair). Sometimes it seems to work, but You mean you try to encrypt a 2048 bit value with a 1024 bit key - that is obviously not possible. Salam-Shalom, Werner -- Linux-Kongress 2008 + Hamburg + October 7-10 + www.linux-kongress.org Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. From simon at josefsson.org Mon Sep 1 11:09:27 2008 From: simon at josefsson.org (Simon Josefsson) Date: Mon, 01 Sep 2008 11:09:27 +0200 Subject: Release candidate for Libgcrypt 1.4.2 In-Reply-To: <87r684463i.fsf@wheatstone.g10code.de> (Werner Koch's message of "Mon, 01 Sep 2008 10:34:41 +0200") References: <87r684463i.fsf@wheatstone.g10code.de> Message-ID: <87ljyc9qrc.fsf@mocca.josefsson.org> Werner Koch writes: > ftp://ftp.gnupg.org/gcrypt/alpha/libgcrypt/libgcrypt-1.4.2rc2.tar.bz2 Works fine here, on debian x86 and mingw32. There is one old buglet wrt to Wine. The self tests prints times such as this: MD5 27574050817572864ms 5084966400557066ms 5084966400557116ms SHA1 27574050817572864ms 5103280141107220ms 5103280141107260ms RIPEMD160 27574050817572884ms 5103280141107220ms 5103280141107260ms TIGER192 27574050817572884ms 5103280141107230ms 5103280141107270ms ... However, it is not important and I'll see if I can debug it and provide a patch to make it look nicer. Thanks, Simon From simon at josefsson.org Mon Sep 1 18:36:03 2008 From: simon at josefsson.org (Simon Josefsson) Date: Mon, 01 Sep 2008 18:36:03 +0200 Subject: Release candidate for Libgcrypt 1.4.2 In-Reply-To: <87ljyc9qrc.fsf@mocca.josefsson.org> (Simon Josefsson's message of "Mon, 01 Sep 2008 11:09:27 +0200") References: <87r684463i.fsf@wheatstone.g10code.de> <87ljyc9qrc.fsf@mocca.josefsson.org> Message-ID: <87aber6cy4.fsf@mocca.josefsson.org> Simon Josefsson writes: > There is one old buglet wrt to Wine. The self tests prints times such > as this: > > MD5 27574050817572864ms 5084966400557066ms 5084966400557116ms > SHA1 27574050817572864ms 5103280141107220ms 5103280141107260ms > RIPEMD160 27574050817572884ms 5103280141107220ms 5103280141107260ms > TIGER192 27574050817572884ms 5103280141107230ms 5103280141107270ms > ... > > However, it is not important and I'll see if I can debug it and provide > a patch to make it look nicer. This patch fixes the problem. Thanks, /Simon Index: benchmark.c =================================================================== --- benchmark.c (revision 1312) +++ benchmark.c (working copy) @@ -321,7 +321,7 @@ t2 += (((unsigned long long)stopped_at.user_time.dwHighDateTime << 32) + stopped_at.user_time.dwLowDateTime); t = (t2 - t1)/10000; - snprintf (buf, sizeof buf, "%5lums", (unsigned long)t ); + snprintf (buf, sizeof buf, "%5.0fms", (double)t ); #else snprintf (buf, sizeof buf, "%5.0fms", (((double) (stopped_at - started_at))/CLOCKS_PER_SEC)*10000000); From wk at gnupg.org Mon Sep 1 20:04:51 2008 From: wk at gnupg.org (Werner Koch) Date: Mon, 01 Sep 2008 20:04:51 +0200 Subject: Release candidate for Libgcrypt 1.4.2 In-Reply-To: <87aber6cy4.fsf@mocca.josefsson.org> (Simon Josefsson's message of "Mon, 01 Sep 2008 18:36:03 +0200") References: <87r684463i.fsf@wheatstone.g10code.de> <87ljyc9qrc.fsf@mocca.josefsson.org> <87aber6cy4.fsf@mocca.josefsson.org> Message-ID: <87wshv214s.fsf@wheatstone.g10code.de> On Mon, 1 Sep 2008 18:36, simon at josefsson.org said: > - snprintf (buf, sizeof buf, "%5lums", (unsigned long)t ); > + snprintf (buf, sizeof buf, "%5.0fms", (double)t ); Do you understand why this occurs only with Wine? I have not tested it on Wine but it works fine on a standard XP box. Is there a problem with my code or is Wine's snprintf broken? Shalom-Salam, Werner -- Linux-Kongress 2008 + Hamburg + October 7-10 + www.linux-kongress.org Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. From simon at josefsson.org Mon Sep 1 21:56:43 2008 From: simon at josefsson.org (Simon Josefsson) Date: Mon, 01 Sep 2008 21:56:43 +0200 Subject: Release candidate for Libgcrypt 1.4.2 In-Reply-To: <87wshv214s.fsf@wheatstone.g10code.de> (Werner Koch's message of "Mon, 01 Sep 2008 20:04:51 +0200") References: <87r684463i.fsf@wheatstone.g10code.de> <87ljyc9qrc.fsf@mocca.josefsson.org> <87aber6cy4.fsf@mocca.josefsson.org> <87wshv214s.fsf@wheatstone.g10code.de> Message-ID: <87hc8z4p38.fsf@mocca.josefsson.org> Werner Koch writes: > On Mon, 1 Sep 2008 18:36, simon at josefsson.org said: > >> - snprintf (buf, sizeof buf, "%5lums", (unsigned long)t ); >> + snprintf (buf, sizeof buf, "%5.0fms", (double)t ); > > Do you understand why this occurs only with Wine? I have not tested it > on Wine but it works fine on a standard XP box. Is there a problem with > my code or is Wine's snprintf broken? I actually don't know where the problem is. I can't reproduce it in a small snippet. FWIW, this also works fine under mingw+wine: snprintf (buf, sizeof buf, "%5llums", t ); That is arguably more correct, but requires that all Windows supports %ll. Something seems to go wrong when the 64-bit value is cast to a 32-bit value and then passed as an argument. The values are interesting, see: MD5 27574050817572874ms 5083798169452554ms 5083798169452604ms That isn't even close to 64-bit or 32-bit boundaries. /Simon From wk at gnupg.org Tue Sep 2 18:30:52 2008 From: wk at gnupg.org (Werner Koch) Date: Tue, 02 Sep 2008 18:30:52 +0200 Subject: Release candidate for Libgcrypt 1.4.2 In-Reply-To: <87hc8z4p38.fsf@mocca.josefsson.org> (Simon Josefsson's message of "Mon, 01 Sep 2008 21:56:43 +0200") References: <87r684463i.fsf@wheatstone.g10code.de> <87ljyc9qrc.fsf@mocca.josefsson.org> <87aber6cy4.fsf@mocca.josefsson.org> <87wshv214s.fsf@wheatstone.g10code.de> <87hc8z4p38.fsf@mocca.josefsson.org> Message-ID: <871w021pdv.fsf@wheatstone.g10code.de> Hi! I just tried it on wine 0.9.8 on an ia32 Debian Sid and I don't have this problem. Shalom-Salam, Werner -- Linux-Kongress 2008 + Hamburg + October 7-10 + www.linux-kongress.org Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. From mail at markuswestphal.de Thu Sep 4 13:48:48 2008 From: mail at markuswestphal.de (Markus Westphal) Date: Thu, 4 Sep 2008 13:48:48 +0200 Subject: GPGME export secret key Message-ID: revisiting an old topic (http://marc.info/?t=101889760900001): what about an option to export a private key in GPGME? Werner Koch and Janusz Urbanowicz rejected this request back then because the format was prone to Klima Rosa attack (http://marc.info/? l=gnupg-devel&m=101895382319899&w=2). Has this been fixed since? Would it now be possible to add support for exporting private keys? Thanks in advance and best regards, Markus -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: Signierter Teil der Nachricht URL: From mail at markuswestphal.de Thu Sep 4 16:32:49 2008 From: mail at markuswestphal.de (Markus Westphal) Date: Thu, 4 Sep 2008 16:32:49 +0200 Subject: GPGME export secret key In-Reply-To: References: Message-ID: just realized: wrong list - I'm sorry... > revisiting an old topic (http://marc.info/?t=101889760900001): what > about an option to export a private key in GPGME? > Werner Koch and Janusz Urbanowicz rejected this request back then > because the format was prone to Klima Rosa attack (http:// > marc.info/?l=gnupg-devel&m=101895382319899&w=2). > > Has this been fixed since? Would it now be possible to add support > for exporting private keys? -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: Signierter Teil der Nachricht URL: From wk at gnupg.org Mon Sep 8 20:02:58 2008 From: wk at gnupg.org (Werner Koch) Date: Mon, 08 Sep 2008 20:02:58 +0200 Subject: Libgcrypt 1.4.2 released Message-ID: <873akabjn1.fsf@wheatstone.g10code.de> Hello! The GNU project is pleased to announce the availability of Libgcrypt version 1.4.2. Libgcrypt is a general purpose library of cryptographic building blocks. It is originally based on code used by GnuPG. It does not provide any implementation of OpenPGP or other protocols. Thorough understanding of applied cryptography is required to use Libgcrypt. Noteworthy changes in version 1.4.2: * The long missing gcry_mpi_lshift function has been added. * RSA key generation now supports a "transient-key" flag. * The keygrip computation for ECDSA has been implemented thus ECDSA is now fully supported. * A few macros have been replaced by functions for better type checking. * The thread initialization structure now carries version information. * The manual describes more clearly how to initialize Libgcrypt. * The library may now be switched into a FIPS mode. * Interface changes relative to the 1.3.0 release: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ GCRYCTL_OPERATIONAL_P NEW. GCRYCTL_FIPS_MODE_P NEW. GCRYCTL_FORCE_FIPS_MODE NEW. gcry_cipher_setkey NEW: Replaces macro. gcry_cipher_setiv NEW: Replaces macro. gcry_cipher_setctr NEW: Replaces macro. gcry_mpi_lshift NEW. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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/libgcrypt/libgcrypt-1.4.2.tar.bz2 (1049k) ftp://ftp.gnupg.org/gcrypt/libgcrypt/libgcrypt-1.4.2.tar.bz2.sig This file is bzip2 compressed. A gzip compressed version is also available: ftp://ftp.gnupg.org/gcrypt/libgcrypt/libgcrypt-1.4.1.tar.gz (1301k) ftp://ftp.gnupg.org/gcrypt/libgcrypt/libgcrypt-1.4.1.tar.gz.sig Alternativley you may upgrade version 1.4.1 using this patch file: ftp://ftp.gnupg.org/gcrypt/libgcrypt/libgcrypt-1.4.1-1.4.2.diff.bz2 (171k) The SHA-1 checksums are: f4eda0d4a63905aef3bcdf24bb3dad787ef4b918 libgcrypt-1.4.2.tar.gz e9c65688e3191c4cad2910bda2f6c69fc05997a2 libgcrypt-1.4.2.tar.bz2 e0e5e4192f144ae0fc093d08aff50b725f46c0f9 libgcrypt-1.4.1-1.4.2.diff.bz2 For help on developing with Libgcrypt you should read the included manual and optional ask on the gcrypt-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], order extensions or support or more general by donating money to the Free Software movement [3]. Commercial support contracts for Libgcrypt are available [4], 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. Many thanks to all who contributed to Libgcrypt development, be it bug fixes, code, documentation, testing or helping users. Happy hacking, Werner [1] See http://www.gnupg.org/documentation/mailing-lists.html . [2] Note that copyright assignments to the FSF are required. [3] For example see http://donate.fsf.org . [4] See the service directory at http://www.gnupg.org/service.html . -- Linux-Kongress 2008 + Hamburg + October 7-10 + www.linux-kongress.org Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 205 bytes Desc: not available URL: From sergi at calcurco.cat Mon Sep 15 12:36:08 2008 From: sergi at calcurco.cat (Sergi Blanch i =?utf-8?q?Torn=C3=A9?=) Date: Mon, 15 Sep 2008 12:36:08 +0200 Subject: implementing the internet draft 'ECC in OpenPGP' Message-ID: <200809151236.17738.sergi@calcurco.cat> Hi! I'm preparing a patch to have implemented the elliptic curve encryption is side the libgcrypt. There are two points that I need to be guide in order to have the methods in the correct place implemented. First of all, the encryption schema uses a Key derivation Function (KDF) from the NIST 'SP800-56A', that could be used in the future in other algorithms. Then implement it inside the cipher/ecc.c file could be incorrect. Where can be the correct place? Second, the algorithm orders to use a aes wrapper from the rfc 3394. Also this would be used from other places on the library. I don't think the correct place for it is the rijndael file. Maybe a new file in cipher directory can be suggested? Then, I'll write it but if it can be done in the correct final position it will save time to the main team. Danke /Sergi. Ps: Oh! future changes on the ecc interface will be necessary to have interoperability according to the mentioned interned draft. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part. URL: From wk at gnupg.org Thu Sep 18 17:23:58 2008 From: wk at gnupg.org (Werner Koch) Date: Thu, 18 Sep 2008 17:23:58 +0200 Subject: Libgcrypt 1.4.3 released Message-ID: <878wtpa35d.fsf@wheatstone.g10code.de> Hello! The GNU project is pleased to announce the availability of Libgcrypt version 1.4.3. Libgcrypt is a general purpose library of cryptographic building blocks. It is originally based on code used by GnuPG. It does not provide any implementation of OpenPGP or other protocols. Thorough understanding of applied cryptography is required to use Libgcrypt. Noteworthy changes in version 1.4.3: * Try to auto-initialize Libgcrypt to minimize the effect of applications not doing that correctly. This is not a perfect solution but given that many applicationion would totally fail without such a hack, we try to help at least with the most common cases. Folks, please read the manual to learn how to properly initialize Libgcrypt! * Auto-initialize the secure memory to 32k instead of aborting the process. * Log fatal errors via syslog. * Changed the name and the semantics of the fips mode config file. * Add convenience macro gcry_fips_mode_active. * More self-tests. * Documentation cleanups. 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/libgcrypt/libgcrypt-1.4.3.tar.bz2 (1062k) ftp://ftp.gnupg.org/gcrypt/libgcrypt/libgcrypt-1.4.3.tar.bz2.sig This file is bzip2 compressed. A gzip compressed version is also available: ftp://ftp.gnupg.org/gcrypt/libgcrypt/libgcrypt-1.4.3.tar.gz (1325k) ftp://ftp.gnupg.org/gcrypt/libgcrypt/libgcrypt-1.4.3.tar.gz.sig Alternativley you may upgrade version 1.4.2 using this patch file: ftp://ftp.gnupg.org/gcrypt/libgcrypt/libgcrypt-1.4.2-1.4.3.diff.bz2 (42k) The SHA-1 checksums are: bdc67c1fdcec464a94dca691615f2335a12db5ce libgcrypt-1.4.3.tar.bz2 3d9d583501ce951596fa7dd3667afd357ac7d056 libgcrypt-1.4.3.tar.gz e28b74c5824364e20ae7f147f1b89925f5426669 libgcrypt-1.4.2-1.4.3.diff.bz2 For help on developing with Libgcrypt you should read the included manual and optional ask on the gcrypt-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], order extensions or support or more general by donating money to the Free Software movement [3]. Commercial support contracts for Libgcrypt are available [4], 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. Many thanks to all who contributed to Libgcrypt development, be it bug fixes, code, documentation, testing or helping users. Happy hacking, Werner [1] See http://www.gnupg.org/documentation/mailing-lists.html . [2] Note that copyright assignments to the FSF are required. [3] For example see http://donate.fsf.org . [4] See the service directory at http://www.gnupg.org/service.html . -- Linux-Kongress 2008 + Hamburg + October 7-10 + www.linux-kongress.org Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 205 bytes Desc: not available URL: From simon at josefsson.org Thu Sep 18 22:52:55 2008 From: simon at josefsson.org (Simon Josefsson) Date: Thu, 18 Sep 2008 22:52:55 +0200 Subject: Libgcrypt 1.4.3 released In-Reply-To: <878wtpa35d.fsf@wheatstone.g10code.de> (Werner Koch's message of "Thu, 18 Sep 2008 17:23:58 +0200") References: <878wtpa35d.fsf@wheatstone.g10code.de> Message-ID: <87y71p5g7s.fsf@mocca.josefsson.org> Werner Koch writes: > The GNU project is pleased to announce the availability of Libgcrypt > version 1.4.3. It works fine here under mingw+wine, and the time problem appears to have been fixed: MD5 0ms 20ms 60ms SHA1 0ms 20ms 60ms RIPEMD160 10ms 20ms 70ms TIGER192 20ms 30ms 80ms ... Thanks, /Simon From ladislav.hagara at unob.cz Fri Sep 19 09:17:09 2008 From: ladislav.hagara at unob.cz (Ladislav Hagara) Date: Fri, 19 Sep 2008 09:17:09 +0200 Subject: [Announce] Libgcrypt 1.4.3 released In-Reply-To: <878wtpa35d.fsf@wheatstone.g10code.de> References: <878wtpa35d.fsf@wheatstone.g10code.de> Message-ID: <48D351F5.7020904@unob.cz> Hi, > The GNU project is pleased to announce the availability of Libgcrypt > version 1.4.3. > seems README comes from 1.4.4. :-) Libgcrypt - The GNU Crypto Library ------------------------------------ Version 1.4.4 -- Ladislav Hagara From wk at gnupg.org Fri Sep 19 10:55:59 2008 From: wk at gnupg.org (Werner Koch) Date: Fri, 19 Sep 2008 10:55:59 +0200 Subject: Libgcrypt 1.4.3 released In-Reply-To: <87y71p5g7s.fsf@mocca.josefsson.org> (Simon Josefsson's message of "Thu, 18 Sep 2008 22:52:55 +0200") References: <878wtpa35d.fsf@wheatstone.g10code.de> <87y71p5g7s.fsf@mocca.josefsson.org> Message-ID: <87fxnw7bvk.fsf@wheatstone.g10code.de> On Thu, 18 Sep 2008 22:52, simon at josefsson.org said: > It works fine here under mingw+wine, and the time problem appears to > have been fixed: Yeah, I decided to fix it after I did the first release build and tested this one on Windows before uploading. Funnily the problem now happened on my Windows box too. Salam-Shalom, Werner -- Linux-Kongress 2008 + Hamburg + October 7-10 + www.linux-kongress.org Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. From wk at gnupg.org Fri Sep 19 10:57:02 2008 From: wk at gnupg.org (Werner Koch) Date: Fri, 19 Sep 2008 10:57:02 +0200 Subject: [Announce] Libgcrypt 1.4.3 released In-Reply-To: <48D351F5.7020904@unob.cz> (Ladislav Hagara's message of "Fri, 19 Sep 2008 09:17:09 +0200") References: <878wtpa35d.fsf@wheatstone.g10code.de> <48D351F5.7020904@unob.cz> Message-ID: <87bpyk7btt.fsf@wheatstone.g10code.de> On Fri, 19 Sep 2008 09:17, ladislav.hagara at unob.cz said: > seems README comes from 1.4.4. :-) Yeah, I noticed it right after sending out the announcement. Now I need to remember not to change README for the next release. Shalom-Salam, Werner -- Linux-Kongress 2008 + Hamburg + October 7-10 + www.linux-kongress.org Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. From marcus.brinkmann at ruhr-uni-bochum.de Wed Sep 24 15:56:55 2008 From: marcus.brinkmann at ruhr-uni-bochum.de (Marcus Brinkmann) Date: Wed, 24 Sep 2008 15:56:55 +0200 Subject: Release candidate for Libgcrypt 1.4.2 In-Reply-To: <87hc8z4p38.fsf@mocca.josefsson.org> References: <87r684463i.fsf@wheatstone.g10code.de> <87ljyc9qrc.fsf@mocca.josefsson.org> <87aber6cy4.fsf@mocca.josefsson.org> <87wshv214s.fsf@wheatstone.g10code.de> <87hc8z4p38.fsf@mocca.josefsson.org> Message-ID: <877i91abq0.wl%marcus.brinkmann@ruhr-uni-bochum.de> At Mon, 01 Sep 2008 21:56:43 +0200, Simon Josefsson wrote: > > Werner Koch writes: > > > On Mon, 1 Sep 2008 18:36, simon at josefsson.org said: > > > >> - snprintf (buf, sizeof buf, "%5lums", (unsigned long)t ); > >> + snprintf (buf, sizeof buf, "%5.0fms", (double)t ); > > > > Do you understand why this occurs only with Wine? I have not tested it > > on Wine but it works fine on a standard XP box. Is there a problem with > > my code or is Wine's snprintf broken? > > I actually don't know where the problem is. I can't reproduce it in a > small snippet. FWIW, this also works fine under mingw+wine: > > snprintf (buf, sizeof buf, "%5llums", t ); > > That is arguably more correct, but requires that all Windows supports > %ll. > > Something seems to go wrong when the 64-bit value is cast to a 32-bit > value and then passed as an argument. The values are interesting, see: > > MD5 27574050817572874ms 5083798169452554ms 5083798169452604ms > > That isn't even close to 64-bit or 32-bit boundaries. Hi, I posted this a couple of months ago on the gpg4win devel mailing list. Maybe it is relevant here: if you use Ubuntu 8.04 or Debian unstable, you will encounter the following bug in mingw32-runtime 3.13-1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=452977 Gpg4win packages built with this version of mingw32-runtime are badly broken. The INPUT FD=NR assuan commands will have bizarre NRs, due to the misinterpretation of a %ld format string as %lld. The attached patch fixes this particular problem. This is how it can be installed and used: $ apt-get source mingw32-runtime $ sudo apt-get build-dep mingw32-runtime $ mkdir mingw32-runtime-3.13/debian/patches $ cp 01-snprintf.patch mingw32-runtime-3.13/debian/patches/ $ cd mingw32-runtime-3.13 $ dpkg-buildpackage -rfakeroot -uc -us -b $ sudo dpkg -i ../mingw32-runtime_3.13-1_all.deb Note 1: If you do not recompile version 3.13-1, you might have to change the paths in the patch file. Note 2: You might want to add a new changelog entry to the package (use version number 3.13-1.1). Have fun, Marcus diff -rup mingw-runtime-3.13-20070825-1-orig/mingwex/gdtoa/mingw_snprintf.c mingw-runtime-3.13-20070825-1/mingwex/gdtoa/mingw_snprintf.c --- mingw-runtime-3.13-20070825-1-orig/mingwex/gdtoa/mingw_snprintf.c 2007-08-24 12:57:04.000000000 +0200 +++ mingw-runtime-3.13-20070825-1/mingwex/gdtoa/mingw_snprintf.c 2008-05-14 17:22:06.000000000 +0200 @@ -465,7 +465,7 @@ x_sprintf len = LEN_LL; } else - len = LEN_LL; + len = LEN_L; goto fmtloop; case 'L': flag_ld++; @@ -617,6 +617,7 @@ x_sprintf break; case LEN_S: *(short*)ip = c; + break; case LEN_LL: *(long long*) ip = c; break; From simon at josefsson.org Wed Sep 24 16:06:51 2008 From: simon at josefsson.org (Simon Josefsson) Date: Wed, 24 Sep 2008 16:06:51 +0200 Subject: Release candidate for Libgcrypt 1.4.2 In-Reply-To: <877i91abq0.wl%marcus.brinkmann@ruhr-uni-bochum.de> (Marcus Brinkmann's message of "Wed, 24 Sep 2008 15:56:55 +0200") References: <87r684463i.fsf@wheatstone.g10code.de> <87ljyc9qrc.fsf@mocca.josefsson.org> <87aber6cy4.fsf@mocca.josefsson.org> <87wshv214s.fsf@wheatstone.g10code.de> <87hc8z4p38.fsf@mocca.josefsson.org> <877i91abq0.wl%marcus.brinkmann@ruhr-uni-bochum.de> Message-ID: <87r679bptw.fsf@mocca.josefsson.org> Marcus Brinkmann writes: > if you use Ubuntu 8.04 or Debian unstable, you will encounter the > following bug in mingw32-runtime 3.13-1: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=452977 Ah, thanks. I've asked that a newer version is uploaded to experimental: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498529 I guess other problems have been fixed between 3.13 and 3.15 that we can benefit from too. /Simon