From wk at gnupg.org Fri Jul 6 12:23:54 2007 From: wk at gnupg.org (Werner Koch) Date: Fri, 06 Jul 2007 12:23:54 +0200 Subject: [Announce] GnuPG 2.0.5 released Message-ID: <87abu925l1.fsf@wheatstone.g10code.de> Hello! We are pleased to announce the availability of a new stable GnuPG-2 release: Version 2.0.5. This is maintenance release with a few bug fixes and support for building for W32 platforms. The GNU Privacy Guard (GnuPG) is GNU's tool for secure communication and data storage. It can be used to encrypt data, create digital signatures, help authenticating using Secure Shell and to provide a framework for public key cryptography. It includes an advanced key management facility and is compliant with the OpenPGP and S/MIME standards. GnuPG-2 has a different architecture than GnuPG-1 (e.g. 1.4.7) in that it splits up functionality into several modules. However, both versions may be installed alongside without any conflict. In fact, the gpg version from GnuPG-1 is able to make use of the gpg-agent as included in GnuPG-2 and allows for seamless passphrase caching. The advantage of GnuPG-1 is its smaller size and the lack of dependency on other modules at run and build time. We will keep maintaining GnuPG-1 versions because they are very useful for small systems and for server based applications requiring only OpenPGP support. GnuPG is distributed under the terms of the GNU General Public License (GPL). GnuPG-2 works best on GNU/Linux or *BSD systems. What's New =========== * Switched license to GPLv3. * Basic support for Windows. Run "./autogen.sh --build-w32" to build it. As usual the mingw cross compiling toolchain is required. * Fixed bug when using the --p12-charset without --armor. * The command --gen-key may now be used instead of the gpgsm-gencert.sh script. * Changed key generation to reveal less information about the machine. Bug fixes for gpg2's card key generation. Note that we plan to released GnuPG 1.4.8 within the next few weeks. Getting the Software ==================== Please follow the instructions found at http://www.gnupg.org/download/ or read on: GnuPG 2.0.5 may be downloaded from one of the GnuPG mirror sites or direct from ftp://ftp.gnupg.org/gcrypt/gnupg/ . The list of mirrors can be found at http://www.gnupg.org/mirrors.html . Note, that GnuPG is not available at ftp.gnu.org. On the FTP server and ist mirrors you should find the following files in the gnupg/ directory: gnupg-2.0.5.tar.bz2 (3432k) gnupg-2.0.5.tar.bz2.sig GnuPG source compressed using BZIP2 and OpenPGP signature. gnupg-2.0.4-2.0.5.diff.bz2 (251k) A patch file to upgrade a 2.0.4 GnuPG source tree. This patch does not include updates of the language files. Note, that we don't distribute gzip compressed tarballs. Checking the Integrity ====================== In order to check that the version of GnuPG which you are going to install is an original and unmodified one, you can do it in one of the following ways: * If you already have a trusted version of GnuPG installed, you can simply check the supplied signature. For example to check the signature of the file gnupg-2.0.5.tar.bz2 you would use this command: gpg --verify gnupg-2.0.5.tar.bz2.sig This checks whether the signature file matches the source file. You should see a message indicating that the signature is good and made by that signing key. Make sure that you have the right key, either by checking the fingerprint of that key with other sources or by checking that the key has been signed by a trustworthy other key. Note, that you can retrieve the signing key using the command finger wk ,at' g10code.com or using a keyserver like gpg --recv-key 1CE0C630 The distribution key 1CE0C630 is signed by the well known key 5B0358A2. If you get an key expired message, you should retrieve a fresh copy as the expiration date might have been prolonged. NEVER USE A GNUPG VERSION YOU JUST DOWNLOADED TO CHECK THE INTEGRITY OF THE SOURCE - USE AN EXISTING GNUPG INSTALLATION! * If you are not able to use an old version of GnuPG, you have to verify the SHA-1 checksum. Assuming you downloaded the file gnupg-2.0.5.tar.bz2, you would run the sha1sum command like this: sha1sum gnupg-2.0.5.tar.bz2 and check that the output matches the first line from the following list: 9435e7fabe525ce943a5818008d412ecad244018 gnupg-2.0.5.tar.bz2 e9ff3b74aaa23e6a8503f7b910e44c0c34eead3b gnupg-2.0.4-2.0.5.diff.bz2 Internationalization ==================== GnuPG comes with support for 27 languages. Due to a lot of new and changed strings most translations are not entirely complete. The Swedish, Turkish, German and Russian translations are close to be complete. Documentation ============= We are currently working on an installation guide to explain in more detail how to configure the new features. As of now the chapters on gpg-agent and gpgsm include brief information on how to set up the whole thing. Please watch the GnuPG website for updates of the documentation. In the meantime you may search the GnuPG mailing list archives or ask on the gnupg-users mailing lists for advise on how to solve problems. Many of the new features are around for several years and thus enough public knowledge is already available. KDE's KMail is the most prominent user of GnuPG. In fact it has been developed along with the Kmail folks. Mutt users might want to use the configure option "--enable-gpgme" and "set use_crypt_gpgme" in ~/.muttrc to make use of GnuPG-2 to enable S/MIME in addition to a reworked OpenPGP support. The manual is also available online in HTML format at http://www.gnupg.org/documentation/manuals/gnupg/ and as an PDF at http://www.gnupg.org/documentation/manuals/gnupg.pdf . For questions on how to build for W32 you are best advised to ask on the gnupg-devel mailing list. Support ======= Improving GnuPG is costly, but you can help! We are looking for organizations that find GnuPG useful and wish to contribute back. You can contribute by reporting bugs, improve the software, or by donating money. Commercial support contracts for GnuPG are available, and they help finance continued maintenance. g10 Code GmbH, a Duesseldorf based company owned and headed by GnuPG's principal author, is currently funding GnuPG development. We are always looking for interesting development projects. The GnuPG service directory is available at: http://www.gnupg.org/service.html Thanks ====== We have to thank all the people who helped with this release, be it testing, coding, translating, suggesting, auditing, administering the servers, spreading the word or answering questions on the mailing lists. Happy Hacking, The GnuPG Team (David, Marcus, Werner and all other contributors) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : /pipermail/attachments/20070706/4ec39c8b/attachment.pgp -------------- next part -------------- _______________________________________________ Gnupg-announce mailing list Gnupg-announce at gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-announce From jesus_martinez1967 at yahoo.com.ar Wed Jul 4 17:18:16 2007 From: jesus_martinez1967 at yahoo.com.ar (jesus martinez) Date: Wed, 4 Jul 2007 12:18:16 -0300 (ART) Subject: why exporting private key without passphrase Message-ID: <667694.83397.qm@web32510.mail.mud.yahoo.com> hello. my name is jesus and am writing to you from argentina. i noticed that using GnuPG anyone who has access to a machina where its installed, can export any private key without being asked the correct passphrase. isnt it a security issue ? what is a computer is a public one ? thanks for your comments, j.- __________________________________________________ Pregunt?. Respond?. Descubr?. Todo lo que quer?as saber, y lo que ni imaginabas, est? en Yahoo! Respuestas (Beta). ?Probalo ya! http://www.yahoo.com.ar/respuestas From alex at bofh.net.pl Fri Jul 6 15:50:15 2007 From: alex at bofh.net.pl (Janusz A. Urbanowicz) Date: Fri, 6 Jul 2007 15:50:15 +0200 Subject: why exporting private key without passphrase In-Reply-To: <667694.83397.qm@web32510.mail.mud.yahoo.com> References: <667694.83397.qm@web32510.mail.mud.yahoo.com> Message-ID: <20070706135015.GJ11184@hell.pl> On Wed, Jul 04, 2007 at 12:18:16PM -0300, jesus martinez wrote: > i noticed that using GnuPG anyone who has access to > a machina where its installed, can export any private > key without being asked the correct passphrase. > > isnt it a security issue ? what is a computer is > a public one ? the keys can be copied without running gpg anyway (they are kept in a plain file), so there is no point in protecting export process don't keep secret keys on a public computer =alx -- JID: alex at hell.pl PGP: 0x46399138 od zwracania uwagi na detale s? lekarze, adwokaci, programi?ci i zegarmistrze -- Czerski From dshaw at jabberwocky.com Fri Jul 6 16:06:25 2007 From: dshaw at jabberwocky.com (David Shaw) Date: Fri, 6 Jul 2007 10:06:25 -0400 Subject: why exporting private key without passphrase In-Reply-To: <667694.83397.qm@web32510.mail.mud.yahoo.com> References: <667694.83397.qm@web32510.mail.mud.yahoo.com> Message-ID: <20070706140625.GC30117@jabberwocky.com> On Wed, Jul 04, 2007 at 12:18:16PM -0300, jesus martinez wrote: > > hello. my name is jesus and am writing to you from > argentina. > > i noticed that using GnuPG anyone who has access to > a machina where its installed, can export any private > key without being asked the correct passphrase. > > isnt it a security issue ? what is a computer is > a public one ? In general, the secret keyring is not protected in any way - there is little point. After all, even if GPG added some passphrase protection before it would export a key, you can just go around GPG and do something like "cp secring.gpg /mnt/my-thumb-drive" and take the whole keyring. That said, however, if you are running SELinux you can prevent anything but GPG from reading the secring.gpg. In that case, a passphrase requirement for export is meaningful and useful. It's actually on the todo list, but hasn't happened yet. David From marcus.brinkmann at ruhr-uni-bochum.de Fri Jul 6 16:11:29 2007 From: marcus.brinkmann at ruhr-uni-bochum.de (Marcus Brinkmann) Date: Fri, 06 Jul 2007 16:11:29 +0200 Subject: [PATCH] Fix compilation of gpgme on Mac OS X Tiger In-Reply-To: <87wsxm95tw.fsf@wheatstone.g10code.de> References: <200706262135.22713@erwin.ingo-kloecker.de> <87k5tpkfhm.fsf@wheatstone.g10code.de> <200706282143.01686@erwin.ingo-kloecker.de> <87wsxm95tw.fsf@wheatstone.g10code.de> Message-ID: <87odipmxke.wl%marcus.brinkmann@ruhr-uni-bochum.de> At Fri, 29 Jun 2007 16:46:19 +0200, 'Werner Koch' wrote: > > On Thu, 28 Jun 2007 21:42, kloecker at kde.org said: > > > This code is compile if #ifdef _ASSUAN_IN_GPGME_BUILD_ASSUAN. Should > > gpgme use an installed libassuan? > > Sorry, I missed that you have been talking about the included assuan. > Yeah, you are right that needs to be fixed. > > We need to update the included Assuan version anyway. Please give us a > few days until the standard Assuan is stable enough. It should be fixed now. Please let me know if there are still issues. Marcus From wk at gnupg.org Fri Jul 6 17:04:48 2007 From: wk at gnupg.org (Werner Koch) Date: Fri, 06 Jul 2007 17:04:48 +0200 Subject: why exporting private key without passphrase In-Reply-To: <20070706140625.GC30117@jabberwocky.com> (David Shaw's message of "Fri, 6 Jul 2007 10:06:25 -0400") References: <667694.83397.qm@web32510.mail.mud.yahoo.com> <20070706140625.GC30117@jabberwocky.com> Message-ID: <87ejjly3n3.fsf@wheatstone.g10code.de> On Fri, 6 Jul 2007 16:06, dshaw at jabberwocky.com said: > That said, however, if you are running SELinux you can prevent > anything but GPG from reading the secring.gpg. In that case, a > passphrase requirement for export is meaningful and useful. It's > actually on the todo list, but hasn't happened yet. It would actuall break the SELinux system, thus the proper way to handle it is to have a seperate binary to allow exporting of secret keys. In general exporting a secret key is not useful and a proper checme to do this needs to be integrated into the security setup of the entire system. If GnuPG has been build with SELinux support, exporting a secret key is not possible. Shalom-Salam, Werner From ahasenack at terra.com.br Fri Jul 6 19:51:35 2007 From: ahasenack at terra.com.br (Andreas Hasenack) Date: Fri, 6 Jul 2007 14:51:35 -0300 Subject: gnupg 2.0.5: make check fails for x86_64 Message-ID: <20070706175135.GG5387@mandriva.com.br> Besides updating gnupg from 2.0.4 to 2.0.5, I also had to update libksba and libassuan to 1.0.2. Now make check fails on x86_64 (i386 is fine) with this: make[2]: Entering directory `/tmp/andreas/gnupg2/BUILD/gnupg-2.0.5/common' PASS: t-convert t-gettime.c:68: test 4 failed t-gettime.c:68: test 5 failed t-gettime.c:68: test 6 failed t-gettime.c:68: test 7 failed t-gettime.c:68: test 8 failed t-gettime.c:68: test 15 failed FAIL: t-gettime ==================================== 1 of 2 tests failed I recall make check failing some months ago also only in x86_64, but it just "fixed itself". Probably with some update. From alon.barlev at gmail.com Sat Jul 7 17:13:31 2007 From: alon.barlev at gmail.com (Alon Bar-Lev) Date: Sat, 7 Jul 2007 18:13:31 +0300 Subject: gnupg 2.0.5: make check fails for x86_64 In-Reply-To: <20070706175135.GG5387@mandriva.com.br> References: <20070706175135.GG5387@mandriva.com.br> Message-ID: <9e0cf0bf0707070813r503cc776hadffe15a77924069@mail.gmail.com> We have also problem with this one... http://bugs.gentoo.org/show_bug.cgi?id=184484 Werner, I will be glad to get a patch for this. Alon. On 7/6/07, Andreas Hasenack wrote: > Besides updating gnupg from 2.0.4 to 2.0.5, I also had to update libksba and > libassuan to 1.0.2. Now make check fails on x86_64 (i386 is fine) with this: > > make[2]: Entering directory `/tmp/andreas/gnupg2/BUILD/gnupg-2.0.5/common' > PASS: t-convert > t-gettime.c:68: test 4 failed > t-gettime.c:68: test 5 failed > t-gettime.c:68: test 6 failed > t-gettime.c:68: test 7 failed > t-gettime.c:68: test 8 failed > t-gettime.c:68: test 15 failed > FAIL: t-gettime > ==================================== > 1 of 2 tests failed > > I recall make check failing some months ago also only in x86_64, but it just > "fixed itself". Probably with some update. > > > _______________________________________________ > Gnupg-devel mailing list > Gnupg-devel at gnupg.org > http://lists.gnupg.org/mailman/listinfo/gnupg-devel > From alon.barlev at gmail.com Sat Jul 7 18:14:12 2007 From: alon.barlev at gmail.com (Alon Bar-Lev) Date: Sat, 7 Jul 2007 19:14:12 +0300 Subject: gnupg 2.0.5: make check fails for x86_64 In-Reply-To: <9e0cf0bf0707070813r503cc776hadffe15a77924069@mail.gmail.com> References: <20070706175135.GG5387@mandriva.com.br> <9e0cf0bf0707070813r503cc776hadffe15a77924069@mail.gmail.com> Message-ID: <9e0cf0bf0707070914y3ff17f3cib7a74802191fdaa4@mail.gmail.com> OK. I have a fix at that URL. Werner, I think there is a further problem with timezone settings. Alon. On 7/7/07, Alon Bar-Lev wrote: > We have also problem with this one... > http://bugs.gentoo.org/show_bug.cgi?id=184484 > > Werner, I will be glad to get a patch for this. > > Alon. > > On 7/6/07, Andreas Hasenack wrote: > > Besides updating gnupg from 2.0.4 to 2.0.5, I also had to update libksba and > > libassuan to 1.0.2. Now make check fails on x86_64 (i386 is fine) with this: > > > > make[2]: Entering directory `/tmp/andreas/gnupg2/BUILD/gnupg-2.0.5/common' > > PASS: t-convert > > t-gettime.c:68: test 4 failed > > t-gettime.c:68: test 5 failed > > t-gettime.c:68: test 6 failed > > t-gettime.c:68: test 7 failed > > t-gettime.c:68: test 8 failed > > t-gettime.c:68: test 15 failed > > FAIL: t-gettime > > ==================================== > > 1 of 2 tests failed > > > > I recall make check failing some months ago also only in x86_64, but it just > > "fixed itself". Probably with some update. > > > > > > _______________________________________________ > > Gnupg-devel mailing list > > Gnupg-devel at gnupg.org > > http://lists.gnupg.org/mailman/listinfo/gnupg-devel > > > From kloecker at kde.org Sun Jul 8 21:50:54 2007 From: kloecker at kde.org (Ingo =?iso-8859-1?q?Kl=F6cker?=) Date: Sun, 08 Jul 2007 21:50:54 +0200 Subject: [PATCH] Fix compilation of gpgme on Mac OS X Tiger In-Reply-To: <87odipmxke.wl%marcus.brinkmann@ruhr-uni-bochum.de> References: <200706262135.22713@erwin.ingo-kloecker.de> <87wsxm95tw.fsf@wheatstone.g10code.de> <87odipmxke.wl%marcus.brinkmann@ruhr-uni-bochum.de> Message-ID: <200707082150.59521@erwin.ingo-kloecker.de> On Friday 06 July 2007 16:11, Marcus Brinkmann wrote: > At Fri, 29 Jun 2007 16:46:19 +0200, > > 'Werner Koch' wrote: > > On Thu, 28 Jun 2007 21:42, kloecker at kde.org said: > > > This code is compile if #ifdef _ASSUAN_IN_GPGME_BUILD_ASSUAN. > > > Should gpgme use an installed libassuan? > > > > Sorry, I missed that you have been talking about the included > > assuan. Yeah, you are right that needs to be fixed. > > > > We need to update the included Assuan version anyway. Please give > > us a few days until the standard Assuan is stable enough. > > It should be fixed now. Please let me know if there are still > issues. With today's changes (revision 1224) compilation works. Thanks! Regards, Ingo -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : /pipermail/attachments/20070708/e48d157f/attachment.pgp From wk at gnupg.org Mon Jul 9 10:21:21 2007 From: wk at gnupg.org (Werner Koch) Date: Mon, 09 Jul 2007 10:21:21 +0200 Subject: gnupg 2.0.5: make check fails for x86_64 In-Reply-To: <20070706175135.GG5387@mandriva.com.br> (Andreas Hasenack's message of "Fri, 6 Jul 2007 14:51:35 -0300") References: <20070706175135.GG5387@mandriva.com.br> Message-ID: <87myy6htry.fsf@wheatstone.g10code.de> On Fri, 6 Jul 2007 19:51, ahasenack at terra.com.br said: > t-gettime.c:68: test 4 failed Great t-gettime worked. It revealed a bug. The fix is easy (as also decribed in the gentoo tracker): Repalce the u32 type by time_t. That problem was introduced as I wrote the epoch functions initially using an u32 return time and changed that later while realizing that the u32 type (as used for OpenPGP) is not general enough. Salam-Shalom, Werner From wk at gnupg.org Mon Jul 9 10:25:24 2007 From: wk at gnupg.org (Werner Koch) Date: Mon, 09 Jul 2007 10:25:24 +0200 Subject: gnupg 2.0.5: make check fails for x86_64 In-Reply-To: <9e0cf0bf0707070914y3ff17f3cib7a74802191fdaa4@mail.gmail.com> (Alon Bar-Lev's message of "Sat, 7 Jul 2007 19:14:12 +0300") References: <20070706175135.GG5387@mandriva.com.br> <9e0cf0bf0707070813r503cc776hadffe15a77924069@mail.gmail.com> <9e0cf0bf0707070914y3ff17f3cib7a74802191fdaa4@mail.gmail.com> Message-ID: <87ir8uhtl7.fsf@wheatstone.g10code.de> On Sat, 7 Jul 2007 18:14, alon.barlev at gmail.com said: > Werner, I think there is a further problem with timezone settings. You mean the leap seconds calculations when using TAI as your timezone? (Is that valid at all?). I have not checked POSIX what it tells about this but I recall that there was some disagreement on the leapseconds topic a couple of years ago. One of the problems is that time_t was never meant to describe arbitrary dates and in particular not those in the future. This is why gpgsm uses a string to represent times. Shalom-Salam, Werner From marcus.brinkmann at ruhr-uni-bochum.de Mon Jul 9 15:46:30 2007 From: marcus.brinkmann at ruhr-uni-bochum.de (Marcus Brinkmann) Date: Mon, 09 Jul 2007 15:46:30 +0200 Subject: [Announce] GPGME 1.1.5 released Message-ID: <87myy5heq1.wl%marcus.brinkmann@ruhr-uni-bochum.de> Hi, We are pleased to announce version 1.1.5 of GnuPG Made Easy, a library designed to make access to GnuPG easier for applications. It may be found in the file (about 907 KB/697 KB compressed) ftp://ftp.gnupg.org/gcrypt/gpgme/gpgme-1.1.5.tar.gz ftp://ftp.gnupg.org/gcrypt/gpgme/gpgme-1.1.5.tar.bz2 The following files are also available: ftp://ftp.gnupg.org/gcrypt/gpgme/gpgme-1.1.5.tar.gz.sig ftp://ftp.gnupg.org/gcrypt/gpgme/gpgme-1.1.5.tar.bz2.sig ftp://ftp.gnupg.org/gcrypt/gpgme/gpgme-1.1.4-1.1.5.diff.gz It should soon appear on the mirrors listed at: http://www.gnupg.org/mirrors.html Bug reports and requests for assistance should be sent to: gnupg-devel at gnupg.org The sha1sum checksums for this distibution are 364399bb53ba93373c64b9270a567dcb263fdf3c gpgme-1.1.4-1.1.5.diff.bz2 dc2744b4555192546566bba754e708991677badc gpgme-1.1.5.tar.bz2 cdc16881e84ba475b761225707e2f198352395dd gpgme-1.1.5.tar.bz2.sig 428d0faee47509e69ce95620d5075579296cb884 gpgme-1.1.5.tar.gz 34968a0b335d876c4ab05899b23078badedd319e gpgme-1.1.5.tar.gz.sig Noteworthy changes in version 1.1.5 (2007-07-09) ------------------------------------------------ * Bug and portability fixes (mainly for W32). Marcus Brinkmann mb at g10code.de -- g10 Code GmbH http://g10code.com AmtsGer. Wuppertal HRB 14459 H?ttenstr. 61 Gesch?ftsf?hrung Werner Koch D-40699 Erkrath -=- The GnuPG Experts -=- USt-Id DE215605608 _______________________________________________ Gnupg-announce mailing list Gnupg-announce at gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-announce From alon.barlev at gmail.com Mon Jul 9 19:49:53 2007 From: alon.barlev at gmail.com (Alon Bar-Lev) Date: Mon, 9 Jul 2007 20:49:53 +0300 Subject: gnupg 2.0.5: make check fails for x86_64 In-Reply-To: <87ir8uhtl7.fsf@wheatstone.g10code.de> References: <20070706175135.GG5387@mandriva.com.br> <9e0cf0bf0707070813r503cc776hadffe15a77924069@mail.gmail.com> <9e0cf0bf0707070914y3ff17f3cib7a74802191fdaa4@mail.gmail.com> <87ir8uhtl7.fsf@wheatstone.g10code.de> Message-ID: <9e0cf0bf0707091049j74e513d1g21195976245eff8f@mail.gmail.com> On 7/9/07, Werner Koch wrote: > On Sat, 7 Jul 2007 18:14, alon.barlev at gmail.com said: > > > Werner, I think there is a further problem with timezone settings. > > You mean the leap seconds calculations when using TAI as your timezone? > (Is that valid at all?). I have not checked POSIX what it tells about > this but I recall that there was some disagreement on the leapseconds > topic a couple of years ago. > > One of the problems is that time_t was never meant to describe arbitrary > dates and in particular not those in the future. This is why gpgsm uses > a string to represent times. I am fine with any solution which makes the tests succeed... :) There are advantages for each approach... But if a user prefer to use a valid timezone as TAI timezone you should support this. Alon. From m at riolenz.de Mon Jul 9 18:46:39 2007 From: m at riolenz.de (Mario Lenz) Date: Mon, 09 Jul 2007 18:46:39 +0200 Subject: gpgme_op_verify problem Message-ID: <1183999599.3394.14.camel@etch> Hi! I already asked this on the gnupg-users list, but since nobody helped, I have the same problem with 1.1.5 and "Bug reports and requests for assistance should be sent to" this list... I'm trying to get the plain text out of a signature: #include #include #include int main (int argc, char **argv) { gpgme_ctx_t ctx; gpgme_error_t err; gpgme_data_t plain, signed_text; char buffer[100]; ssize_t size; printf ("%s\n", gpgme_check_version (NULL)); err = gpgme_engine_check_version (GPGME_PROTOCOL_OpenPGP); if (err) exit (1); err = gpgme_new (&ctx); if (!err) { err = gpgme_set_protocol(ctx, GPGME_PROTOCOL_OpenPGP); } if (err) exit (2); err = gpgme_data_new_from_mem (&plain, "Hallo Leute\n", 13, 1); if (err) exit (3); err = gpgme_data_new (&signed_text); if (err) exit (4); err = gpgme_op_sign (ctx, plain, signed_text, GPGME_SIG_MODE_NORMAL); if (err) exit (5); gpgme_data_release (plain); err = gpgme_data_new (&plain); if (err) exit (6); gpgme_data_seek (signed_text, 0, SEEK_SET); err = gpgme_op_verify (ctx, signed_text, NULL, plain); if (err) exit (7); gpgme_data_seek (plain, 0, SEEK_SET); size = gpgme_data_read (plain, buffer, 100); if (size > 0) printf("%s\n", buffer); else printf("failed with size %d\n", size); gpgme_data_release (plain); gpgme_data_release (signed_text); gpgme_release (ctx); return 0; } Compiling with: gcc -o test_rme test_rme.c "$HOME"/src/gpgme-1.1.5/gpgme/.libs/libgpgme.so -Wl,--rpath -Wl,"$HOME"/src/gpgme-1.1.5/gpgme/.libs Output ./test_rme: 1.1.5 failed with size 0 Am I doing it wrong or *is* there a bug? greez Mario PS Normally I wouldn't have sent a mail again... but since you released a new version I wanted to inform you that the problem still exists. And as long as you don't tell me my code is wrong I'll consider it a bug in gpgme :-) -- Rule One: Do not act incautiously when confronting little bald wrinkly smiling men. From marcus.brinkmann at ruhr-uni-bochum.de Mon Jul 9 22:30:24 2007 From: marcus.brinkmann at ruhr-uni-bochum.de (Marcus Brinkmann) Date: Mon, 09 Jul 2007 22:30:24 +0200 Subject: gpgme_op_verify problem In-Reply-To: <1183999599.3394.14.camel@etch> References: <1183999599.3394.14.camel@etch> Message-ID: <87hcodgw0v.wl%marcus.brinkmann@ruhr-uni-bochum.de> At Mon, 09 Jul 2007 18:46:39 +0200, Mario Lenz wrote: > > Hi! > > I already asked this on the gnupg-users list, but since nobody helped, I > have the same problem with 1.1.5 and "Bug reports and requests for > assistance should be sent to" this list... > > I'm trying to get the plain text out of a signature: 1) Please check the error codes of *all* functions that return one, including gpgme_data_seek(). 2) http://www.gnupg.org/faq/gpgme-faq.html Why does the function gpgme_data_seek not work? You probably did not compile the program with largefile support. GPGME is compiled with largefile support by default, so off_t is a 64-bit data type. Because gpgme_data_seek uses off_t as a parameter type, you have to compile your program with largefile support as well, so that the data types used by GPGME and by your program match. Note that you have to compile your program with largefile support even if you do not use gpgme_data_seek, because file descriptors are exchanged between the program and GPGME. The GPGME documentation contains much more information on the subject. See section 2.3 Largefile support of the GPGME Reference Manual. > Compiling with: gcc -o test_rme test_rme.c > "$HOME"/src/gpgme-1.1.5/gpgme/.libs/libgpgme.so -Wl,--rpath > -Wl,"$HOME"/src/gpgme-1.1.5/gpgme/.libs You should add -D_FILE_OFFSET_BITS=64 here. Thanks, Marcus From wk at gnupg.org Tue Jul 10 08:45:20 2007 From: wk at gnupg.org (Werner Koch) Date: Tue, 10 Jul 2007 08:45:20 +0200 Subject: gnupg 2.0.5: make check fails for x86_64 In-Reply-To: <9e0cf0bf0707091049j74e513d1g21195976245eff8f@mail.gmail.com> (Alon Bar-Lev's message of "Mon, 9 Jul 2007 20:49:53 +0300") References: <20070706175135.GG5387@mandriva.com.br> <9e0cf0bf0707070813r503cc776hadffe15a77924069@mail.gmail.com> <9e0cf0bf0707070914y3ff17f3cib7a74802191fdaa4@mail.gmail.com> <87ir8uhtl7.fsf@wheatstone.g10code.de> <9e0cf0bf0707091049j74e513d1g21195976245eff8f@mail.gmail.com> Message-ID: <87ir8sbvun.fsf@wheatstone.g10code.de> On Mon, 9 Jul 2007 19:49, alon.barlev at gmail.com said: > I am fine with any solution which makes the tests succeed... :) > There are advantages for each approach... > But if a user prefer to use a valid timezone as TAI timezone you > should support this. Please help me to duplicate the problem. I simply can't. t-gettime.c tests the back and forth conversion between gmtime(3) and timegm(3). From my understanding the locale won't matter. The input is a time_t which is a specific way to describe the number of seconds since Epoch. That number should be returned by timegm. The problem seems to be that you are using the timegm emulation in jnlib/mischelp.c which uses mktime and a TZ=UTC. To me this seems to be correct interpretation of POSIX. Only localtime(3) should take TAI or any other conversion into acount. What is your environment? echo "$TZ"; zdump UTC What OS and libc are you using? Is HAVE_TIMEGM defined in your config.h? Salam-Shalom, Werner From alex at bofh.net.pl Tue Jul 10 14:57:21 2007 From: alex at bofh.net.pl (Janusz A. Urbanowicz) Date: Tue, 10 Jul 2007 14:57:21 +0200 Subject: why exporting private key without passphrase In-Reply-To: <554066.76473.qm@web32512.mail.mud.yahoo.com> References: <20070706135015.GJ11184@hell.pl> <554066.76473.qm@web32512.mail.mud.yahoo.com> Message-ID: <20070710125720.GO11184@hell.pl> On Sun, Jul 08, 2007 at 03:07:08PM +0000, jesus martinez wrote: > Janusz, thanks for replying ! > > in my work, many people uses my computer. > > - what do i have to do to avoid them to access to > my private key ? Private keys are usually stored on a filesystem in a plain file. Depending on the operating system you run, prohibit other users from accessing that file (or your whole home directory). You can use GPG smartcard, in that scenario, your secret keys reside on the card. To sign or decrypt you put the card in the reader connected to the computer. When somebody uses the computer, you take away the card with your keys. > - what happend if there is a trojan made to > get private keys ? If you use normal storage (file on a filesystem), you lose. If you use a smartcard, a trojan can only decrypt or sign something instead of file you specify. > i really think that a passpphrase must > be asked to export private keys. > > what do you think ? and what can i do to protect my > self ? Define your threat model. Make a description of what is the situation, what you want to do, and what you can do (for example if you have administrative access to the computer). Then look for solution. =alx -- JID: alex at hell.pl PGP: 0x46399138 od zwracania uwagi na detale s? lekarze, adwokaci, programi?ci i zegarmistrze -- Czerski -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : /pipermail/attachments/20070710/8d99b750/attachment.pgp From wk at gnupg.org Tue Jul 10 16:40:54 2007 From: wk at gnupg.org (Werner Koch) Date: Tue, 10 Jul 2007 16:40:54 +0200 Subject: [Announce] Gpg4win 1.1.1 released Message-ID: <87644s724p.fsf@wheatstone.g10code.de> Hi! We are pleased to announce the availability of Gpg4win, version 1.1.1. This is a maintenance release. It fixes a bug introduced with the last release (problems using gpg via %PATH%), prepares the road for future support of the S/MIME protocol and updates Sylpheed-Claws to its current stable version. About Gpg4win ------------- The Gpg4win project aims at updating the Gpg4win Windows installation package with GnuPG encryption tool, associated applications and documentation on a regular basis. Especially the documentation (handbooks "Novices", "Einsteiger" and "Durchblicker") are directly maintained as part of the gpg4win project. It is an international project. Due to the origin of the project the German language is fully supported. People helping with translations are very welcome! The main difference compared to all other similar approaches (mainly GnuPP, GnuPT, Windows Privacy Tools and GnuPG-Basics) is that the first thing developed was the Gpg4win-Builder. This builder allows to easily create new gpg4win.exe installers with updated components. The builder runs on any decent Unix system, preferable Debian GNU/Linux. Almost all products are automatically cross-compiled for integration into the installer. With this concept it is hoped to prevent quick aging of the installer package. This is due to easier updating and less dependancy on single developers. Noteworthy changes in version 1.1.1 (2007-07-10) ------------------------------------------------ * Replaced Sylpheed-Claws by a current Claws-Mail package. * Add command line tools for CMS (S/MIME) to the standard installer. * Translations of the installer are now done in the usual GNU gettext way. * Fixed a couple of bugs. * Included components are: GnuPG: 1.4.7 GnuPG2: 2.0.5 [*] GPA: 0.7.6 GPGol: 0.9.91 GPGee: 1.3.1 WinPT: 1.2.0 Claws-Mail: 2.10.0 [*] Novices: 1.0.0 Einsteiger: 2.0.2 Durchblicker: 2.0.2 (Marked packages are updated since the last release) Future Work ----------- * We are currently working on integrating S/MIME support into Claws-Mail. * IMAP support for Claws-Mail is also in the works. Using GPG via %PATH% -------------------- As of version 1.1.0, Gpg4win updates the PATH variable to include a new public directory containing the command line tools of Gpg4win. To avoid having a bunch of DLLs in the PATH a special wrapper is used to access these tools. With this release the wrapper should actually work and allows access to gpg, gpgsm and gpg-connect-agent from anywhere in the system without the need to know where Gpg4win has been installed. Developers of frontends making use of Gpg4win might want to avoid the use of these wrappers. A hidden option in the wrapper makes the actual used binary available. For example, running "gpg --version --version" will print the following to stdout if the wrapper is being used: gpgwrap (Gpg4win) 1.1.1 ;C:\Programme\GNU\GnuPG\gpg.exe gpg (GnuPG) 1.4.7 .... The string after the semicolon to the end of the first line may be used for future invocations of gpg.exe. Installation ------------ For installation instructions, please visit http://www.gpg4win.org or read on. Developers who want to *build an installer* need to get the following files from http://wald.intevation.org/projects/gpg4win/ : gpg4win-1.1.1.tar.bz2 (4.3M) gpg4win-1.1.1.tar.bz2.sig The second file is a digital signature of the the first file. Either check that this signature is fine or compare with the checksums given below. (see also http://www.gnupg.org/download/integrity_check.html) The *ready to use installer* is available at: http://ftp.gpg4win.org/gpg4win-1.1.1.exe (9.0M) http://ftp.gpg4win.org/gpg4win-1.1.1.exe.sig Or using the ftp protocol at: ftp://ftp.gpg4win.org/gpg4win/gpg4win-1.1.0.exe (9.0M) ftp://ftp.gpg4win.org/gpg4win/gpg4win-1.1.0.exe.sig SHA1 and MD5 checksums for these files are given below. If you don't need the manuals or the GnuPG2 command line tools for S/MIME, you might alternatively download the "light" version of the installer: http://ftp.gpg4win.org/gpg4win-light-1.1.1.exe (5.7M) http://ftp.gpg4win.org/gpg4win-light-1.1.1.exe.sig or using FTP at: ftp://ftp.gpg4win.org/gpg4win/gpg4win-1.1.1.exe (5.7M) ftp://ftp.gpg4win.org/gpg4win/gpg4win-1.1.1.exe.sig A separate installer with the the sources used to build the above installer is available at: ftp://ftp.gpg4win.org/gpg4win/gpg4win-src-1.1.1.exe (57M) ftp://ftp.gpg4win.org/gpg4win/gpg4win-src-1.1.1.exe.sig Most people don't need this source installer; it is merely stored on that server to satisfy the conditions of the GPL. In general it is better to get the gpg4win builder tarball (see above) and follow the instructions in the README to build new installers; building the installer is not possible on Windows machines and works best on current Debian GNU/Linux systems (we use the mingw32 package from Sid). SHA1 checksums are: 14ce65038cc6814649bf17be136271da7dd6bbeb gpg4win-1.1.1.exe 7bc5dea3eb3b1f90898dc881fbc882fb04aa44af gpg4win-light-1.1.1.exe 6ce77994eb181cca823d9c28444cd7b95f0c1af3 gpg4win-src-1.1.1.exe 8ffcaac64751f4df6e4e8f42be682845ee7da579 gpg4win-1.1.1.tar.bz2 MD5 checksums are: b7d78ac0fadf49725dcb99e764a99bd3 gpg4win-1.1.1.exe bb80feedfeb8bd5187bd43d53bfdf4d5 gpg4win-light-1.1.1.exe 9e565ffd67eeb66fed78fada3c92260d gpg4win-src-1.1.1.exe b6c4fb52319b1d10b0fde01b71297218 gpg4win-1.1.1.tar.bz2 If you have problems downloading the above files, you may try the mirror server http://ftp.no.gpg4win.org/pub/gpg4win/ . We like to thank the authors of the included packages, the NSIS authors, all other contributors and first of all, those folks who stayed with us and tested the early releases of gpg4win. To help furthering this project, please consider to sponsor the development. See http://www.gpg4win.org . Happy hacking, The Gpg4win hackers -- g10 Code GmbH http://g10code.com AmtsGer. Wuppertal HRB 14459 H?ttenstr. 61 Gesch?ftsf?hrung Werner Koch D-40699 Erkrath -=- The GnuPG Experts -=- USt-Id DE215605608 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : /pipermail/attachments/20070710/ac700c15/attachment.pgp -------------- next part -------------- _______________________________________________ Gnupg-announce mailing list Gnupg-announce at gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-announce From alon.barlev at gmail.com Wed Jul 11 05:13:37 2007 From: alon.barlev at gmail.com (Alon Bar-Lev) Date: Wed, 11 Jul 2007 06:13:37 +0300 Subject: gnupg 2.0.5: make check fails for x86_64 In-Reply-To: <87ir8sbvun.fsf@wheatstone.g10code.de> References: <20070706175135.GG5387@mandriva.com.br> <9e0cf0bf0707070813r503cc776hadffe15a77924069@mail.gmail.com> <9e0cf0bf0707070914y3ff17f3cib7a74802191fdaa4@mail.gmail.com> <87ir8uhtl7.fsf@wheatstone.g10code.de> <9e0cf0bf0707091049j74e513d1g21195976245eff8f@mail.gmail.com> <87ir8sbvun.fsf@wheatstone.g10code.de> Message-ID: <9e0cf0bf0707102013p8747091g47163f48b33c9798@mail.gmail.com> On 7/10/07, Werner Koch wrote: > Please help me to duplicate the problem. I simply can't. $ TZ="UTC" ./t-gettime --verbose $ TZ="right/UTC" ./t-gettime --verbose t-gettime.c:68: test 2 failed string `19980815T143712' exp: 903191832 got: 903191853 t-gettime.c:68: test 9 failed string `20010101T123456' exp: 978352496 got: 978352518 t-gettime.c:68: test 10 failed string `20070629T160000' exp: 1183132800 got: 1183132823 t-gettime.c:68: test 11 failed string `20070629T160000:' exp: 1183132800 got: 1183132823 t-gettime.c:68: test 12 failed string `20070629T160000,' exp: 1183132800 got: 1183132823 t-gettime.c:68: test 13 failed string `20070629T160000 ' exp: 1183132800 got: 1183132823 t-gettime.c:68: test 14 failed string `20070629T160000 ' exp: 1183132800 got: 1183132823 > What is your environment? echo "$TZ"; zdump UTC $ TZ="UTC" /usr/sbin/zdump UTC UTC Wed Jul 11 03:11:35 2007 UTC $ TZ="right/UTC" /usr/sbin/zdump UTC UTC Wed Jul 11 03:11:13 2007 UTC > What OS and libc are you using? Portage 2.1.3_rc6 (selinux/x86/2006.1, gcc-4.1.2, glibc-2.5-r4, 2.6.21-suspend2-r6 i686) ================================================================= System uname: 2.6.21-suspend2-r6 i686 Intel(R) Pentium(R) M processor 1.80GHz Gentoo Base System release 1.12.9 Timestamp of tree: Wed, 11 Jul 2007 01:47:01 +0000 dev-java/java-config: 1.3.7, 2.0.33-r1 dev-lang/python: 2.4.4-r4 dev-python/pycrypto: 2.0.1-r5 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.23b virtual/os-headers: 2.6.17-r2 > Is HAVE_TIMEGM defined in your config.h? Yes. Alon. From brian.mcardle at heanet.ie Wed Jul 11 14:14:57 2007 From: brian.mcardle at heanet.ie (Brian McArdle) Date: Wed, 11 Jul 2007 13:14:57 +0100 Subject: Mirror in Ireland Message-ID: <1184156097.5768.88.camel@SIRIUS> Hi there, During a review of our mirrored services here at HEAnet, we noticed that although we are actively mirroring your content, we do not appear on your list of mirrors at http://www.gnupg.org/(en)/download/mirrors.html. Your mirrored data can be accessed via FTP: ftp://ftp.heanet.ie/mirrors/ftp.gnupg.org/gcrypt/ HTTP: http://ftp.heanet.ie/mirrors/ftp.gnupg.org/gcrypt/ rsync: rsync://ftp.heanet.ie/mirrors/ftp.gnupg.org/gcrypt/ We are located in Dublin, Ireland - technical information can be found at http://ftp.heanet.ie/about/. We sync with your data four times a day - you can view the status of the last sync at http://ftp.heanet.ie/pub/heanet/log/gnupg/. If you have any questions or queries I am more than happy to help! Regards, Brian McArdle. -- Brian McArdle, Managed Network Services HEAnet Limited, Ireland's Education and Research Network 1st Floor, 5 George's Dock, IFSC, Dublin 1. Tel: +353-1-660 9040 Fax: +353-1-660 3666 Web: http://www.heanet.ie/ Registered in Ireland, no 275301 From wk at gnupg.org Wed Jul 11 08:23:34 2007 From: wk at gnupg.org (Werner Koch) Date: Wed, 11 Jul 2007 08:23:34 +0200 Subject: gnupg 2.0.5: make check fails for x86_64 In-Reply-To: <9e0cf0bf0707102013p8747091g47163f48b33c9798@mail.gmail.com> (Alon Bar-Lev's message of "Wed, 11 Jul 2007 06:13:37 +0300") References: <20070706175135.GG5387@mandriva.com.br> <9e0cf0bf0707070813r503cc776hadffe15a77924069@mail.gmail.com> <9e0cf0bf0707070914y3ff17f3cib7a74802191fdaa4@mail.gmail.com> <87ir8uhtl7.fsf@wheatstone.g10code.de> <9e0cf0bf0707091049j74e513d1g21195976245eff8f@mail.gmail.com> <87ir8sbvun.fsf@wheatstone.g10code.de> <9e0cf0bf0707102013p8747091g47163f48b33c9798@mail.gmail.com> Message-ID: <87odijv4pl.fsf@wheatstone.g10code.de> On Wed, 11 Jul 2007 05:13, alon.barlev at gmail.com said: > Portage 2.1.3_rc6 (selinux/x86/2006.1, gcc-4.1.2, glibc-2.5-r4, Okay, I need to check glibc 2.5. I have only looked at 2.4 and not copy of 2.5 available right now. Shalom-Salam, Werner From wk at gnupg.org Thu Jul 12 07:48:33 2007 From: wk at gnupg.org (Werner Koch) Date: Thu, 12 Jul 2007 07:48:33 +0200 Subject: Mirror in Ireland In-Reply-To: <1184156097.5768.88.camel@SIRIUS> (Brian McArdle's message of "Wed, 11 Jul 2007 13:14:57 +0100") References: <1184156097.5768.88.camel@SIRIUS> Message-ID: <87ps2yi34e.fsf@wheatstone.g10code.de> On Wed, 11 Jul 2007 14:14, brian.mcardle at heanet.ie said: > During a review of our mirrored services here at HEAnet, we noticed that > although we are actively mirroring your content, we do not appear on > your list of mirrors at http://www.gnupg.org/(en)/download/mirrors.html. Thanks. The updated list will show up this afternoon. Salam-Shalom, Werner From m.zdila at episoftware.com Sat Jul 14 09:54:32 2007 From: m.zdila at episoftware.com (M.Zdila/EpiSoftware Ltd.) Date: Sat, 14 Jul 2007 09:54:32 +0200 Subject: problem with S/MIME signature Message-ID: <200707140954.35680.m.zdila@episoftware.com> Hello I have problem with one S/MIME signature and it seems like a bug in GnuPG. I am getting "bad signature" error on signed mail. This error occures in KMail that uses gpgsm, but not in Mozilla Thunderbird. Other S/MIME signed mail in KMail works correctly. I was testing with gpgsm 2.0.3 and 2.0.4. Please see also attached log. I would like to ask somebody trusted to send me his public PGP key so I would send him encrypted all necessary data to check it on his own as I don't want to make this mail public. Thanks in advance Best regards -- Martin Zdila Analyst/Developer EpiSoftware Slovakia Ltd. Letna 27, 043 14 Kosice tel:+421-908-363-848 tel:+421-55-6770-420 mailto:m.zdila at episoftware.com http://www.episoftware.com xmpp:zdila at jabber.sk callto://m.zdila/ -------------- next part -------------- A non-text attachment was scrubbed... Name: gpgsm.log Type: text/x-log Size: 13080 bytes Desc: not available Url : /pipermail/attachments/20070714/49ac9336/attachment.bin -------------- 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 : /pipermail/attachments/20070714/49ac9336/attachment.pgp From wk at gnupg.org Mon Jul 16 11:56:49 2007 From: wk at gnupg.org (Werner Koch) Date: Mon, 16 Jul 2007 11:56:49 +0200 Subject: 2.0.5 too many open files fix Message-ID: <87y7hgd63i.fsf@wheatstone.g10code.de> Hi, Just this morning I figured out that gpg-agent does not anymore close all files. This is in particular annoying if you use ssh along with the agent. The patch is simple: * estream.c (es_func_file_create): Clear NO_CLOSE flag. --- common/estream.c (revision 4541) +++ common/estream.c (working copy) @@ -861,6 +861,7 @@ #endif file_cookie->fd = fd; + file_cookie->no_close = 0; *cookie = file_cookie; *filedes = fd; The fix is already in the SVN. Shalom-Salam, Werner From JPClizbe at tx.rr.com Thu Jul 19 11:25:22 2007 From: JPClizbe at tx.rr.com (John Clizbe) Date: Thu, 19 Jul 2007 04:25:22 -0500 Subject: Spelling error in 1.4 svn Message-ID: <469F2E02.9060008@tx.rr.com> $ diff -uarN g10/gpg.c~ g10/gpg.c --- g10/gpg.c~ 2007-07-19 02:31:19 -0500 +++ g10/gpg.c 2007-07-19 04:23:52 -0500 @@ -2849,8 +2849,8 @@ #endif #ifdef USE_CAMELLIA /* We better also print a runtime warning if people build it with - support for Camellia (which is not yet defiend by OpenPGP). */ - log_info ("WARNING: This version has been build with support for the " + support for Camellia (which is not yet defined by OpenPGP). */ + log_info ("WARNING: This version has been built with support for the " "Camellia cipher.\n"); log_info (" It is for testing only and is NOT for production " "use!\n"); -- John P. Clizbe Inet: John (a) Mozilla-Enigmail.org You can't spell fiasco without SCO. PGP/GPG KeyID: 0x608D2A10/0x18BB373A "what's the key to success?" / "two words: good decisions." "what's the key to good decisions?" / "one word: experience." "how do i get experience?" / "two words: bad decisions." "Just how do the residents of Haiku, Hawai'i hold conversations?" -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 663 bytes Desc: OpenPGP digital signature Url : /pipermail/attachments/20070719/e23546e7/attachment-0001.pgp From dshaw at jabberwocky.com Thu Jul 19 14:45:11 2007 From: dshaw at jabberwocky.com (David Shaw) Date: Thu, 19 Jul 2007 08:45:11 -0400 Subject: Spelling error in 1.4 svn In-Reply-To: <469F2E02.9060008@tx.rr.com> References: <469F2E02.9060008@tx.rr.com> Message-ID: <20070719124510.GA11430@jabberwocky.com> On Thu, Jul 19, 2007 at 04:25:22AM -0500, John Clizbe wrote: > $ diff -uarN g10/gpg.c~ g10/gpg.c > --- g10/gpg.c~ 2007-07-19 02:31:19 -0500 > +++ g10/gpg.c 2007-07-19 04:23:52 -0500 > @@ -2849,8 +2849,8 @@ > #endif > #ifdef USE_CAMELLIA > /* We better also print a runtime warning if people build it with > - support for Camellia (which is not yet defiend by OpenPGP). */ > - log_info ("WARNING: This version has been build with support for the " > + support for Camellia (which is not yet defined by OpenPGP). */ > + log_info ("WARNING: This version has been built with support for the " Indeed. David From eric at debian.org Sun Jul 22 22:02:35 2007 From: eric at debian.org (Eric Dorland) Date: Sun, 22 Jul 2007 16:02:35 -0400 Subject: Remove --print-atr from scdaemon docs Message-ID: <20070722200235.GE6089@gambit> Hello, The scdaemon documentation still refers to the --print-atr option that no longer exists. Here's a patch to remove it. diff --git a/doc/scdaemon.texi b/doc/scdaemon.texi index f8bab80..25e9d49 100644 --- a/doc/scdaemon.texi +++ b/doc/scdaemon.texi @@ -93,11 +93,6 @@ may be used to get the name of that extra socket. Run the program in the background. This option is required to prevent it from being accidently running in the background. - at item --print-atr - at opindex print-atr -This is mainly a debugging command, used to print the ATR -(Answer-To-Reset) of a card and exit immediately. - @end table -- Eric Dorland ICQ: #61138586, Jabber: hooty at jabber.com 1024D/16D970C6 097C 4861 9934 27A0 8E1C 2B0A 61E9 8ECF 16D9 70C6 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : /pipermail/attachments/20070722/d39ae6b6/attachment.pgp From Christian.Kamps at gmx.de Tue Jul 24 09:42:16 2007 From: Christian.Kamps at gmx.de (Christian Kamps) Date: Tue, 24 Jul 2007 09:42:16 +0200 Subject: GPGME-Error rungpg.c:487: command_handler: Assertion `gpg->cmd.code' failed. Message-ID: <1185262936.8647.22.camel@gollum> Hello, I have developed a c/c++ program for automatic email verification and decryption, which reads the email via STDIN and returns the resulting email via STDOUT. According to some tests the program works fine - but there's still one single error that's buggering me. The program should in _any case something goes wrong_ give the original email back via STDOUT. It does so with all my original testmails (with and without attachments, PGP/inline, PGP/MIME - doesn't matter) - but it should also work with manipulated emails. So i manipulated all of my testmails and saved them to different names and tried the program again. Goal is clear - the program should give an error that a decryption or verification was not possible an return the original email. All fine - but when I run a bash-script which calls my program and one email after another only one single manipulated mail gives this error (In the following I shortened the stdout to out.txt and stderr to err.txt - all of the program-calls have different output-files): 8345 Aborted (core dumped) ./check out.txt 2>err.txt last few lines of STDERR (err.txt) are: - gpgme-context created - gpgme-data-objekt msg created (MIME) - gpgme-data-object sig created (MIME) check: rungpg.c:487: command_handler: Assertion `gpg->cmd.code' failed. out.txt is empty. Now comes the weird part: If I only run the single command "./check out.txt 2>err.txt" from commandline all works perfectly fine, err.txt says "could not decrypt" and out.txt contains the original email. And even weirder - when I run the bash-script mentioned above on two other machines it works perfectly fine on one of them. I tried on all of these machines with - GPG 1.4.6, gpgme-1.1.4, libgpg-error-1.4 - GPG 1.4.6, gpgme-1.1.5, libgpg-error-1.5 Athlon 3000+ 512MB RAM Ubuntu 7.04 Bash-Script failes Pentium3 1Ghz 512MB RAM Debian 4.0 Bash-Script failes Duron 900Mhz 384MB RAM Debian 4.0 Bash-Script works Confused and hoping for some thoughts Christian From marcus.brinkmann at ruhr-uni-bochum.de Tue Jul 24 13:52:04 2007 From: marcus.brinkmann at ruhr-uni-bochum.de (Marcus Brinkmann) Date: Tue, 24 Jul 2007 13:52:04 +0200 Subject: GPGME-Error rungpg.c:487: command_handler: Assertion `gpg->cmd.code' failed. In-Reply-To: <1185262936.8647.22.camel@gollum> References: <1185262936.8647.22.camel@gollum> Message-ID: <87fy3ekoij.wl%marcus.brinkmann@ruhr-uni-bochum.de> At Tue, 24 Jul 2007 09:42:16 +0200, Christian Kamps wrote: > 8345 Aborted (core dumped) ./check out.txt 2>err.txt > > last few lines of STDERR (err.txt) are: > - gpgme-context created > - gpgme-data-objekt msg created (MIME) > - gpgme-data-object sig created (MIME) > check: rungpg.c:487: command_handler: Assertion `gpg->cmd.code' failed. Three ideas: Run with valgrind to check for memory access errors (in your code and in GPGME). Run with GPGME_DEBUG=3 and see if the log reveals something. Attach gdb to the core file or if possible at run time and try to find out what's going on. If you send me your files I can try to reproduce it here. Thanks, Marcus From Christian.Kamps at gmx.de Tue Jul 24 14:42:00 2007 From: Christian.Kamps at gmx.de (Christian Kamps) Date: Tue, 24 Jul 2007 14:42:00 +0200 Subject: GPGME-Error rungpg.c:487: command_handler: Assertion `gpg->cmd.code' failed. (solved!?) In-Reply-To: <87fy3ekoij.wl%marcus.brinkmann@ruhr-uni-bochum.de> References: <1185262936.8647.22.camel@gollum> <87fy3ekoij.wl%marcus.brinkmann@ruhr-uni-bochum.de> Message-ID: <1185280920.4805.12.camel@gollum> I don't know what i did exactly (because ich changed nothing directly related to the gpgme-calls) but now it works. > Run with valgrind to check for memory access errors (in your code and > in GPGME). > Run with GPGME_DEBUG=3 and see if the log reveals something. > Attach gdb to the core file or if possible at run time and try to find > out what's going on. Thank you for your recommendations! They'll surely help me next time I'm in trouble :-) I think the error was in my code and related to a string compare (which in the actual version no longer exists), which may not have worked correctly, because of a "\r\n" in the middle of the string. But as I can't reproduce the error anymore myself I'm not really sure. thank you very much (and excuse me for wasting your time!) Christian From seto-kun at freesurf.ch Tue Jul 24 15:43:55 2007 From: seto-kun at freesurf.ch (Gregor Riepl) Date: Tue, 24 Jul 2007 15:43:55 +0200 Subject: libgcrypt symbol prefix bug Message-ID: Hello A while ago, i posted a patch for libgcrypt on the gcrypt-devel mailinglist, but there was no reply since. Is anyone reading that list at all? I found a bug in the autoconf script that prevents it from detecting if the target platform needs a underscore prefix for symbols, which is used in the assembly routines. Can someone comment on my fix? Here's the original mail plus patch, for reference: http:// www.gossamer-threads.com/lists/gnupg/gcrypt/41072 Thanks for checking. Gregor -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2482 bytes Desc: not available Url : /pipermail/attachments/20070724/86b08f93/attachment.bin From wk at gnupg.org Thu Jul 26 10:43:26 2007 From: wk at gnupg.org (Werner Koch) Date: Thu, 26 Jul 2007 10:43:26 +0200 Subject: libgcrypt symbol prefix bug Message-ID: <87tzrrh7wx.fsf@wheatstone.g10code.de> An embedded message was scrubbed... From: Werner Koch Subject: Re: libgcrypt symbol prefix bug Date: Thu, 26 Jul 2007 10:42:42 +0200 Size: 1078 Url: /pipermail/attachments/20070726/3c6ae3f3/attachment.mht From ken at clearshape.com Fri Jul 27 01:23:29 2007 From: ken at clearshape.com (Kenneth Simpson) Date: Thu, 26 Jul 2007 16:23:29 -0700 Subject: linking gpa on Linux Message-ID: <46A92CF1.8080403@clearshape.com> Hi - I can't link ga-0.7.6 on either RHES 3.5 or RHES 4.4 - it fails with the message fileman.o(.text+0x950): In function `dnd_data_received_handler': /usr/local/src/gpa-0.7.6/src/fileman.c:725: undefined reference to `g_uri_list_extract_uris' Any ideas? - - Ken make[2]: Entering directory `/usr/local/src/gpa-0.7.6/src' gcc -I/usr/local/include -I/usr/local/include -DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/X11R6/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/freetype2/config -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -g -O2 -Wall -o gpa gpa.o gpawindowkeeper.o gtktools.o helpmenu.o icons.o gpawidgets.o fileman.o filesigndlg.o encryptdlg.o verifydlg.o keyring.o ownertrustdlg.o keysigndlg.o keygendlg.o keygenwizard.o qdchkpwd.o keyeditdlg.o expirydlg.o keydeletedlg.o keylist.o siglist.o gpasubkeylist.o gpawizard.o gpapastrings.o gpa_license.o keyserver.o w32reg.o hidewnd.o keytable.o gpgmetools.o gpgmeedit.o server_access.o settingsdlg.o passwddlg.o gpacontext.o gpaprogressdlg.o gparecvkeydlg.o gpaoperation.o gpafileop.o gpafiledecryptop.o gpafileencryptop.o gpafilesignop.o gpafileverifyop.o gpakeyop.o gpakeydeleteop.o gpakeysignop.o gpakeytrustop.o gpakeyexpireop.o gpakeypasswdop.o gpaexportop.o gpaexportfileop.o gpaexportclipop.o gpaexportserverop.o gpaimportop.o gpaimportfileop.o gpaimportclipop.o gpaimportserverop.o gpagenkeyop.o gpagenkeyadvop.o gpagenkeysimpleop.o gpabackupop.o gpakeyselector.o options.o -L/usr/local/lib -lgpgme -L/usr/local/lib -lgpg-error -Wl,--export-dynamic -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 -lm -lz fileman.o(.text+0x950): In function `dnd_data_received_handler': /usr/local/src/gpa-0.7.6/src/fileman.c:725: undefined reference to `g_uri_list_extract_uris' collect2: ld returned 1 exit status From ken at clearshape.com Fri Jul 27 02:07:28 2007 From: ken at clearshape.com (Kenneth Simpson) Date: Thu, 26 Jul 2007 17:07:28 -0700 Subject: linking gpa on Linux In-Reply-To: <46A92CF1.8080403@clearshape.com> References: <46A92CF1.8080403@clearshape.com> Message-ID: <46A93740.8030702@clearshape.com> I switched to version ga-0.74 and the problem disappeared. Kenneth Simpson wrote: > Hi - I can't link ga-0.7.6 on either RHES 3.5 or RHES 4.4 - > it fails with the message > > fileman.o(.text+0x950): In function `dnd_data_received_handler': > /usr/local/src/gpa-0.7.6/src/fileman.c:725: undefined reference to > `g_uri_list_extract_uris' > > Any ideas? > > - - Ken > > > > make[2]: Entering directory `/usr/local/src/gpa-0.7.6/src' > gcc -I/usr/local/include -I/usr/local/include -DXTHREADS -D_REENTRANT > -DXUSE_MTSAFE_API -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include > -I/usr/X11R6/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 > -I/usr/include/freetype2 -I/usr/include/freetype2/config > -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -g -O2 -Wall > -o gpa gpa.o gpawindowkeeper.o gtktools.o helpmenu.o icons.o > gpawidgets.o fileman.o filesigndlg.o encryptdlg.o verifydlg.o keyring.o > ownertrustdlg.o keysigndlg.o keygendlg.o keygenwizard.o qdchkpwd.o > keyeditdlg.o expirydlg.o keydeletedlg.o keylist.o siglist.o > gpasubkeylist.o gpawizard.o gpapastrings.o gpa_license.o keyserver.o > w32reg.o hidewnd.o keytable.o gpgmetools.o gpgmeedit.o server_access.o > settingsdlg.o passwddlg.o gpacontext.o gpaprogressdlg.o gparecvkeydlg.o > gpaoperation.o gpafileop.o gpafiledecryptop.o gpafileencryptop.o > gpafilesignop.o gpafileverifyop.o gpakeyop.o gpakeydeleteop.o > gpakeysignop.o gpakeytrustop.o gpakeyexpireop.o gpakeypasswdop.o > gpaexportop.o gpaexportfileop.o gpaexportclipop.o gpaexportserverop.o > gpaimportop.o gpaimportfileop.o gpaimportclipop.o gpaimportserverop.o > gpagenkeyop.o gpagenkeyadvop.o gpagenkeysimpleop.o gpabackupop.o > gpakeyselector.o options.o -L/usr/local/lib -lgpgme -L/usr/local/lib > -lgpg-error -Wl,--export-dynamic -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 > -lgdk_pixbuf-2.0 -lm -lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 > -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 -lm -lz > fileman.o(.text+0x950): In function `dnd_data_received_handler': > /usr/local/src/gpa-0.7.6/src/fileman.c:725: undefined reference to > `g_uri_list_extract_uris' > collect2: ld returned 1 exit status > > > From patrick at mozilla-enigmail.org Fri Jul 27 17:16:20 2007 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Fri, 27 Jul 2007 17:16:20 +0200 Subject: Using gpg-agent on Windows Message-ID: <46AA0C44.2040203@mozilla-enigmail.org> Hi, I'm trying to run gpg-agent as delivered with gpg4win 1.1.1 to enable proper support for it in Enigmail. Unfortunately, I cannot make the process detach, it always stays in the foreground if I run it with "--daemon". Furthermore, I think that some of the command line parameters like --write-env-file don't work as expected. Any ideas? Thanks, Patrick From wk at gnupg.org Fri Jul 27 19:22:49 2007 From: wk at gnupg.org (Werner Koch) Date: Fri, 27 Jul 2007 19:22:49 +0200 Subject: Using gpg-agent on Windows In-Reply-To: <46AA0C44.2040203@mozilla-enigmail.org> (Patrick Brunschwig's message of "Fri, 27 Jul 2007 17:16:20 +0200") References: <46AA0C44.2040203@mozilla-enigmail.org> Message-ID: <87wswl92xi.fsf@wheatstone.g10code.de> On Fri, 27 Jul 2007 17:16, patrick at mozilla-enigmail.org said: > I'm trying to run gpg-agent as delivered with gpg4win 1.1.1 to enable > proper support for it in Enigmail. Well, it might work or might not work. The current SVN evrsion is definitely better. Udner Windows you don't need to care about envvars or --daemon. gpgsm starts gpg-agent on demand. The other tools should do that do but it has not yet been implemented. There are a couple of things to watch out for. For example, all file descriptors are system handles of course. I was recently abale to send a signed mail from claws using gpgme and gpgsm. Shalom-Salam, Werner From stuff at babylonfarms.com Fri Jul 27 20:46:37 2007 From: stuff at babylonfarms.com (Troy) Date: Fri, 27 Jul 2007 13:46:37 -0500 Subject: error building 4552 Message-ID: <46AA3D8D.4080700@babylonfarms.com> Hello, I keep getting an error building 4552 gnupg1. texti :4: @include "version.texti no such file gnupg1. texti :46: warning undefined flag: version gnupg1. texti :46: warning undefined flag: updated gnupg1. texti :103: warning undefined flag: version gnupg1. texti :103: warning undefined flag: updated makeinfo removing output file `gnupg1.info' due to errors; use -- force to preserve I am using mysys building static win32 Troy P.S. my appologies for sending this twice but I realized 1) I sent it from the wrong address & 2) didn't completely proof read it so you don't have to moderate my last post you can just delete it sorry From JPClizbe at tx.rr.com Sat Jul 28 23:22:28 2007 From: JPClizbe at tx.rr.com (John Clizbe) Date: Sat, 28 Jul 2007 16:22:28 -0500 Subject: error building 4552 In-Reply-To: <46AA3D8D.4080700@babylonfarms.com> References: <46AA3D8D.4080700@babylonfarms.com> Message-ID: <46ABB394.1020706@tx.rr.com> Troy wrote: > I keep getting an error building 4552 > > gnupg1. texti :4: @include "version.texti no such file > gnupg1. texti :46: warning undefined flag: version > gnupg1. texti :46: warning undefined flag: updated > gnupg1. texti :103: warning undefined flag: version > gnupg1. texti :103: warning undefined flag: updated > makeinfo removing output file `gnupg1.info' due to errors; use -- > force to preserve Grab an updated version of texinfo. The one distributed with the last MSYS is 4.3. wget \ ftp://download.sourceforge.net/pub/sourceforge/g/gn/gnuwin32/texinfo-4.8-bin.zip unzip texinfo-4.8-bin.zip -d /mingw/ wget \ ftp://download.sourceforge.net/pub/sourceforge/g/gn/gnuwin32/texinfo-4.8-dep.zip unzip texinfo-4.8-dep.zip -d /mingw/ Working on an updated release of MSYS - maybe this fall. If you don't have wget, there's a copy in the wget-1.9.1 mingwPORT package. You can download it from the MinGW SourceForge page. Put the exe in /mingw/bin/, not /bin. -- John P. Clizbe Inet: John (a) Mozilla-Enigmail.org You can't spell fiasco without SCO. PGP/GPG KeyID: 0x608D2A10/0x18BB373A "what's the key to success?" / "two words: good decisions." "what's the key to good decisions?" / "one word: experience." "how do i get experience?" / "two words: bad decisions." "Just how do the residents of Haiku, Hawai'i hold conversations?" -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 663 bytes Desc: OpenPGP digital signature Url : /pipermail/attachments/20070728/7f4882ad/attachment.pgp From patrick at mozilla-enigmail.org Mon Jul 30 13:48:49 2007 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Mon, 30 Jul 2007 13:48:49 +0200 Subject: Windows / Linux encoding issues In-Reply-To: <46AB676A.7090504@gmail.com> References: <46AB676A.7090504@gmail.com> Message-ID: <46ADD021.9020809@mozilla-enigmail.org> Sacha wrote: > Hello, > > I've created my key pair using WinPT under Windows 2000. I used special > characters (like ?, ?, ?, ?, etcetera) in my passphrase. > > Since a hard drive crash, I've installed Gentoo Linux on the computer > and I can not found my Windows 2000 installation CD. I've successfully > imported my private key in GnuPG from a backup, but when I type my > passphrase, GnuPG says that it's a bad passphrase. > > My idea is that there is a charset encoding issue, because under Linux I > have UTF-8 in my X server and ISO-859-1 in the console. And what under > Windows 2000 used is, I really don't know (Windows-1252 ? perhaps...). > > Can you suggest me something to found the right passphrase ? Indeed it's very likely a charset problem. Try to convert your passphrase to Windows-1250 or CP850, using e.g. iconv -Patrick