From wk at gnupg.org Tue Dec 1 10:03:41 2020 From: wk at gnupg.org (Werner Koch) Date: Tue, 01 Dec 2020 10:03:41 +0100 Subject: [PATCH GnuPG] doc: Add parameters for batch generation of ECC keys. In-Reply-To: <71f73cd1-8cf1-891b-d116-edff2e9fbd5e@b1-systems.de> ("Jens \=\?utf-8\?Q\?Mei\=C3\=9Fner\=22's\?\= message of "Sun, 22 Nov 2020 14:42:34 +0100") References: <71f73cd1-8cf1-891b-d116-edff2e9fbd5e@b1-systems.de> Message-ID: <87mtyxdhjm.fsf@wheatstone.g10code.de> On Sun, 22 Nov 2020 14:42, Jens Mei?ner said: > * doc/gpg.texi: Add parameters for batch generation of ECC keys. Thanks. Applied to master and 2.2. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From wk at gnupg.org Mon Dec 21 19:26:37 2020 From: wk at gnupg.org (Werner Koch) Date: Mon, 21 Dec 2020 19:26:37 +0100 Subject: [Announce] GnuPG 2.2.26 released Message-ID: <87mty7vwv6.fsf@wheatstone.g10code.de> Hello! We are pleased to announce the availability of a new GnuPG release: version 2.2.26. This is a maintenance release improving support for LDAP keyservers and enterprise use. What is GnuPG ============= The GNU Privacy Guard (GnuPG, GPG) is a complete and free implementation of the OpenPGP and S/MIME standards. GnuPG allows to encrypt and sign data and communication, features a versatile key management system as well as access modules for public key directories. GnuPG itself is a command line tool with features for easy integration with other applications. The separate library GPGME provides a uniform API to use the GnuPG engine by software written in common programming languages. A wealth of frontend applications and libraries making use of GnuPG are available. As an universal crypto engine GnuPG provides support for S/MIME and Secure Shell in addition to OpenPGP. GnuPG is Free Software (meaning that it respects your freedom). It can be freely used, modified and distributed under the terms of the GNU General Public License. Noteworthy changes in version 2.2.26 ==================================== * gpg: New AKL method "ntds". * gpg: Fix --trusted-key with fingerprint arg. * scd: Fix writing of ECC keys to an OpenPGP card. [#5163] * scd: Make an USB error fix specific to SPR532 readers. [#5167] * dirmngr: With new LDAP keyservers store the new attributes. Never store the useless pgpSignerID. Fix a long standing bug storing some keys on an ldap server. * dirmngr: Support the new Active Direcory LDAP schema for keyservers. * dirmngr: Allow LDAP OpenPGP searches via fingerprint. * dirmngr: Do not block other threads during keyserver LDAP calls. * Support global configuration files. [#4788] * Fix the iconv fallback handling to UTF-8. [#5038] Release-info: https://dev.gnupg.org/T5153 Getting the Software ==================== Please follow the instructions found at or read on: GnuPG 2.2.26 may be downloaded from one of the GnuPG mirror sites or direct from its primary FTP server. The list of mirrors can be found at . Note that GnuPG is not available at ftp.gnu.org. The GnuPG source code compressed using BZIP2 and its OpenPGP signature are available here: https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.2.26.tar.bz2 (7020k) https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.2.26.tar.bz2.sig An installer for Windows without any graphical frontend except for a very minimal Pinentry tool is available here: https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.2.26_20201221.exe (4249k) https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.2.26_20201221.exe.sig The source used to build the Windows installer can be found in the same directory with a ".tar.xz" suffix. New versions of the GnuPG VS-Desktop(tm) and Gpg4win featuring this version of GnuPG will be released shortly. 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 version of GnuPG installed, you can simply verify the supplied signature. For example to verify the signature of the file gnupg-2.2.26.tar.bz2 you would use this command: gpg --verify gnupg-2.2.26.tar.bz2.sig gnupg-2.2.26.tar.bz2 This checks whether the signature file matches the source file. You should see a message indicating that the signature is good and made by one or more of the release signing keys. Make sure that this is a valid key, either by matching the shown fingerprint against a trustworthy list of valid release signing keys or by checking that the key has been signed by trustworthy other keys. See the end of this mail for information on the signing keys. * If you are not able to use an existing version of GnuPG, you have to verify the SHA-1 checksum. On Unix systems the command to do this is either "sha1sum" or "shasum". Assuming you downloaded the file gnupg-2.2.26.tar.bz2, you run the command like this: sha1sum gnupg-2.2.26.tar.bz2 and check that the output matches the next line: 11ffe2ee80d594c3e83f123b9e189b630c0fe19d gnupg-2.2.26.tar.bz2 0ae3080532b53fe4fd5c05ae6efd1d05bb28365f gnupg-w32-2.2.26_20201221.tar.xz 6829e6250efedd8de09628104a9e15f5943b65c8 gnupg-w32-2.2.26_20201221.exe Internationalization ==================== This version of GnuPG has support for 26 languages with Chinese (traditional and simplified), Czech, French, German, Italian, Japanese, Norwegian, Polish, Russian, and Ukrainian being almost completely translated. Documentation and Support ========================= If you used GnuPG in the past you should read the description of changes and new features at doc/whats-new-in-2.1.txt or online at https://gnupg.org/faq/whats-new-in-2.1.html The file gnupg.info has the complete reference manual of the system. Separate man pages are included as well but they miss some of the details available only in thee manual. The manual is also available online at https://gnupg.org/documentation/manuals/gnupg/ or can be downloaded as PDF at https://gnupg.org/documentation/manuals/gnupg.pdf . You may also want to search the GnuPG mailing list archives or ask on the gnupg-users mailing list for advise on how to solve problems. Most of the new features are around for several years and thus enough public experience is available. https://wiki.gnupg.org has user contributed information around GnuPG and relate software. In case of build problems specific to this release please first check https://dev.gnupg.org/T5153 for updated information. Please consult the archive of the gnupg-users mailing list before reporting a bug: https://gnupg.org/documentation/mailing-lists.html. We suggest to send bug reports for a new release to this list in favor of filing a bug at https://bugs.gnupg.org. If you need commercial support go to https://gnupg.com or https://gnupg.org/service.html. If you are a developer and you need a certain feature for your project, please do not hesitate to bring it to the gnupg-devel mailing list for discussion. Thanks ====== Since 2001 maintenance and development of GnuPG is done by g10 Code GmbH and still mostly financed by donations. Two full-time employed developers as well as two contractors exclusively work on GnuPG and closely related software like Libgcrypt, GPGME and Gpg4win. We like to thank all the nice people who are helping the GnuPG project, be it testing, coding, translating, suggesting, auditing, administering the servers, spreading the word, or answering questions on the mailing lists. Many thanks to our numerous financial supporters, both corporate and individuals. Without you it would not be possible to keep GnuPG in a good and secure shape and to address all the small and larger requests made by our users. Thanks. Happy hacking, Your GnuPG hackers p.s. This is an announcement only mailing list. Please send replies only to the gnupg-users'at'gnupg.org mailing list. p.p.s List of Release Signing Keys: To guarantee that a downloaded GnuPG version has not been tampered by malicious entities we provide signature files for all tarballs and binary versions. The keys are also signed by the long term keys of their respective owners. Current releases are signed by one or more of these four keys: ed25519 2020-08-24 [expires: 2030-06-30] Key fingerprint = 6DAA 6E64 A76D 2840 571B 4902 5288 97B8 2640 3ADA Werner Koch (dist signing 2020) rsa2048 2014-10-29 [expires: 2020-10-30] Key fingerprint = 031E C253 6E58 0D8E A286 A9F2 2071 B08A 33BD 3F06 NIIBE Yutaka (GnuPG Release Key) rsa3072 2017-03-17 [expires: 2027-03-15] Key fingerprint = 5B80 C575 4298 F0CB 55D8 ED6A BCEF 7E29 4B09 2E28 Andre Heinecke (Release Signing Key) rsa2048 2011-01-12 [expires: 2021-12-31] Key fingerprint = D869 2123 C406 5DEA 5E0F 3AB5 249B 39D2 4F25 E3B6 Werner Koch (dist sig) The keys are available at https://gnupg.org/signature_key.html and in any recently released GnuPG tarball in the file g10/distsigkey.gpg . Note that this mail has been signed by a different key. -- "If privacy is outlawed, only outlaws will have privacy." - PRZ 1991 ... even the EU still does not get it. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 227 bytes Desc: not available URL: -------------- next part -------------- _______________________________________________ Gnupg-announce mailing list Gnupg-announce at gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-announce From kloecker at kde.org Wed Dec 30 19:50:15 2020 From: kloecker at kde.org (Ingo =?ISO-8859-1?Q?Kl=F6cker?=) Date: Wed, 30 Dec 2020 19:50:15 +0100 Subject: Missing const in Signature::operator< In-Reply-To: <2843969.slGk94SIus@beastie.bionicmutton.org> References: <2843969.slGk94SIus@beastie.bionicmutton.org> Message-ID: <5677373.lOV4Wx5bFT@collossus.localdomain> On Mittwoch, 30. Dezember 2020 14:56:45 CET Adriaan de Groot wrote: > [ BCC'ed to Ingo (maintainer) and Jason (FreeBSD maintainer) ] [ Not BCC'ed Jason because I don't know the email address. ] > In 6a6d2a27648, Signature got an operator<, so that Signatures can be > sorted. This is used in libkleo, for instance, to sort the signatures for > display. > > + bool operator<(const Signature &other); > > That should be const, though? Yeah, should've been const. > I have bunged in a const in the obvious spot, a patch is at https:// > invent.kde.org/-/snippets/1437 . I have test-built libkleo against a gpgmepp > patched this way on FreeBSD, and this compile failure is then repaired. Unfortunately, making a member function const is not BC. I'll add a const overload instead. Regards, Ingo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 228 bytes Desc: This is a digitally signed message part. URL: