From wk at gnupg.org Thu Sep 16 12:27:33 2021 From: wk at gnupg.org (Werner Koch) Date: Thu, 16 Sep 2021 12:27:33 +0200 Subject: [Announce] GnuPG 2.2.31 (LTS) released Message-ID: <877dfgerxm.fsf@wheatstone.g10code.de> Hello! We are pleased to announce the availability of a new GnuPG LTS release: version 2.2.31. This release fixes a few minor bugs and a regression in the last release. The LTS (long term support) series of GnuPG is guaranteed to be maintained at least until the end of 2024. See https://gnupg.org/download/index.html#end-of-life 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.31 (2021-09-15) ================================================= * agent: Fix a regression in GET_PASSPHRASE. [#5577] * scd: Fix an assertion failure in close_pcsc_reader. [67e1834ad4] * scd: Add support for PC/SC in "GETINFO reader_list". Release-info: https://dev.gnupg.org/T5571 Getting the Software ==================== Please follow the instructions found at or read on: GnuPG 2.2.31 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.31.tar.bz2 (7043k) https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.2.31.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.31_20210915.exe (4395k) https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.2.31_202109.exe.sig The source used to build the Windows installer can be found in the same directory with a ".tar.xz" suffix. A new version of Gpg4win will probably not be published. Users affected by one of the fixed bugs may instead install this version on top of Gpg4win 3.1.16. 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.31.tar.bz2 you would use this command: gpg --verify gnupg-2.2.31.tar.bz2.sig gnupg-2.2.31.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.31.tar.bz2, you run the command like this: sha1sum gnupg-2.2.31.tar.bz2 and check that the output matches the next line: 18104b919caf14d1ef17635262418f382f888d53 gnupg-2.2.31.tar.bz2 e387330c49855bd5a04387b3c9a51abfdafa5e64 gnupg-w32-2.2.31_20210915.tar.xz abc56b365c4e9a93d0b55de72b631b1615b66628 gnupg-w32-2.2.31_20210915.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 ========================= 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/T5571 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. Three 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. 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 keys: rsa3072 2017-03-17 [expires: 2027-03-15] 5B80 C575 4298 F0CB 55D8 ED6A BCEF 7E29 4B09 2E28 Andre Heinecke (Release Signing Key) ed25519 2020-08-24 [expires: 2030-06-30] 6DAA 6E64 A76D 2840 571B 4902 5288 97B8 2640 3ADA Werner Koch (dist signing 2020) ed25519 2021-05-19 [expires: 2027-04-04] AC8E 115B F73E 2D8D 47FA 9908 E98E 9B2D 19C6 C8BD Niibe Yutaka (GnuPG Release Key) 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. -- Please read Nils Melzer: Der Fall Julian Assange It is really important to know the background of the Assange case to understand the massive perils to free journalism. The book is right now only available in German: https://dev.gnupg.org/u/melzerassang -------------- 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 andrewg at andrewg.com Fri Sep 24 01:00:04 2021 From: andrewg at andrewg.com (Andrew Gallagher) Date: Fri, 24 Sep 2021 00:00:04 +0100 Subject: Update keys.gnupg.net? Re: [Announce] GnuPG 2.2.29 (LTS) released In-Reply-To: References: <87tulaaxu5.fsf@wheatstone.g10code.de> <202107131015.24257.bernhard@intevation.de> <6559495.4FfYX22H5t@daneel> Message-ID: <333721ea-fd8f-b5a3-f271-c276784c0647@andrewg.com> On 13/07/2021 21:09, Phil Pennock via Gnupg-devel wrote: > In case it helps: a decade ago, I wrote an SKS spider for building a > graph of all the available servers, after a while, I rewrote from Python > to Go, and that can be found at > ; it was a weekend rewrite > and is not clean Go and is not a good example of the language, but if > anyone wants a basis for getting started with building a graph for > publishing DNS records, this one works. I have updated Phil's code to support Hockeypuck servers, and it is now running at https://spider.pgpkeys.eu . This is NOT a pool, and it will not become one for reasons explained at length elsewhere. I do intend to keep it available on a best-effort basis for anyone interested in monitoring the health of the remaining keyserver network. It also hosts pretty graphs at https://spider.pgpkeys.eu/graphs made using Gunnar's code from https://sks-status.gwolf.org - unfortunately these are not clickable but you can't have everything... Enjoy. :-) -- Andrew Gallagher -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From bernhard at intevation.de Fri Sep 24 12:27:48 2021 From: bernhard at intevation.de (Bernhard Reiter) Date: Fri, 24 Sep 2021 12:27:48 +0200 Subject: Keyserver: List of available ones (dynamic) In-Reply-To: <333721ea-fd8f-b5a3-f271-c276784c0647@andrewg.com> References: <87tulaaxu5.fsf@wheatstone.g10code.de> <333721ea-fd8f-b5a3-f271-c276784c0647@andrewg.com> Message-ID: <202109241227.54884.bernhard@intevation.de> Am Freitag 24 September 2021 01:00:04 schrieb Andrew Gallagher via Gnupg-devel: > > https://github.com/philpennock/sks_spider > I have updated Phil's code to support Hockeypuck servers, and it is now > running at https://spider.pgpkeys.eu . Very cool! Did you make your code available? > It also hosts pretty graphs at https://spider.pgpkeys.eu/graphs In the graphs I can see keyserver.ubuntu.com, but in the list I cannot. Why is that? Regards, Bernhard -- www.intevation.de/~bernhard ? +49 541 33 508 3-3 Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998 Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: This is a digitally signed message part. URL: From bernhard at intevation.de Fri Sep 24 12:41:32 2021 From: bernhard at intevation.de (Bernhard Reiter) Date: Fri, 24 Sep 2021 12:41:32 +0200 Subject: WKD hashing choice z-base-32 In-Reply-To: <20210802134703.TlVIZ%steffen@sdaoden.eu> References: <20210728150419.DEIXG%steffen@sdaoden.eu> <87v94p5zhk.fsf@wheatstone.g10code.de> <20210802134703.TlVIZ%steffen@sdaoden.eu> Message-ID: <202109241241.38711.bernhard@intevation.de> == WKD protocol Am Montag 02 August 2021 15:47:03 schrieb Steffen Nurpmeso: > Yes, no, my problem is about the the special z-base-32 step, for > which there is no tool around by default. https://wiki.gnupg.org/EasyGpg2016/PubkeyDistributionConcept?highlight=%28z-base-32%29 documents the reasons for some design decisions, it says: | The reason for using this encoding instead of a standard hex encoding is to | visually distinguish such an item from a fingerprint. Furthermore, in | contrast to Base-64 and other Base-32 encodings, z-Base-32 has been | optimized for easier human use. So it is _not_ a fingerprint. :) And the hashing and encoding is done to get an equal length string without funny characters so it can easily be put as files in a directory tree. == ssh > But i personally still > struggle with the base64 that SSH now uses for fingerprinting For manual visual comparison, using -o VisualHostKey=yes works for me in many situations. Bernhard -- www.intevation.de/~bernhard ? +49 541 33 508 3-3 Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998 Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: This is a digitally signed message part. URL: From andrewg at andrewg.com Fri Sep 24 13:49:18 2021 From: andrewg at andrewg.com (Andrew Gallagher) Date: Fri, 24 Sep 2021 12:49:18 +0100 Subject: Keyserver: List of available ones (dynamic) In-Reply-To: <202109241227.54884.bernhard@intevation.de> References: <87tulaaxu5.fsf@wheatstone.g10code.de> <333721ea-fd8f-b5a3-f271-c276784c0647@andrewg.com> <202109241227.54884.bernhard@intevation.de> Message-ID: <07af606d-9eda-83b1-db56-5b29feda34c1@andrewg.com> On 24/09/2021 11:27, Bernhard Reiter wrote: > Am Freitag 24 September 2021 01:00:04 schrieb Andrew Gallagher via > Gnupg-devel: >>> https://github.com/philpennock/sks_spider >> I have updated Phil's code to support Hockeypuck servers, and it is now >> running at https://spider.pgpkeys.eu . > > Very cool! > > Did you make your code available? Ref this PR: https://github.com/philpennock/sks_spider/pull/8 >> It also hosts pretty graphs at https://spider.pgpkeys.eu/graphs > > In the graphs I can see keyserver.ubuntu.com, but in the list > I cannot. Why is that? Well spotted. :-) The graph code (written in Ruby) polls both port 80 and port 11371, while the list code (written in Go) only polls 11371. Furthermore, keyserver.ubuntu.com is not referenced directly by any peer, but keyserver.syseleven.de is -- it runs a proxy on port 80 (only) that forwards requests to keyserver.ubuntu.com. This means that the Ruby spider can find keyserver.ubuntu.com by traversing syseleven port 80, but the Go spider can't. Note that the Ruby code records every peer reference no matter what the error, whereas the Go code records only HTTP errors, and silently ignores connection failures. The Go code performs URL deduplication by detecting the hostname that the target server returns. The Ruby code doesn't; instead I bodged it by hard-coding a list of duplicates by hand (unresponsive servers don't return hostnames). In any case, keyserver.ubuntu.com is not syncing because it has no mutual peers. -- Andrew Gallagher -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From bernhard at intevation.de Tue Sep 28 17:32:09 2021 From: bernhard at intevation.de (Bernhard Reiter) Date: Tue, 28 Sep 2021 17:32:09 +0200 Subject: IncreaseWKDUsage2021 bachelor thesis Message-ID: <202109281732.15021.bernhard@intevation.de> Hello All, within the next months Christoph Klassen in CC will do his bachelor thesis at Intevation about how to increase the usage of WKD. The precise subject and focus is still to be determined. Currently the idea is to see if the current instructions and existing implementations in code are good enough to implement this in another email client. Or see what is missing in existing email clients that could be implemented or documentated. Ideally we get some code and documentation, helping more users to use WKD and OpenPGP. The current place for this little project is https://wiki.gnupg.org/WKD/Misc (We are still setting things up.) Christoph is subscribed to this mailing list. So feel free to give feedback to him or us directly or discuss things here on the list. Best Regards, Bernhard -- www.intevation.de/~bernhard ? +49 541 33 508 3-3 Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998 Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: This is a digitally signed message part. URL: