home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   PUBLIC_KEYS      Public-Key Discussion Echo      845 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 828 of 845   
   Wilfred van Velzen to All   
   [Announce] GnuPG 2.5.16 released   
   27 Jan 26 18:34:41   
   
   TID: FMail-lnx64 2.3.2.6-B20251227   
   RFC-X-No-Archive: Yes   
   TZUTC: 0100   
   CHRS: CP850 2   
   PID: GED+LNX 1.1.5-b20240604   
   MSGID: 2:280/464 6978f770   
      
   Hello!   
      
   We are pleased to announce the availability of a new GnuPG release:   
   version 2.5.17.  This version fixes a *critical security bug* in   
   versions 2.5.13 to 2.5.16.  We also released a new Gpg4win version and   
   updated Debian packages.   
      
      
   Impact   
   ======   
      
   These versions are affected:   
      
    - GnuPG 2.5.16          (released 2025-12-30)   
    - GnuPG 2.5.15          (released 2025-12-29)   
    - GnuPG 2.5.14          (released 2025-11-19)   
    - GnuPG 2.5.13          (released 2025-10-22)   
    - Gpg4win 5.0.0         (released 2026-01-14)   
    - Gpg4win 5.0.0-beta479 (released 2026-01-02)   
    - Gpg4win 5.0.0-beta476 (released 2025-12-22)   
    - Gpg4win 5.0.0-beta395 (released 2025-10-22)   
      
   All other versions are not affected.   
      
   A crafted CMS (S/MIME) EnvelopedData message carrying an oversized   
   wrapped session key can cause a stack buffer overflow in gpg-agent   
   during the PKDECRYPT--kem=CMS handling.  This can easily be used for a   
   DoS but, worse, the memory corruption can very likley also be used to   
   mount a remote code execution attack.  The bug was introduced while   
   changing an internal API to the FIPS required KEM API.   
      
   A CVE-id has not been assigned.  We track this bug as T8044 under   
   https://dev.gnupg.org/T8044.  This vulnerability was discovered by:   
   OpenAI Security Research.  Their report was received on 2026-01-18;   
   fixed versions released 2026-01-27.   
      
      
   Solution   
   ========   
      
   If an affected GnuPG version is used please update ASAP to the new   
   version 2.5.17.   
      
   If an affected version of Gpg4win is used please update ASAP to the new   
   version 5.0.1.   
      
   If an immediate update is not possible please remove the gpgsm or   
   gpgsm.exe binary; this way the bug can't be remotely triggered.   
      
      
      
   Noteworthy changes in version 2.5.17 (2026-01-27)   
   =================================================   
            [compared to version 2.5.16]   
      
     * agent: Fix stack buffer overflow when using gpgsm and KEM.  This   
       was introduced with 2.5.13; see above.  [T8044]   
      
     * tpm: Fix possible buffer overflow in PKDECRYPT.  [T8045]   
      
     * gpg: Fix possible NULL-deref with overlong signature packets. [T8049]   
      
     * gpg: New export-option "keep-expired-subkeys".  [T7990]   
      
     * gpgsm: Make multiple search patterns work with keyboxd.  [T8026]   
      
     * agent: Add accelerator keys for "Wrong" and "Correct".  [T8055]   
      
     * dirmngr: Help detection of bad keyserver configurations.  [T7730]   
      
     Release-info: https://dev.gnupg.org/T7996   
      
      
      
   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 file 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.5.17.tar.bz2 (8113k)   
    https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.5.17.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.5.17_20260127.exe (5573k)   
    https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.5.17_20260127.exe.sig   
      
   The source used to build this installer for 64-bit Windows is available as   
      
    https://gnupg.org/ftp/gcrypt/gnupg/gnupg-w32-2.5.17_20260127.tar.xz (15M)   
    https://gnupg.org/ftp/gcrypt/gnupg/gnupg-w32-2.5.17_20260127.tar.xz.sig   
      
    This source tarball may also be used to download all required libraries   
    at once to build a Unix version on any modern system.  See the included   
    README.   
      
      
   Debian Packages   
   ===============   
      
   We also provide new Debian style packages for a couple of Debian   
   variants.  See https://repos.gnupg.org/deb/gnupg/trixie/ or use the menu   
   to switch to other distros/releases.  It may take a view hours before   
   the new packages show up.  If you encounter other packaging problems   
   please report them to the gnupg-devel mailing list.   
      
      
   Windows Installer   
   =================   
      
   A new version of Gpg4win (5.0.1), our full featured Windows installer,   
   including this version of GnuPG, the Kleopatra GUI, and a PDF reader has   
   also been released.  Head over to 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.5.17.tar.bz2 you would use this command:   
      
        gpg --verify gnupg-2.5.17.tar.bz2.sig gnupg-2.5.17.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.5.17.tar.bz2, you run the command like this:   
      
        sha1sum gnupg-2.5.17.tar.bz2   
      
      and check that the output matches the next line:   
      
   ee0bc59eadf258b6d92131911b5dca6cabc89419  gnupg-2.5.17.tar.bz2   
   8826ff58e245c9700391fefff34afe775300e7cd  gnupg-w32-2.5.17_20260127.tar.xz   
   31ac31fe8f5b4f3e3ae8e5e6a70c967a59f66e63  gnupg-w32-2.5.17_20260127.exe   
      
      
   Internationalization   
   ====================   
      
   This version of GnuPG has support for 26 languages with Chinese, Czech,   
   Dutch, French, Georgian, German, Italian, Japanese, Norwegian, Polish,   
   Portuguese, Russian, Swedish, 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.   
      
   If you are using cleartext signatures in your application please read   
   https://gnupg.org/blog/20251226-cleartext-signatures.html .   
      
   In case of build problems specific to this release please first check   
   https://dev.gnupg.org/T7996 for updated information.  We are sorry that   
   due to ongoing DoS on this service, you may end up at a "is under   
   maintenance page".   
      
   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.  A team of full-time employed   
   developers and contractors are working exclusively on GnuPG and related   
   software like Libgcrypt, GPGME, Kleopatra, Okular, 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:   
      
       ed25519 2020-08-24 [SC] [expires: 2030-06-30]   
       6DAA 6E64 A76D 2840 571B  4902 5288 97B8 2640 3ADA   
       Werner Koch (dist signing 2020)   
      
       ed25519 2021-05-19 [SC] [expires: 2027-04-04]   
       AC8E 115B F73E 2D8D 47FA  9908 E98E 9B2D 19C6 C8BD   
       Niibe Yutaka (GnuPG Release Key)   
      
       rsa3072 2025-05-09 [SC] [expires: 2033-03-03]   
       3B76 1AE4 E63B F351 9CE7  D63B ECB6 64CB E133 2EEF   
       Alexander Kulbartsch (GnuPG Release Key)   
      
       brainpoolP256r1 2021-10-15 [SC] [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.   
      
   * Debian Package Signing Key:   
     The new Debian style packages are signed using this key:   
      
     ed25519 2025-07-08 [SC] [expires: 2035-07-14]   
     3209 7B71 9B37 45D6 E61D DA1B 85C4 5AE3 E1A2 B355   
     GnuPG.org Package Signing Key    
      
     See the package website (https://repos.gnupg.org/deb/gnupg) for a list   
     of supported distributions and a download link for the key.   
      
   --   
   Arguing that you don't care about the right to privacy because you have   
   nothing to hide is no different from saying you don't care about free   
   speech because you have nothing to say.                - Edward Snowden   
      
      
      
   _______________________________________________   
   Gnupg-announce mailing list   
   Gnupg-announce@gnupg.org   
   http://lists.gnupg.org/mailman/listinfo/gnupg-announce   
      
      
   --- FMail-lnx64 2.3.2.6-B20251227   
    * Origin: FMail development HQ (2:280/464)   
   SEEN-BY: 50/22 103/705 105/81 106/201 124/5016 128/187 153/757 7715   
   SEEN-BY: 154/10 30 110 203/0 218/700 221/0 226/30 227/114 229/110   
   SEEN-BY: 229/112 134 206 317 400 426 428 470 664 700 705 240/1120   
   SEEN-BY: 240/5832 266/512 280/464 5003 5006 291/111 292/854 8125 301/1   
   SEEN-BY: 310/31 320/219 322/757 341/66 234 342/200 396/45 423/120   
   SEEN-BY: 460/58 256 1124 633/280 712/848 770/1 902/26 5020/400 8912   
   SEEN-BY: 5054/30 5075/35   
   PATH: 280/464 460/58 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca