From wk at gnupg.org Fri Oct 26 16:14:26 2007 From: wk at gnupg.org (Werner Koch) Date: Fri, 26 Oct 2007 16:14:26 +0200 Subject: [Announce] Libgcrypt 1.3.1 released Message-ID: <87tzoem08t.fsf@wheatstone.g10code.de> Hello! We are pleased to announce the availability of Libgcrypt 1.3.1. This is the second 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 compared to 1.3.1 are: * The entire library is now under the LGPLv2. The helper programs and the manual are under the GPLv2. Kudos to Peter Gutmann for giving permissions to relicense the rndw32 and rndunix modules. * The Camellia cipher is now under the LGPL and build by default. * Fixed a bug in the detection of symbol prefixes which inhibited the build of optimzied assembler code on certain systems. * Updated the entropy gatherer for W32. 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 signature is: ftp://ftp.gnupg.org/gcrypt/alpha/libgcrypt/libgcrypt-1.3.1.tar.bz2 (930k) ftp://ftp.gnupg.org/gcrypt/alpha/libgcrypt/libgcrypt-1.3.1.tar.bz2.sig This file is bzip2 compressed. The SHA-1 checksum is: eea6aea27d7e12297630de6b4fcba1b486c809c8 libgcrypt-1.3.1.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 . -- Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : /pipermail/attachments/20071026/8e127367/attachment.pgp From wk at gnupg.org Fri Nov 16 15:38:52 2007 From: wk at gnupg.org (Werner Koch) Date: Fri, 16 Nov 2007 15:38:52 +0100 Subject: [Announce] GnuPG release candidate 1.4.8 Message-ID: <87d4uaxnk3.fsf@wheatstone.g10code.de> Hi, I just uploaded a release candidate for GnuPG 1.4.8: ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-1.4.8rc1.tar.bz2 ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-1.4.8rc1.tar.bz2.sig If you have problems with 1.4.7, you may want to give it a try. Those who reported build problems should also try to build that one and report if the problems persist (to the gnupg-users ML). Note that the language files are not all updated and our translators may want to check whether they find time to send an update in. There are certainly a couple of bugs not yet fixed as we had not the time to work through all bug reports, please complain if there are important things still not resolved. The actual release of 1.4.8 is planned for December 20. Noteworthy changes in version 1.4.8 (unreleased) ------------------------------------------------ * Changed the license to GPLv3. * Improved detection of keyrings specified multiple times. * Changes to better cope with broken keyservers. * Minor bug fixes. * New option --rfc4880 which is currently identical to --openpgp. Happy hacking, Werner -- Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 1557 bytes Desc: not available Url : /pipermail/attachments/20071116/44d2b766/attachment.bin From wk at gnupg.org Mon Dec 3 11:34:03 2007 From: wk at gnupg.org (Werner Koch) Date: Mon, 03 Dec 2007 11:34:03 +0100 Subject: [Announce] Libgcrypt 1.3.2 (devel) released Message-ID: <87wsrwt6ck.fsf@wheatstone.g10code.de> Hello! We are pleased to announce the availability of Libgcrypt 1.3.2. This version should be considered a release candidate for 1.4.0. 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 compared to 1.3.2 are: * The visibility attribute is now used if supported by the toolchain. * The ACE engine of VIA processors is now used for AES-128. * The ASN.1 DER template for SHA-224 has been fixed. 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 signature is: ftp://ftp.gnupg.org/gcrypt/alpha/libgcrypt/libgcrypt-1.3.2.tar.bz2 (941k) ftp://ftp.gnupg.org/gcrypt/alpha/libgcrypt/libgcrypt-1.3.2.tar.bz2.sig This file is bzip2 compressed. The SHA-1 checksum is: a6d7cf7d717edf10718d9200ab7ee11296f984ee libgcrypt-1.3.2.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 . -- Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 204 bytes Desc: not available Url : /pipermail/attachments/20071203/af4f475f/attachment-0001.pgp From wk at gnupg.org Mon Dec 10 20:01:06 2007 From: wk at gnupg.org (Werner Koch) Date: Mon, 10 Dec 2007 20:01:06 +0100 Subject: [Announce] Libgcrypt 1.4.0 (stable) released Message-ID: <87y7c2ml1p.fsf@wheatstone.g10code.de> Hello! We are pleased to announce the availability of Libgcrypt 1.4.0. This is the new stable version of Libgcrypt and upward compatible with the 1.2 series. The 1.2 series will enter end of life state in 2 years on 2009-12-31. 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 between 1.2.x and 1.4.0 are: * Support for SHA-224 and HMAC using SHA-384 and SHA-512. * Support for the SEED cipher. * Support for the Camellia cipher. * Support for OFB encryption mode. * Support for DSA2. * Support for Microsoft Windows. * The entire library is now under the LGPLv2+. The helper programs and the manual are under the GPLv2+. Kudos to Peter Gutmann for giving permissions to relicense the rndw32 and rndunix modules. * The visibility attribute is now used if supported by the toolchain. * The ACE engine of VIA processors is now used for AES-128. * Changed the way the RNG gets initialized. This allows to keep it uninitialized as long as no random numbers are used. * Updated the entropy gatherer for W32. * Made the RNG immune against fork without exec. * Reading and writing the random seed file is now protected by a fcntl style file lock on systems that provide this function. * gcry_mpi_rshift does not anymore truncate the shift count. * Reserved algorithm ranges for use by applications. * The new function gcry_md_debug should be used instead of the gcry_md_start_debug and gcry_md_stop_debug macros. * Non executable stack support is now used by default on systems supporting it. * Assembler support for the AMD64 architecture. * New configure option --enable-mpi-path for optimized builds. * Fixed a bug in the detection of symbol prefixes which inhibited the build of optimized assembler code on certain systems. * New control code GCRYCTL_PRINT_CONFIG to print the build configuration. * Experimental support for ECDSA; should only be used for testing. * 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. * Minor changes to some function declarations. Buffer arguments are now typed as void pointer. This should not affect any compilation. Fixed two bugs in return values and clarified documentation. * Interface changes relative to the 1.2.0 release: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ gcry_fast_random_pol NEW. gcry_md_debug NEW. gcry_sexp_nth_string NEW. GCRY_MD_SHA224 NEW. GCRY_PK_USAGE_CERT NEW. GCRY_PK_USAGE_AUTH NEW. GCRY_PK_USAGE_UNKN NEW. GCRY_PK_ECDSA NEW. GCRY_CIPHER_SEED NEW. GCRY_CIPHER_CAMELLIA128 NEW. GCRY_CIPHER_CAMELLIA192 NEW. GCRY_CIPHER_CAMELLIA256 NEW. GCRYCTL_FAKED_RANDOM_P NEW. GCRYCTL_PRINT_CONFIG NEW. GCRYCTL_SET_RNDEGD_SOCKET NEW. gcry_mpi_scan CHANGED: Argument BUFFER is now void*. gcry_pk_algo_name CHANGED: Returns "?" instead of NULL. gcry_cipher_algo_name CHANGED: Returns "?" instead of "". gcry_pk_spec_t CHANGED: Element ALIASES is now const ptr. gcry_md_write_t CHANGED: Argument BUF is now a const void*. gcry_md_ctl CHANGED: Argument BUFFER is now void*. gcry_cipher_encrypt CHANGED: Arguments IN and OUT are now void*. gcry_cipher_decrypt CHANGED: Arguments IN and OUT are now void*. gcry_sexp_sprint CHANGED: Argument BUFFER is now void*. gcry_create_nonce CHANGED: Argument BUFFER is now void*. gcry_randomize CHANGED: Argument BUFFER is now void*. gcry_cipher_register CHANGED: Argument ALGORITHM_ID is now int*. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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.0.tar.bz2 (942k) ftp://ftp.gnupg.org/gcrypt/libgcrypt/libgcrypt-1.4.0.tar.bz2.sig This file is bzip2 compressed. A gzip compressed version is also available: ftp://ftp.gnupg.org/gcrypt/libgcrypt/libgcrypt-1.4.0.tar.gz (1176k) ftp://ftp.gnupg.org/gcrypt/libgcrypt/libgcrypt-1.4.0.tar.gz.sig The SHA-1 checksums are: cd1b52e8ecfa361737c6f130ed2f1d850e312c16 libgcrypt-1.4.0.tar.bz2 69183b7100b60da8eb1648f49836a611454541bb libgcrypt-1.4.0.tar.gz 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], 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. 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] See the service directory at http://www.gnupg.org/service.html . -- Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 204 bytes Desc: not available Url : /pipermail/attachments/20071210/e4ccd64b/attachment.pgp From wk at gnupg.org Fri Dec 14 14:35:45 2007 From: wk at gnupg.org (Werner Koch) Date: Fri, 14 Dec 2007 14:35:45 +0100 Subject: [Announce] GnuPG: second release candidate for 1.4.8 Message-ID: <87wsrhtn4e.fsf@wheatstone.g10code.de> Hi, I just uploaded a second release candidate for GnuPG 1.4.8: ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-1.4.8rc2.tar.bz2 ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-1.4.8rc2.tar.bz2.sig If you have problems with 1.4.7, you may want to give it a try. Those who reported build problems should also try to build that one and report if the problems persist (to the gnupg-users ML). Note that the language files are not all updated and our translators may want to check whether they find time to send an update in. There are certainly a couple of bugs not yet fixed as we had not the time to work through all bug reports, please complain if there are important things still not resolved. The actual release of 1.4.8 is planned for December 20. Noteworthy changes since the last release candidate --------------------------------------------------- * Allow encryption using legacy Elgamal sign+encrypt keys if option --rfc2440 is used. * Fixed the auto creation of the key stub for smartcards. * Fixed a rare bug in decryption using the OpenPGP card. * Fix RFC-4880 typo in the SHA-224 hash prefix. Old SHA-224 signatures will continue to work. Happy hacking, Werner -- Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 204 bytes Desc: not available Url : /pipermail/attachments/20071214/5e5e14f9/attachment.pgp From wk at gnupg.org Fri Dec 14 17:26:04 2007 From: wk at gnupg.org (Werner Koch) Date: Fri, 14 Dec 2007 17:26:04 +0100 Subject: [Announce] Here comes the release candidate for GnuPG 2.0.8 Message-ID: <87tzmls0o3.fsf@wheatstone.g10code.de> Hi, I just uploaded a release candidate for GnuPG 2.0.8: ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-2.0.8rc1.tar.bz2 ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-2.0.8rc1.tar.bz2.sig Note that the language files are not all updated and our translators may want to check whether they find time to send an update in. There are certainly a couple of bugs not yet fixed as we had not the time to work through all bug reports, please complain if there are important things still not resolved. The actual release of 2.0.8 is also planned for December 20. Noteworthy changes since 2.0.7 ------------------------------ * Make sure that under Windows the file permissions of the socket are taken into account. This required a change of our socket emulation code; thus old GnuPG modules can't be used anymore. * Fixed a crash in gpgconf. * Enhanced gpg-connect-agent with a small scripting language. * New option --list-config for gpgconf. * The envvars XAUTHORITY and PINENTRY_USER_DATA are now passed to the pinentry. * Allow encryption with legacy Elgamal sign+encrypt keys with option --rfc2440. * Fixed the auto creation of the key stub for smartcards. * Fixed a rare bug in decryption using the OpenPGP card. * Creating DSA2 keys is now possible. * New option --extra-digest-algo for gpgsm to allow verification of broken signatures. Note: You need the current version of libassuan (1.0.4) to build this. Happy hacking, Werner -- Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 204 bytes Desc: not available Url : /pipermail/attachments/20071214/7e220758/attachment.pgp From wk at gnupg.org Thu Dec 20 10:40:28 2007 From: wk at gnupg.org (Werner Koch) Date: Thu, 20 Dec 2007 10:40:28 +0100 Subject: [Announce] GnuPG 1.4.8 released Message-ID: <8763ytd7qr.fsf@wheatstone.g10code.de> Hello! We are pleased to announce the availability of a new stable GnuPG-1 release: Version 1.4.8. This is GnuPG's 10th birthday celebration release. The GNU Privacy Guard (GnuPG) is GNU's tool for secure communication and data storage. It is a complete and free replacement of PGP and can be used to encrypt data and to create digital signatures. It includes an advanced key management facility, samrtcard support and is compliant with the OpenPGP Internet standard as described by RFC-4880 (the recently released update of RFC-2440). Note that this version is from the GnuPG-1 series and thus smaller than those from the GnuPG-2 series, easier to build and also better portable. In contrast to GnuPG-2 (e.g version 2.0.8) it comes with no support for S/MIME or other tools useful for desktop environments. Fortunately you may install both versions alongside on the same system without any conflict. Getting the Software ==================== Please follow the instructions found at http://www.gnupg.org/download/ or read on: GnuPG 1.4.8 may be downloaded from one of the GnuPG mirror sites or direct from ftp://ftp.gnupg.org/gcrypt/ . 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 mirrors you should find the following files in the *gnupg* directory: gnupg-1.4.8.tar.bz2 (3242k) gnupg-1.4.8.tar.bz2.sig GnuPG source compressed using BZIP2 and OpenPGP signature. gnupg-1.4.8.tar.gz (4550k) gnupg-1.4.8.tar.gz.sig GnuPG source compressed using GZIP and OpenPGP signature. gnupg-1.4.7-1.4.8.diff.bz2 (330k) A patch file to upgrade a 1.4.7 GnuPG source. Select one of them. To shorten the download time, you probably want to get the BZIP2 compressed file. Please try another mirror if exceptional your mirror is not yet up to date. In the *binary* directory, you should find these files: gnupg-w32cli-1.4.8.exe (2117k) gnupg-w32cli-1.4.8.exe.sig GnuPG compiled for Microsoft Windows and OpenPGP signature. This is a command line only version; the source files are the same as given above. Note, that this is a minimal installer and unless you are just in need for the gpg binary, you are better off using the full featured installer at http://www.gpg4win.org . A new version of Gpg4win, including this version of GnuPG will be available and announced soon. 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-1.4.8.tar.bz2 you would use this command: gpg --verify gnupg-1.4.8.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-1.4.8.tar.bz2, you would run the sha1sum command like this: sha1sum gnupg-1.4.8.tar.bz2 and check that the output matches the second line from the following list: 29803a37645493104b239247505418f9c5bedd88 gnupg-1.4.8.tar.gz 4b63267358e5c70f05b48e27d6877bad2636cabd gnupg-1.4.8.tar.bz2 e69d50a34c9f8d80aca366494228e2be0e8c641b gnupg-1.4.7-1.4.8.diff.bz2 6ef3f9ba7a36ad1da53a02a8733bf77bc5305587 gnupg-w32cli-1.4.8.exe What's New =========== * Changed the license to GPLv3. * Improved detection of keyrings specified multiple times. * Changes to better cope with broken keyservers. * Minor bug fixes. * The new OpenPGP standard is now complete, and has been published as RFC-4880. The GnuPG --openpgp mode (note this is not the default) has been updated to match the new standard. The --rfc2440 option can be used to return to the older RFC-2440 behavior. The main differences between the two are "--enable-dsa2 --no-rfc2440-text --escape-from-lines --require-cross-certification". * By default (i.e. --gnupg mode), --require-cross-certification is now on. --rfc2440-text and --force-v3-sigs are now off. * Allow encryption using legacy Elgamal sign+encrypt keys if option --rfc2440 is used. * Fixed the auto creation of the key stub for smartcards. * Fixed a rare bug in decryption using the OpenPGP card. * Fix RFC-4880 typo in the SHA-224 hash prefix. Old SHA-224 signatures will continue to work. Internationalization ==================== GnuPG comes with support for 28 languages. Due to a lot of new and changed strings some translations are not entirely complete. The Chinese (Simple and Traditional), Czech, Dutch, French, German, Norwegian, Polish, Romanian, Russian, Spanish, Swedish and Turkish translations are close to be complete. 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, order extensions or support or more general by donating money to the Free Software movement (e.g. http://www.fsfeurope.org/help/donate.en.html). Commercial support contracts for GnuPG are available, and they help finance continued maintenance. g10 Code GmbH, a Duesseldorf based company owned and headed by gpg's principal author, is currently funding GnuPG development. We are always looking for interesting development projects. A 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, Werner and the other contributors) -- Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : /pipermail/attachments/20071220/ac14720e/attachment.pgp From wk at gnupg.org Thu Dec 20 10:44:54 2007 From: wk at gnupg.org (Werner Koch) Date: Thu, 20 Dec 2007 10:44:54 +0100 Subject: [Announce] GnuPG 2.0.8 released Message-ID: <87zlw5bsyx.fsf@wheatstone.g10code.de> Hello! We are pleased to announce the availability of a new stable GnuPG-2 release: Version 2.0.8 This is GnuPG's 10th birthday celebration release. 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.8) 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 version 3). GnuPG-2 works best on GNU/Linux or *BSD systems. What's New =========== * Enhanced gpg-connect-agent with a small scripting language. * New option --list-config for gpgconf. * Fixed a crash in gpgconf. * Gpg-agent now supports the passphrase quality bar of the latest Pinentry. * The envvars XAUTHORITY and PINENTRY_USER_DATA are now passed to the pinentry. * Fixed the auto creation of the key stub for smartcards. * Fixed a rare bug in decryption using the OpenPGP card. * Creating DSA2 keys is now possible. * New option --extra-digest-algo for gpgsm to allow verification of broken signatures. * Allow encryption with legacy Elgamal sign+encrypt keys with option --rfc2440. * Windows is now a supported platform. * Made sure that under Windows the file permissions of the socket are taken into account. This required a change of our socket emulation code and changed the IPC protocol under Windows. Getting the Software ==================== Please follow the instructions found at http://www.gnupg.org/download/ or read on: GnuPG 2.0.8 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.8.tar.bz2 (3568k) gnupg-2.0.8.tar.bz2.sig GnuPG source compressed using BZIP2 and OpenPGP signature. gnupg-2.0.7-2.0.8.diff.bz2 (156k) A patch file to upgrade a 2.0.7 GnuPG source tree. This patch does not include updates of the language files. Note, that we don't distribute gzip compressed tarballs for GnuPG-2. 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.8.tar.bz2 you would use this command: gpg --verify gnupg-2.0.8.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.8.tar.bz2, you would run the sha1sum command like this: sha1sum gnupg-2.0.8.tar.bz2 and check that the output matches the first line from the following list: baeb7962f9d3d4628ada78036d1f5d4480aaa2d9 gnupg-2.0.8.tar.bz2 80f8c84834122e988eaeeaddff070097b3a9f383 gnupg-2.0.7-2.0.8.diff.bz2 Internationalization ==================== GnuPG comes with support for 27 languages. Due to a lot of new and changed strings many translations are not entirely complete. The German, Polish, Russian, Swedish and Turkish 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-2. 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 in Portable Document Format at http://www.gnupg.org/documentation/manuals/gnupg.pdf . 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, order extensions or support or more general by donating money to the Free Software movement (e.g. http://www.fsfeurope.org/help/donate.en.html). 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) -- Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : /pipermail/attachments/20071220/22b45e58/attachment-0001.pgp From wk at gnupg.org Thu Dec 20 10:55:16 2007 From: wk at gnupg.org (Werner Koch) Date: Thu, 20 Dec 2007 10:55:16 +0100 Subject: [Announce] GnuPG's 10th birthday Message-ID: <87tzmdbshn.fsf@wheatstone.g10code.de> A Short History of the GNU Privacy Guard ======================================== It's been a decade now that the very first version of the GNU Privacy Guard [0] has been released. This very first version was not yet known under the name of GnuPG but dubbed "g10" as a reference on the German constitution article on freedom of telecommunication (Grundgesetz Artikel 10) and as a pun on the G-10 law which allows the secret services to bypass these constitutional guaranteed freedoms. Version 0.0.0 released on December 20th 1997 [1], was a barely working replacement of PGP avoiding all patented algorithm by using Elgamal and Blowfish instead of RSA and IDEA. It was prominently marked as a test version but nevertheless included most of the features of the current GnuPG. The data format however was not compatible with OpenPGP but oriented towards the PGP 2 format with a few extensions (e.g. to allow streaming of data). The OpenPGP working group was founded back in fall 1997 and I learned a bit to late about it to build "g10" according to the then existing draft. For copyright reasons it was practically not possible to reverse engineer the format used by PGP-5, so the establishment of the OpenPGP WG was the right thing at the right time. Before talking about GnuPG we need to go some more years back in history: To help political activists Phil Zimmermann published a software called Pretty Good Privacy (PGP) in 1991. PGP was designed as an easy to use encryption tool with no backdoors and disclosed source code. PGP was indeed intended to be cryptographically strong and not just pretty good; however it had a couple of inital bugs, most of all a home designed cipher algorithm. With the availability of the source code a community of hackers (Branko Lankester, Colin Plumb, Derek Atkins, Hal Finney, Peter Gutmann and others) helped him to fix these flaws and a get a solid version 2 out. Soon after that the trouble started. As in many counties the use or export of cryptographic devices and software was also strongly restricted in the USA. Only weak cryptography was generally allowed. PGP was much stronger and due to the Usenet and the availability of FTP servers and BBSs, PGP accidently leaked out of the country and soon Phil was sued for unlicensed munitions export. Those export control laws were not quite up to the age of software with the funny effect that exporting the software in printed form seemed not to be restricted. MIT Press thus published a book with the PGP source code which was then scanned outside the USA to form the base of PGP-2i ("i" for international). Since then that version was used widely. The criminal investigations against Phil ended in 1996 and he founded PGP Inc to write PGP-5. The first public release was done in spring 1997. The same year at the 39th IETF meeting at Munich in August Phil Zimmermann and Jon Callas asked the IETF to setup a working group to publish a standard for the protocol used by PGP-5 under the name OpenPGP. The main drive behind this was to allow widespread use of strong encryption even if at some point the new company would decide to stop selling and supporting PGP. As it turned out PGP Inc was acquired by Network Associates just a few months later and in 2002 this company actually ceased support and development of PGP (though the PGP product was later continued by the new PGP Corporation). Also often claimed to be Free Software, PGP has never fulfilled the requirements for it: PGP-5 is straight proprietary software; the availability of the source code alonedoes not make it free. PGP-2 has certain restrictions on commercial use [2] and thus puts restrictions on the software which makes it also non-free. Another problem with PGP-2 is that it requires the use of the patented RSA and IDEA algorithms. The patent on RSA was only valid in the USA but the patent on IDEA was and is still valid [3] in most countries. Although the GNU project listed a requirement for a PGP replacement for some years on its task list, it was not possible to start implementing it as long as patents on all public key algorithms were valid. That changed when in April 1997 the basic patent on public key algorithms expired (the Diffie-Hellman US patent 4200770) and finally in August when the broader Hellman-Merkle patent (4218582) expired. A month later, at the Individual-Network Betriebstagung at Aachen [4], Richard Stallman continued his talk with a BoF session where he asked the European hackers to start implementing public key software. The arms trafficker laws of the USA prohibited the GNU project to write such software in their country or even by US citizens working abroad. Thus he told the European hackers that they are in the unique position to help the GNU with crypto software. Being tired of writing SMGL conversion software and without a current fun project, I soon found my self hacking on PGP-2 parsing code based on the description in RFC-1991 and the pgformat.txt file. As this turned out to be easy I continued and finally came up with code to decrypt and create PGP-2 data. After I told the GNU towers that I will take up the PGP replacement implementation I spent the rest of the year replacing IDEA by Blowfish, RSA by Elgamal, implementing streaming encryption, adding some key management and getting the code into a reasonable shape. There used to be a plan for a free version of Secure Shell called PSST (later known as LSH) with a somewhat populated mailing lists maintained by Martin Hamilton. Martin was the so kind to setup a mailing list for g10 too and announced it on that list. This way we got the first subscribers. Eventually I made the first tarball, put it up to ftp.guug.de, the FTP server of the German Unix User Group, and wrote an announcement [5]. Right the next day Peter Gutmann offered to allow the use of his random number code for systems without a /dev/random. This eventually helped a lot to make GnuPG portable to many platforms. The next two months were filled with code updates and a lengthly discussion on the name; we finally settled for Anand Kumria's suggestion of GnuPG and made the first release under this name (gnupg-0.2.8) on Feb 24 [6]. Just a few days later an experimental version with support for Windows was released. (That release also fixed an alignment problem on Alpha boxes which was detected due to kernel log files filling up the hard disk and an admin asking whether they really need to be backed up. ;-) In July 1998 the first more or less OpenPGP draft compliant version was released. Matthew Skala had contributed Twofish code done cleanly From scratch (Twofish was at that time a promising AES candidate and suggested by Schneier as a Blowfish replacement; however we had some copyright concerns with the reference code). Michael Roth contributed a Triple-DES implementation later the year and thus completed the required set of OpenPGP algorithms. Over the next year the usual problems were solved, features discussed, complaints noticed and support for gpg in various other software was introduced by their respective authors. Finally, on September 7, 1999 the current code was released as version 1.0.0 with the major update of including Mike Ashley's GNU Privacy Handbook [7]. A year later the RSA patent was to expire on September 20; the patent holder placed the patent into the public domain 3 weeks earlier and thus we could release 1.0.3 with RSA support already on September 18. One of the major obstacles on widespread use public cryptography had gone (far too late of course). Also in 1999 the German government decided that strong encryption will not be regulated in any way and that its use is recommended for everyone. To publicly support this statement the Ministry of Economics funded the porting of GnuPG and related software to Microsoft Windows [8]. The US government was not keen to see that and tried to urge the German government to revise the decision to allow unregulated distribution of crypto software [9]. That did not work out and to the end the USA had no other way than to weaken their own export rules. Although we still develop GnuPG using servers located in Europe the new US export controls eventually allowed US hackers to contribute to GnuPG development. In 2001 David Shaw joined the project and since then he is one of the most active GnuPG hackers and the co-maintainer. It's now a long time since GnuPG could be managed as a fun project and thus I now spend most of my professional life maintaining and extending GnuPG. In 2001 I founded g10 Code, a Free Software company for the development and support of GnuPG and related software. The most known project is probably GnuPG-2 which started under the name NewPG as part of the broader Aegypten project. The main goal of Aegypten was to provide support for S/MIME under GNU/Linux and integrate that cleanly with other mail clients, most notably KMail. Although having been actively used since 2004, we released 2.0.0 only one years ago. It was not that much fun writing X.509/CMS (commonly named S/MIME) software compared to the elegant and very interoperable OpenPGP protocol. Having mastered that we meanwhile achieved to provide a software which is really useful and works nicely with almost any other S/MIME implementation. It also turned out that we could port GnuPG-2 to Windows - despite my original claim that a modern POSIX platform will be needed for GnuPG-2. This development also showed that it is viable to develop Free Software as a business. With the new tools and from a user's perspective S/MIME and OpenPGP will soon not make much of a difference anymore. However I had to smile when I today read a report on the last RSA Europe conference where a quick poll during a talk showed that OpenPGP is the mostly used encryption protocol. Recall that GnuPG is just one tool; there are numerous other tools out to solve related privacy problems. Kudos to all who worked on writing and deploying privacy tools over all these years! Happy Hacking, Werner [0] http://www/gnupg.org [1] ftp://ftp.gnupg.org/gcrypt/historic/g10-0.0.0.tar.gz [2] from pgpdoc2.txt: "Finally, if you want to turn PGP into a commercial product and make money selling it, then we must agree on a way for me to also make money on it. [...] Under no circumstances may PGP be distributed without the PGP documentation, including this PGP User's Guide." [3] "valid" is meant in the sense the patent holders use it and does not imply that I regard patents on software a valid concept. See http://www.fsfeurope.org/projects/swpat/background.en.html . [4] http://www.dascon.de/IN-BT97/programm.html [5] http://lists.gnupg.org/pipermail/gnupg-devel/1997-December/014131.html There are just a few mails in December mainly discussing patent things. [6] http://lists.gnupg.org/pipermail/gnupg-devel/1998-February/014208.html [7] http://lists.gnupg.org/pipermail/gnupg-announce/1999q3/000037.html [8] http://partners.nytimes.com/library/tech/99/11/cyber/articles/19encrypt.html [9] http://www.heise.de/tp/r4/artikel/5/5124/1.html -- Die Gedanken sind frei. Auschnahme regelt ein Bundeschgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : /pipermail/attachments/20071220/00458bad/attachment.pgp