From wk at gnupg.org Mon Oct 17 09:43:56 2022 From: wk at gnupg.org (Werner Koch) Date: Mon, 17 Oct 2022 09:43:56 +0200 Subject: [Announce] [CVE-2022-3515] GnuPG / Libksba Security Advisory Message-ID: <87v8oievyb.fsf@wheatstone.g10code.de> __________________________________________________ SECURITY ADVISORY FOR LIBKSBA/GNUPG (CVE-2022-3515) g10 Code GmbH __________________________________________________ 2022-10-17 Integer Overflow in LibKSBA / GnuPG =================================== A severe bug has been found in [Libksba] , the library used by GnuPG for parsing the ASN.1 structures as used by S/MIME. The bug affects all versions of [Libksba] before 1.6.2 and may be used for remote code execution. *Updating this library is thus important*. Who is affected ~~~~~~~~~~~~~~~ The major user of Libksba is /gpgsm/, the S/MIME cousin of /gpg/. There it is used to parse all kind of input data, in particular signed or encrypted data in files or in mails. Feeding a user with malicious data can thus be easily achieved. A second user of Libksba is /dirmngr/, which is responsible for loading and parsing Certificate Revocation Lists (CRLs) and for verifying certificates used by TLS (i.e. https connections). Mounting an attack is a bit more complex but can anyway be easily done using a rogue web server to serve a Web Key Directory, certificates, or CRLs. An exploit is not yet publicly known but very straightforward to create for experienced crooks. Affected to our knowledge are: - Most software using /Libksba/ versions up to 1.6.1 - All /Gpg4win/ versions from version 2.0.0 up to 4.0.3 - All /GnuPG VS-Desktop/ versions from 3.1.16 up to 3.1.24 - All /GnuPG installers for Windows/ from version 2.3.0 up to 2.3.7 - All /GnuPG LTS installers for Windows/ from version 2.1.0 up to 2.2.39 How to fix ~~~~~~~~~~ If you are on a Unix or Linux system you should get the latest version of Libksba (1.6.2 or newer), build the software and install the new shared library. Restart any background processes (e.g. `gpgconf --kill all' for GnuPG). In the rare case that Libksba is statically linked remember to rebuild those binaries. If your are on Windows or if you use an AppImage of GnuPG VS-Desktop update to the latest version: - Gpgwin version 4.0.4 or newer - GnuPG VS-Desktop version 3.1.25 or newer (MSI or AppImage) - GnuPG installer for Windows version 2.3.8 - GnuPG LTS installer for Windows version 2.2.40 In case you are not yet ready to deploy a new version, please extract `libksba-8.dll' from the respective package and replace the original one by this one. This is sufficient to fix the security issue. See https://gnupg.org/download for links to the latest packages. For Gpg4win see https://gpg4win.org How to check whether GnuPG has been fixed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ GnuPG is the most prominent user of Libksba and it is not immediately visible whether a fixed version of Libksba is used. To check this run: ,---- | gpgconf --show-versions `---- and watch out for a line like ,---- | * KSBA 1.6.2 (xxxxx) `---- If you see a version number of 1.6.2 or newer, you got the fix. CVE ~~~ GnuPG-bug-id: 6230 (https://dev.gnupg.org/T6230) CVE ........: CVE-2022-3515 CVSS .......: 8.1: AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H Other-IDs ..: ZDI-CAN-18927, ZDI-CAN-18928, ZDI-CAN-18927 CVSS taken from the Trend Micro Zero Day Initiative report. Technical background ==================== The task of Libksba is to parse and build ASN.1 objects as used by S/MIME, X.509, and CMS. The used encoding (BER, DER) is based on tag-length-value objects. The function /_ksba_ber_read_tl/ parses such data and returns the tag and associated information in this structure: ,---- | struct tag_info { | enum tag_class class; | int is_constructed; | unsigned long tag; | unsigned long length; /* Length part of the TLV */ | int ndef; /* It is an indefinite length */ | size_t nhdr; /* Number of bytes in the TL */ | unsigned char buf[10]; /* Buffer for the TL */ | const char *err_string; | int non_der; | }; `---- At several places we need to copy the objects to a local buffer. For example we copy OIDs to a statically encoded buffer for further processing: ,---- | struct tag_info ti; | unsigned char tmpbuf[500]; /* for OID or algorithmIdentifier */ | [...] | if (ti.nhdr + ti.length >= DIM(tmpbuf)) | return gpg_error (GPG_ERR_TOO_LARGE); | memcpy (tmpbuf, ti.buf, ti.nhdr); | err = read_buffer (crl->reader, tmpbuf+ti.nhdr, ti.length); `---- It is obvious that the sum of the header length (although less than 10 bytes) and the announced length of the value can easily wrap around and pass the check. The result is then an overflow of /tmpbuf/ with all the usual consequences. The code has been there for ages and it seems that the audits missed this because, well, there is some overflow check and a too brief check may have only noticed that the memcpy if fine. The fix for this is easy because we can check for an overflow right away in the parser. Thus /_ksba_ber_read_tl/ finally does this extra check: ,---- | if (ti->length > ti->nhdr && (ti->nhdr + ti->length) < ti->length) | { | ti->err_string = "header+length would overflow"; | return gpg_error (GPG_ERR_EOVERFLOW); | } `---- Thanks ~~~~~~ This vulnerability was discovered by: Anonymous working with Trend Micro Zero Day Initiative The report was received on 2022-10-04, fix pushed 2022-10-05, new source code release 2002-10-07, binary releases and announcement on 2022-10-17. [Libksba] https://gnupg.org/software/libksba/ -- The pioneers of a warless world are the youth that refuse military service. - A. Einstein -------------- 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 Oct 17 14:58:22 2022 From: wk at gnupg.org (Werner Koch) Date: Mon, 17 Oct 2022 14:58:22 +0200 Subject: [Announce] GnuPG 2.3.8 released Message-ID: <87h702ehe9.fsf@wheatstone.g10code.de> Hello! We are pleased to announce the availability of a new stable GnuPG release: version 2.3.8. This release comes with a lot of new features and the binary releases come with the fix for the Libksba vulnerability CVE-2022-3515 (https://gnupg.org/blog/20221017-pepe-left-the-ksba.html). 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. Three different series of GnuPG are actively maintained: - Version 2.3 is the current stable version with a lot of new features compared to 2.2. This announcement is about the latest release of this series. - Version 2.2 is our LTS (long term support) version and guaranteed to be maintained at least until the end of 2024. Only a small subset of features from 2.3 has been back-ported to this series. See https://gnupg.org/download/index.html#end-of-life - Version 1.4 is only maintained to allow decryption of very old data which is, for security reasons, not anymore possible with other GnuPG versions. Noteworthy changes in version 2.3.8 =================================== * gpg: Do not consider unknown public keys as non-compliant while decrypting. [T6205] * gpg: Avoid to emit a compliance mode line if Libgcrypt is non-compliant. [T6221] * gpg: Improve --edit-key setpref command to ease c+p. [rG1908fa8b83] * gpg: Emit an ERROR status if --quick-set-primary-uid fails and allow to pass the user ID by hash. [T6126] * gpg: Actually show symmetric+pubkey encrypted data as de-vs compliant. Add extra compliance checks for symkey_enc packets. [T6119] * gpg: In de-vs mode use SHA-256 instead of SHA-1 as implicit preference. [T6043] * gpgsm: Fix reporting of bad passphrase error during PKCS#11 import. [T5713,T6037] * agent: Fix a regression in "READKEY --format=ssh". [T6012] * agent: New option --need-attr for KEYINFO. [rG989eae648c] * agent: New attribute "Remote-list" for use by KEYINFO. [r1383aa4750] * scd: Fix problem with Yubikey 5.4 firmware. [T6070] * dirmngr: Fix CRL Distribution Point fallback to other schemes. [rG0c8299e2b5] * dirmngr: New LDAP server flag "areconly" (A-record-only). [rGd65a0335e5] * dirmngr: Fix upload of multiple keys for an LDAP server specified using the colon format. [rG536b5cd663] * dirmngr: Use LDAP schema v2 when a Base DN is specified. [T6047] * dirmngr: Avoid caching expired certificates. [T6142] * wkd: Fix path traversal attack in gpg-wks-server. Add the mail address to the pending request data. [rG8a63a8c825,T6098] * wkd: New command --mirror for gpg-wks-client. [T6224] * gpg-auth: New tool for authentication. [T5862] * New common.conf option no-autostart. [rG203dcc19eb] * Silence warnings from AllowSetForegroundWindow unless GNUPG_EXEC_DEBUG_FLAGS is used. [rG4ef8516a79] Release-info: https://dev.gnupg.org/T6106 Getting the Software ==================== Please follow the instructions found at or read on: GnuPG 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.3.8.tar.bz2 (7465k) https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.3.8.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.3.8_20221013.exe (4797k) https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.3.8_20221013.exe.sig The source used to build the Windows installer can be found in the same directory with a ".tar.xz" suffix. A new release of Gpg4win (version 4.0.4) including this version of GnuPG is available at https://gpg4win.org We will shortly announce a Linux AppImage of this version featuring Kleopatra as graphical user interface. 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.3.8.tar.bz2 you would use this command: gpg --verify gnupg-2.3.8.tar.bz2.sig gnupg-2.3.8.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.3.8.tar.bz2, you run the command like this: sha1sum gnupg-2.3.8.tar.bz2 and check that the output matches the next line: 1f31b7b4c9c9adad97f94ea3acf1aa64c0424bcc gnupg-2.3.8.tar.bz2 014aa20eb1ac677736d0c2e056adc55304e12679 gnupg-w32-2.3.8_20221013.tar.xz 6cfabadbaf15a27988a11e811e9eabb20077b4ff gnupg-w32-2.3.8_20221013.exe Internationalization ==================== This version of GnuPG has support for 26 languages with Chinese (traditional and simplified), Czech, French, German, Italian, Japanese, Norwegian, Polish, Russian, Turkish, 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 the 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/T6106 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 has mostly been 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. Fortunately, and this is still not common with free software, we have now established a way of financing the development while keeping all our software free and freely available for everyone. Our model is similar to the way RedHat manages RHEL and Fedora: Except for the actual binary of the MSI installer for Windows and client specific configuration files, all the software is available under the GNU GPL and other Open Source licenses. Thus customers may even build and distribute their own version of the software as long as they do not use our trademark GnuPG VS-Desktop?. 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, answering questions on the mailing lists, or helping with donations. *Thank you all* 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 four 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) brainpoolP256r1 2021-10-15 [expires: 2029-12-31] 02F3 8DFF 731F F97C B039 A1DA 549E 695E 905B A208 GnuPG.com (Release Signing Key 2021) 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. -- The pioneers of a warless world are the youth that refuse military service. - A. Einstein -------------- 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 Tue Dec 20 10:46:59 2022 From: wk at gnupg.org (Werner Koch) Date: Tue, 20 Dec 2022 10:46:59 +0100 Subject: [Announce] GnuPG 2.4.0 released (silver anniversary) Message-ID: <87sfhao19o.fsf@wheatstone.g10code.de> Hello! Exactly 25 years ago the very first release of GnuPG was published. We are pleased to take this opportunity to announce the availability of a new stable GnuPG release: version 2.4.0. This release has a few new features and the binary releases come with an updated Libksba to fix another vulnerability related to CVE-2022-3515. 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. Three different series of GnuPG are actively maintained: - Version 2.4 is the current stable version with a lot of new features compared to 2.2. This announcement is about the latest release of this series; the previous release was 2.3.8. - Version 2.2 is our LTS (long term support) version and guaranteed to be maintained at least until the end of 2024. Only a small subset of features from 2.4 has been back-ported to this series. See https://gnupg.org/download/index.html#end-of-life - Version 1.4 is only maintained to allow decryption of very old data which is, for security reasons, not anymore possible with other GnuPG versions. Please use 1.4 only for this purpose. Noteworthy changes in version 2.4.0 =================================== * The key database daemon is now a fully supported feature. Keys are stored in a SQLite database to make key lookups much faster. Enable it by adding "use-keyboxd" o common.conf. See also the README file. * gpg: New command --quick-update-pref. [rGd40d23b233] * gpg: New list-options show-pref and show-pref-verbose. [rG811cfa34cb] * gpg: New option --list-filter to restrict key listings like gpg -k --list-filter 'select=revoked-f && sub/algostr=ed25519' [rG1324dc3490] * gpg: New --export-filter export-revocs. [rGc985b52e71] * gpg: Also import stray revocation certificates. [rG7aaedfb107] * gpg: Add a notation to encryption subkeys in de-vs mode. [T6279] * gpg: Improve signature verification speed by a factor of more than four. Double detached signing speed. [T5826] * gpg: Allow only OCB for AEAD encryption. [rG5a2cef801d] * gpg: Fix trusted introducer for mbox only user-ids. [T6238] * gpg: Report an error via status-fd for receiving a key from the agent. [T5151] * gpg: Make --require-compliance work without the --status-fd option. [rG2aacd843ad] * gpg: Fix verification of cleartext signatures with overlong lines. [T6272] * agent: Fix import of protected OpenPGP v5 keys. [T6294] * gpgsm: Change the default cipher algorithm from AES128 to AES256. Also announce support for this in signatures. [rG2d8ac55d26] * gpgsm: Always use the chain validation model if the root-CA requests this. [rG7fa1d3cc82] * gpgsm: Print OCSP revocation date and reason in cert listings. [rGb6abaed2b5] * agent: Support Win32-OpenSSH emulation by gpg-agent. [T3883] * scd: Support the Telesec Signature Card v2.0. [T6252] * scd: Redact --debug cardio output of a VERIFY APDU. [T5085] * scd: Skip deleted pkcs#15 records in CARDOS 5. [rG061efac03f] * dirmngr: Fix build with no LDAP support. [T6239] * dirmngr: Fix verification of ECDSA signed CRLs. [rG868dabb402] * wkd: New option --add-revocs for gpg-wks-client. [rGc3f9f2d497] * wkd: Ignore expired user-ids in gpg-wks-client. [T6292] * card: New commands "gpg" and "gpgsm". [rG9c4691c73e] Release-info: https://dev.gnupg.org/T6303 Getting the Software ==================== Please follow the instructions found at or read on: GnuPG 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.4.0.tar.bz2 (7487k) https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.4.0.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.4.0_20221216.exe (4816k) https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.4.0_20221216.exe.sig The source used to build this Windows installer can be found in the same directory with a ".tar.xz" suffix. A link to GnuPG Desktop?, an AppImage for Linux, featuring this version of GnuPG along with the advanced graphical user interface Kleopatra is available from the download page: https://gnupg.org/download/index.html#binary A new release of Gpg4win (version 4.1.0) including this version of GnuPG is available at https://gpg4win.org 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.4.0.tar.bz2 you would use this command: gpg --verify gnupg-2.4.0.tar.bz2.sig gnupg-2.4.0.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.4.0.tar.bz2, you run the command like this: sha1sum gnupg-2.4.0.tar.bz2 and check that the output matches the next line: 63dde155a8df0d5e1987efa5fc17438beca83ac1 gnupg-2.4.0.tar.bz2 f8b5aaf759fa311e60d34823be342d7e15d1e752 gnupg-w32-2.4.0_20221216.tar.xz 5195ff17de15ffd8629bfd0f0b5dd2b2774295f2 gnupg-w32-2.4.0_20221216.exe Internationalization ==================== This version of GnuPG has support for 26 languages with Chinese (traditional and simplified), Czech, French, German, Italian, Japanese, Norwegian, Polish, Russian, Turkish, 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 the 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/T6303 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 has mostly been 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. Fortunately, and this is still not common with free software, we have established a way of financing the development while keeping all our software free and freely available for everyone. Our model is similar to the way RedHat manages RHEL and Fedora: Except for the actual binary of the MSI installer for Windows and client specific configuration files, all the software is available under the GNU GPL and other Open Source licenses. Thus customers may even build and distribute their own version of the software as long as they do not use our trademarks GnuPG Desktop? or GnuPG VS-Desktop?. 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, answering questions on the mailing lists, or helped with donations. *Thank you all* 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 four 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) brainpoolP256r1 2021-10-15 [expires: 2029-12-31] 02F3 8DFF 731F F97C B039 A1DA 549E 695E 905B A208 GnuPG.com (Release Signing Key 2021) 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. -- The pioneers of a warless world are the youth that refuse military service. - A. Einstein -------------- next part -------------- A non-text attachment was scrubbed... Name: openpgp-digital-signature.asc Type: application/pgp-signature Size: 227 bytes Desc: not available URL: