Libgcrypt is a general purpose cryptography library used for GnuPG2.

For more information see the project home page:

        https://gnupg.org/software/libgcrypt/

The following packages have been upgraded in the Cygwin distribution:

- libgcrypt-devel       1.11.1
- libgcrypt20           1.11.1

As there are multiple changes each release, see the link or list of
changes below, or read /usr/share/doc/libgcrypt/NEWS after installation;
for complete details of changes read /usr/share/doc/libgcrypt/ChangeLog
after installation.

        https://dev.gnupg.org/T7166


2025-05-07    1.11.1

Bug fixes:

- Fix build regression on 32 bit Windows using Clang.
- Fix build regression on macOS due to symbol naming.
- Fix Kyber secret-dependent branch introduced by recent versions of Clang.
- Fix build regression due to the use of AVX512 in Blake.
- Do not build i386 asm on amd64 and vice versa.
- Fix build regression on armhf with gcc-14.
- Return the proper error code on malloc failure in hex2buffer.
- Fix long standing bug for PRIME % 2 == 0.

Performance:

- Add AES Vector Permute intrinsics implementation for AArch64.
- Add GHASH AArch64/SIMD intrinsics implementation.
- Add RISC-V vector permute AES.
- Add GHASH RISC-V Zbb+Zbc implementation.
- Add ChaCha20 RISC-V vector intrinsics implementation.
- Add SHA3 acceleration for RISC-V Zbb extension.

Other:

- Add CET support for i386 and amd64 assembly.
- Add PAC/BTI support for AArch64 asm.
- Apply changes to Kyber from upstream for final FIPS 203.
- Introduce an internal API for a revampled FIPS service indicator.
- Several improvements for constant time operation by the introduction
  of Least Leak Intended (LLI) variants of internal functions.
- Remove WindowsCE support.

-- 
              *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

The easiest way to unsubscribe is to visit 
<https://cygwin.com/mailman/options/cygwin-announce>, and click 'Unsubscribe'.

If you need more information on unsubscribing, start reading here: 
<https://sourceware.org/lists.html#unsubscribe>.

Reply via email to