From dgouttegattat at incenp.org  Fri Jan  3 21:59:56 2025
From: dgouttegattat at incenp.org (Damien Goutte-Gattat)
Date: Fri,  3 Jan 2025 20:59:56 +0000
Subject: [PATCH GnuPG 0/2] Allow AES-128 with Kyber, but force AES-256
Message-ID: <20250103205958.26976-1-dgouttegattat@incenp.org>

The following patch set attempts to fix issue 7472 [1] by:

* when decrypting a session key encrypted to a Kyber key, accepting a
  session key of any size, and simply printing a warning if quantum
  resistance was required;

* when encrypting, force the use of AES-256 (overriding key and user
  preferences if needed) if quantum resistance has been requested, or
  if we only encrypt to Kyber keys and the user did not explicitly
  request a different algo with --cipher-algo.

[1] https://dev.gnupg.org/T7472

Damien Goutte-Gattat (2):
  gpg: Allow smaller session keys with Kyber
  gpg: Force the use of AES-256 in some cases

 g10/encrypt.c    | 19 +++++++++++++++++++
 g10/pubkey-enc.c |  8 ++------
 2 files changed, 21 insertions(+), 6 deletions(-)

-- 
2.46.2



From dgouttegattat at incenp.org  Fri Jan  3 21:59:57 2025
From: dgouttegattat at incenp.org (Damien Goutte-Gattat)
Date: Fri,  3 Jan 2025 20:59:57 +0000
Subject: [PATCH GnuPG 1/2] gpg: Allow smaller session keys with Kyber
In-Reply-To: <20250103205958.26976-1-dgouttegattat@incenp.org>
References: <20250103205958.26976-1-dgouttegattat@incenp.org>
Message-ID: <20250103205958.26976-2-dgouttegattat@incenp.org>

* g10/pubkey-enc.c (get_it): Do not error out when decrypting a session
key of less than 32 octets encrypted to a Kyber key.
--

GnuPG-bug-id: 7472
Signed-off-by: Damien Goutte-Gattat <dgouttegattat at incenp.org>
---
 g10/pubkey-enc.c | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/g10/pubkey-enc.c b/g10/pubkey-enc.c
index 4d2d6d46b..3cbd5624a 100644
--- a/g10/pubkey-enc.c
+++ b/g10/pubkey-enc.c
@@ -307,13 +307,9 @@ get_it (ctrl_t ctrl,
 
   if (sk->pubkey_algo == PUBKEY_ALGO_KYBER)
     {
-      /* We expect a 32 byte session key.  We should not see this
-       * error here because due to the KEM mode the agent_pkdecrypt
-       * should have already failed.  */
-      if (nframe != 32)
+      if (nframe != 32 && opt.flags.require_pqc_encryption)
         {
-          err = gpg_error (GPG_ERR_WRONG_SECKEY);
-          goto leave;
+          log_info (_("WARNING: session key is not quantum-resistant\n"));
         }
       dek->keylen = nframe;
       dek->algo = enc->d.seskey_algo;
-- 
2.46.2



From dgouttegattat at incenp.org  Fri Jan  3 21:59:58 2025
From: dgouttegattat at incenp.org (Damien Goutte-Gattat)
Date: Fri,  3 Jan 2025 20:59:58 +0000
Subject: [PATCH GnuPG 2/2] gpg: Force the use of AES-256 in some cases
In-Reply-To: <20250103205958.26976-1-dgouttegattat@incenp.org>
References: <20250103205958.26976-1-dgouttegattat@incenp.org>
Message-ID: <20250103205958.26976-3-dgouttegattat@incenp.org>

* g10/encrypt.c (create_dek_with_warnings): Forcefully use AES-256 if
PQC encryption was required or if all recipient keys are Kyber keys.
--

If --require-pqc-encryption was set, then it should be safe to always
force AES-256, without even checking if we are encrypting to Kyber keys
(if some recipients do not have Kyber keys, --require-pqc-encryption
will fail elsewhere).

Otherwise, we force AES-256 if we encrypt *only* to Kyber keys -- unless
the user explicitly requested another algo, in which case we assume they
know what they are doing.

GnuPG-bug-id: 7472
Signed-off-by: Damien Goutte-Gattat <dgouttegattat at incenp.org>
---
 g10/encrypt.c | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/g10/encrypt.c b/g10/encrypt.c
index e4e56c8b1..9b27b595b 100644
--- a/g10/encrypt.c
+++ b/g10/encrypt.c
@@ -139,6 +139,25 @@ create_dek_with_warnings (pk_list_t pk_list)
       dek->algo = opt.def_cipher_algo;
     }
 
+  if (dek->algo != CIPHER_ALGO_AES256)
+    {
+      /* If quantum resistance was explicitly required, we force the
+       * use of AES256 no matter what. Otherwise, we force AES256 if we
+       * encrypt to Kyber keys only and the user did not explicity
+       * request another another algo. */
+      if (opt.flags.require_pqc_encryption)
+        dek->algo = CIPHER_ALGO_AES256;
+      else if (!opt.def_cipher_algo)
+        {
+          int non_kyber_pk = 0;
+          for ( ; pk_list; pk_list = pk_list->next)
+            if (pk_list->pk->pubkey_algo != PUBKEY_ALGO_KYBER)
+              non_kyber_pk += 1;
+          if (!non_kyber_pk)
+            dek->algo = CIPHER_ALGO_AES256;
+        }
+    }
+
   return dek;
 }
 
-- 
2.46.2



From wk at gnupg.org  Tue Jan  7 08:14:44 2025
From: wk at gnupg.org (Werner Koch)
Date: Tue, 07 Jan 2025 08:14:44 +0100
Subject: [PATCH GnuPG 0/2] Allow AES-128 with Kyber, but force AES-256
In-Reply-To: <20250103205958.26976-1-dgouttegattat@incenp.org> (Damien
 Goutte-Gattat via Gnupg-devel's message of "Fri, 3 Jan 2025 20:59:56
 +0000")
References: <20250103205958.26976-1-dgouttegattat@incenp.org>
Message-ID: <875xmrw0wr.fsf@jacob.g10code.de>

Hi!

Thanks for the patches.  Both applied.


Shalom-Salam,

   Werner

-- 
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: 247 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20250107/00be0254/attachment.sig>

From rjh at sixdemonbag.org  Tue Jan  7 10:49:33 2025
From: rjh at sixdemonbag.org (Robert J. Hansen)
Date: Tue, 7 Jan 2025 04:49:33 -0500
Subject: libassuan build failure on macOS 15.1.1
Message-ID: <3f340fcc-54b5-41ae-bf2b-cd0f837596be@sixdemonbag.org>



The latest libassuan is failing to build on macOS 15.1.1. I already have 
a recent GnuPG installed from Homebrew, but wanted to look at 2.5.2.

Configuration flags used: --enable-static
Compiler info:
	Apple clang version 16.0.0 (clang-1600.0.26.4)
	Target: arm64-apple-darwin24.1.0
	Thread model: posix
Output:

/bin/sh ../libtool  --tag=CC   --mode=link gcc  -g -O2 -Wall 
-Wcast-align -Wshadow -Wstrict-prototypes -Wpointer-arith 
-version-info 9:1:0  -o libassuan.la -rpath /usr/local/lib 
libassuan_la-assuan.lo libassuan_la-context.lo libassuan_la-system.lo 
libassuan_la-debug.lo libassuan_la-conversion.lo 
libassuan_la-sysutils.lo libassuan_la-client.lo libassuan_la-server.lo 
libassuan_la-assuan-error.lo libassuan_la-assuan-buffer.lo 
libassuan_la-assuan-handler.lo libassuan_la-assuan-inquire.lo 
libassuan_la-assuan-listen.lo libassuan_la-assuan-pipe-server.lo 
libassuan_la-assuan-socket-server.lo libassuan_la-assuan-pipe-connect.lo 
libassuan_la-assuan-socket-connect.lo libassuan_la-assuan-uds.lo 
libassuan_la-assuan-logging.lo libassuan_la-assuan-socket.lo 
libassuan_la-system-posix.lo libassuan_la-assuan-io.lo  memrchr.lo 
-L/opt/homebrew/opt/libgpg-error/lib -lgpg-error
libtool: link: gcc -dynamiclib -Wl,-undefined -Wl,dynamic_lookup -o 
.libs/libassuan.9.dylib  .libs/libassuan_la-assuan.o 
.libs/libassuan_la-context.o .libs/libassuan_la-system.o 
.libs/libassuan_la-debug.o .libs/libassuan_la-conversion.o 
.libs/libassuan_la-sysutils.o .libs/libassuan_la-client.o 
.libs/libassuan_la-server.o .libs/libassuan_la-assuan-error.o 
.libs/libassuan_la-assuan-buffer.o .libs/libassuan_la-assuan-handler.o 
.libs/libassuan_la-assuan-inquire.o .libs/libassuan_la-assuan-listen.o 
.libs/libassuan_la-assuan-pipe-server.o 
.libs/libassuan_la-assuan-socket-server.o 
.libs/libassuan_la-assuan-pipe-connect.o 
.libs/libassuan_la-assuan-socket-connect.o 
.libs/libassuan_la-assuan-uds.o .libs/libassuan_la-assuan-logging.o 
.libs/libassuan_la-assuan-socket.o .libs/libassuan_la-system-posix.o 
.libs/libassuan_la-assuan-io.o .libs/memrchr.o 
-L/opt/homebrew/opt/libgpg-error/lib -lgpg-error  -O2   -install_name 
/usr/local/lib/libassuan.9.dylib -compatibility_version 10 
-current_version 10.1
duplicate symbol '___sputc' in:
     /Users/rjh/Downloads/libassuan-3.0.1/src/.libs/libassuan_la-server.o
  
/Users/rjh/Downloads/libassuan-3.0.1/src/.libs/libassuan_la-conversion.o
     /Users/rjh/Downloads/libassuan-3.0.1/src/.libs/libassuan_la-sysutils.o
  
/Users/rjh/Downloads/libassuan-3.0.1/src/.libs/libassuan_la-assuan-error.o
     /Users/rjh/Downloads/libassuan-3.0.1/src/.libs/libassuan_la-context.o
     /Users/rjh/Downloads/libassuan-3.0.1/src/.libs/libassuan_la-debug.o
  
/Users/rjh/Downloads/libassuan-3.0.1/src/.libs/libassuan_la-assuan-handler.o
  
/Users/rjh/Downloads/libassuan-3.0.1/src/.libs/libassuan_la-assuan-socket-server.o
  
/Users/rjh/Downloads/libassuan-3.0.1/src/.libs/libassuan_la-assuan-logging.o
  
/Users/rjh/Downloads/libassuan-3.0.1/src/.libs/libassuan_la-assuan-socket-connect.o
     /Users/rjh/Downloads/libassuan-3.0.1/src/.libs/libassuan_la-system.o
     /Users/rjh/Downloads/libassuan-3.0.1/src/.libs/libassuan_la-assuan-io.o
     /Users/rjh/Downloads/libassuan-3.0.1/src/.libs/libassuan_la-assuan.o
  
/Users/rjh/Downloads/libassuan-3.0.1/src/.libs/libassuan_la-system-posix.o
  
/Users/rjh/Downloads/libassuan-3.0.1/src/.libs/libassuan_la-assuan-inquire.o
  
/Users/rjh/Downloads/libassuan-3.0.1/src/.libs/libassuan_la-assuan-buffer.o
  
/Users/rjh/Downloads/libassuan-3.0.1/src/.libs/libassuan_la-assuan-pipe-server.o
  
/Users/rjh/Downloads/libassuan-3.0.1/src/.libs/libassuan_la-assuan-uds.o
     /Users/rjh/Downloads/libassuan-3.0.1/src/.libs/libassuan_la-client.o
  
/Users/rjh/Downloads/libassuan-3.0.1/src/.libs/libassuan_la-assuan-listen.o
  
/Users/rjh/Downloads/libassuan-3.0.1/src/.libs/libassuan_la-assuan-pipe-connect.o
  
/Users/rjh/Downloads/libassuan-3.0.1/src/.libs/libassuan_la-assuan-socket.o
ld: 1 duplicate symbols
clang: error: linker command failed with exit code 1 (use -v to see 
invocation)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 236 bytes
Desc: OpenPGP digital signature
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20250107/a6795fca/attachment.sig>

From gniibe at fsij.org  Wed Jan  8 00:54:18 2025
From: gniibe at fsij.org (NIIBE Yutaka)
Date: Wed, 08 Jan 2025 08:54:18 +0900
Subject: libassuan build failure on macOS 15.1.1
In-Reply-To: <3f340fcc-54b5-41ae-bf2b-cd0f837596be@sixdemonbag.org>
References: <3f340fcc-54b5-41ae-bf2b-cd0f837596be@sixdemonbag.org>
Message-ID: <87frlurxhx.fsf@akagi.fsij.org>

Hello,

Robert J. Hansen wrote:
> The latest libassuan is failing to build on macOS 15.1.1.

Thank you for your report.  It is handled in:

	https://dev.gnupg.org/T7177

The fix is simply remove the (unused) declaration in assuan-defs.h.
-- 


From rjh at sixdemonbag.org  Wed Jan  8 00:59:47 2025
From: rjh at sixdemonbag.org (Robert J. Hansen)
Date: Tue, 7 Jan 2025 18:59:47 -0500
Subject: libassuan build failure on macOS 15.1.1
In-Reply-To: <87frlurxhx.fsf@akagi.fsij.org>
References: <3f340fcc-54b5-41ae-bf2b-cd0f837596be@sixdemonbag.org>
 <87frlurxhx.fsf@akagi.fsij.org>
Message-ID: <919ee781-7247-484f-a034-bb38d1398100@sixdemonbag.org>

> The fix is simply remove the (unused) declaration in assuan-defs.h.

rjh at sarah libassuan-3.0.1 % grep -r ___sputc | grep -v "Binary file"
rjh at sarah libassuan-3.0.1 %

There is no such declaration.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 236 bytes
Desc: OpenPGP digital signature
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20250107/33509fcd/attachment.sig>

From gniibe at fsij.org  Wed Jan  8 08:19:05 2025
From: gniibe at fsij.org (NIIBE Yutaka)
Date: Wed, 08 Jan 2025 16:19:05 +0900
Subject: libassuan build failure on macOS 15.1.1
In-Reply-To: <919ee781-7247-484f-a034-bb38d1398100@sixdemonbag.org>
References: <3f340fcc-54b5-41ae-bf2b-cd0f837596be@sixdemonbag.org>
 <87frlurxhx.fsf@akagi.fsij.org>
 <919ee781-7247-484f-a034-bb38d1398100@sixdemonbag.org>
Message-ID: <877c75srh2.fsf@akagi.fsij.org>

"Robert J. Hansen" <rjh at sixdemonbag.org> wrote:
> rjh at sarah libassuan-3.0.1 % grep -r ___sputc | grep -v "Binary file"
> rjh at sarah libassuan-3.0.1 %
>
> There is no such declaration.

On macOS, __sputc is an inline function in stdio.h, and it is used by
the macro of putc_unlocked.  Removing unused putc_unlocked declaration
in libassuan fixed the problem.
-- 


From lennart.fricke at drehpunkt.com  Thu Jan  9 14:51:27 2025
From: lennart.fricke at drehpunkt.com (Lennart Fricke)
Date: Thu, 9 Jan 2025 14:51:27 +0100
Subject: PIV pin on yubikey
Message-ID: <aee82c8c-2314-4ec6-9c8d-caa2df06c64c@drehpunkt.com>

Hello everybody,

I'm trying to enroll gpg with PIV using YubiKeys and encountered a behavior, that might be a bug

after changing the piv pin with ykman (version: 5.2.1): `ykman piv access change-pin`

I cannot authenticate to the card using gpg-card, verify.

I also tried to change the pin using gpg-card, passwd. But I'm also getting 'Bad PIN' errors.

If you can tell me how to debug the issue I would be glad.

Thanks

Lennart Fricke


--
Lennart Fricke
DrehPunkt GmbH
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20250109/a5d8140c/attachment-0001.html>

From jjelen at redhat.com  Thu Jan  9 17:05:16 2025
From: jjelen at redhat.com (Jakub Jelen)
Date: Thu, 9 Jan 2025 17:05:16 +0100
Subject: PIV pin on yubikey
In-Reply-To: <aee82c8c-2314-4ec6-9c8d-caa2df06c64c@drehpunkt.com>
References: <aee82c8c-2314-4ec6-9c8d-caa2df06c64c@drehpunkt.com>
Message-ID: <CAHrFiA9=O_qkgD+j5-yq7r4abvc4ded6rMFsWyqzg996Zis1WQ@mail.gmail.com>

The yubikeys have two independent applets, PIV and OpenPGP. Changing a
PIN in one does not change the PIN in the other and vice versa. Did
you try the old PIN you used in OpenPGP applet?

Jakub

On Thu, Jan 9, 2025 at 4:25?PM Lennart Fricke via Gnupg-devel
<gnupg-devel at gnupg.org> wrote:
>
> Hello everybody,
>
> I'm trying to enroll gpg with PIV using YubiKeys and encountered a behavior, that might be a bug
>
> after changing the piv pin with ykman (version: 5.2.1): `ykman piv access change-pin`
>
> I cannot authenticate to the card using gpg-card, verify.
>
> I also tried to change the pin using gpg-card, passwd. But I'm also getting 'Bad PIN' errors.
>
> If you can tell me how to debug the issue I would be glad.
>
> Thanks
>
> Lennart Fricke
>
>
> --
> Lennart Fricke
> DrehPunkt GmbH
>
> _______________________________________________
> Gnupg-devel mailing list
> Gnupg-devel at gnupg.org
> https://lists.gnupg.org/mailman/listinfo/gnupg-devel



From her at sorah.jp  Mon Jan 13 13:28:13 2025
From: her at sorah.jp (Sorah Fukumori)
Date: Mon, 13 Jan 2025 21:28:13 +0900
Subject: [PATCH gnupg] agent: Fix a memory leak
Message-ID: <20250113122821.2587166-2-her@sorah.jp>

* agent/findkey.c (read_key_file): Free the buffer,
  which were forgotten to be freed at commit 434a641d40c on T6944.
  Otherwise the 'keyinfo --list' agent command gradually leads to
  memory exhaustion.

--

Fixes-commit: 434a641d40cbff82beb9f485e0adca72419bfdf2
Signed-off-by: Sorah Fukumori <her at sorah.jp>
---
 agent/findkey.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/agent/findkey.c b/agent/findkey.c
index 8efb7b320..5b9411c77 100644
--- a/agent/findkey.c
+++ b/agent/findkey.c
@@ -1193,6 +1193,7 @@ read_key_file (ctrl_t ctrl, const unsigned char *grip,
    else
     es_fclose (fp);
   xfree (fname);
+  xfree (buf);
   return err;
 }
 
-- 
2.47.1



From gniibe at fsij.org  Tue Jan 14 03:07:04 2025
From: gniibe at fsij.org (NIIBE Yutaka)
Date: Tue, 14 Jan 2025 11:07:04 +0900
Subject: [PATCH gnupg] agent: Fix a memory leak
In-Reply-To: <20250113122821.2587166-2-her@sorah.jp>
References: <20250113122821.2587166-2-her@sorah.jp>
Message-ID: <87ed16du7r.fsf@akagi.fsij.org>

Hello,

Sorah Fukumori wrote:
> * agent/findkey.c (read_key_file): Free the buffer,
>   which were forgotten to be freed at commit 434a641d40c on T6944.
>   Otherwise the 'keyinfo --list' agent command gradually leads to
>   memory exhaustion.

Thank you, good catch.  I applied it to master, in the commit:

	137481fa1002c417cd2c0661b9eefd893b0149d3
-- 


From wk at gnupg.org  Tue Jan 14 10:54:55 2025
From: wk at gnupg.org (Werner Koch)
Date: Tue, 14 Jan 2025 10:54:55 +0100
Subject: [Announce] GnuPG 2.5.3 released
Message-ID: <87msftsosw.fsf@jacob.g10code.de>

Hello!

We are pleased to announce the availability of a new GnuPG release:
version 2.5.3.  This release is the fourth of a series of public testing
releases eventually leading to a new stable version 2.6.  We also
release a second Beta version of the forthcoming Gpg4win 5.0.

The main features in the 2.6 series are improvements for 64 bit Windows
and the introduction of a PQC encryption algorithm.

Other than PQC support the 2.6 series will not differ a lot from 2.4
because the majority of changes are internal to make use of newer
features from the supporting libraries.


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.5.3 (2025-01-09)
================================================
         [compared to version 2.5.2]

  * gpg: Allow for signature subpackets of up to 30000 octets.
    [rG36dbca3e69]

  * gpg: Silence expired trusted-key diagnostics in quiet mode.  [T7351]

  * gpg: Allow smaller session keys with Kyber and enforce the use of
    AES-256 if useful.  [T7472]

  * gpg: Fix regression in key generation from existing card key.
    [T7309,T7457]

  * gpg: Print a warning if the card backup key could not be written.
    [T2169]

  * The --supervised options of gpg-agent and dirmngr have been
    renamed to --deprecated-supervised as preparation for their
    removal.  [rGa019a0fcd8]

  * There is no more default for a keyserver.

  Release-info: https://dev.gnupg.org/T7442


Getting the Software
====================

Please follow the instructions found at <https://gnupg.org/download/> 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
<https://gnupg.org/download/mirrors.html>.  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.3.tar.bz2 (7989k)
 https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.5.3.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.3_20250109.exe (5655k)
 https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.5.3_20250109.exe.sig

The source used to build this installer for 64-bit Windows is available at

 https://gnupg.org/ftp/gcrypt/gnupg/gnupg-w32-2.5.3_20250109.tar.xz (16M)
 https://gnupg.org/ftp/gcrypt/gnupg/gnupg-w32-2.5.3_20250109.tar.xz.sig

This Windows 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.

For Windows a *Beta* version of Gpg4win, our full featured Gpg4win
installer including this version of GnuPG as well as Kleopatra GUI
and a PDF editor can be retrieved from here:

 https://files.gpg4win.org/Beta/gpg4win-5.0.0-beta51/gpg4win-5.0.0-beta51.exe (43M)
 https://files.gpg4win.org/Beta/gpg4win-5.0.0-beta51/gpg4win-5.0.0-beta51.exe.sig

with the source code at:

 https://files.gpg4win.org/Beta/gpg4win-5.0.0-beta51/gpg4win-5.0.0-beta51.tar.xz (279M)
 https://files.gpg4win.org/Beta/gpg4win-5.0.0-beta51/gpg4win-5.0.0-beta51.tar.xz.sig



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.3.tar.bz2 you would use this command:

     gpg --verify gnupg-2.5.3.tar.bz2.sig gnupg-2.5.3.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.3.tar.bz2, you run the command like this:

     sha1sum gnupg-2.5.3.tar.bz2

   and check that the output matches the next line:

6dd8c940e1dff21d5e333a0ad3066e269e83df5e  gnupg-2.5.3.tar.bz2
50f416d52eb423e5b359812ba02ceca2cea85c91  gnupg-w32-2.5.3_20250109.tar.xz
acb39daee05aced0d37195f4ad739c16bda9aa5e  gnupg-w32-2.5.3_20250109.exe
84a1169f55e3ddef02567fd0f3a0b666a9881107  gpg4win-5.0.0-beta51.exe
2fa55c64ed9238c7b745fa8d54978d4713a7e2b9  gpg4win-5.0.0-beta51.tar.xz


Internationalization
====================

This version of GnuPG has support for 26 languages with Chinese
(traditional and simplified), Czech, French, German, Italian, Japanese,
Norwegian, Polish, Portuguese, 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/T7442 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.  Several full-time employed
developers and contractors are working exclusively on GnuPG and closely
related software like Libgcrypt, GPGME, Kleopatra 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.

-- 
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: openpgp-digital-signature.asc
Type: application/pgp-signature
Size: 247 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20250114/9a76db2c/attachment.sig>
-------------- next part --------------
_______________________________________________
Gnupg-announce mailing list
Gnupg-announce at gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-announce