Re: [Announce] GnuPG 2.5.21 released (Werner Koch)

--===============0966599101879806850==
Content-Type: multipart/signed; boundary="nextPartD-BOu-zJTpCNPJtPVq9SJA";
 micalg="pgp-sha512"; protocol="application/pgp-signature"

--nextPartD-BOu-zJTpCNPJtPVq9SJA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; protected-headers="v1"
From: Ingo =?UTF-8?B?S2zDtmNrZXI=?= <[email protected]>
To: [email protected]
Reply-To: [email protected]
Subject: Re: [Announce] GnuPG 2.5.21 released (Werner Koch)
Date: Tue, 14 Jul 2026 13:43:51 +0200
Message-ID: <[email protected]>
In-Reply-To: <[email protected]>
MIME-Version: 1.0

On Dienstag, 14. Juli 2026 00:30:31 Mitteleurop=C3=A4ische Sommerzeit Vinay=
 Sajip=20
via Gnupg-devel wrote:
> There appears to be a regression from 2.5.20: a decryption filename is
> passed when decrypting a file, which doesn't seem to preserve the file mo=
de
> under some circumstances. The particular circumstance is that I call the
> decryption twice on the same input. The first time, I provide the entire
> input to be decrypted, and get a satisfactory response from gpg. The seco=
nd
> call, to test a failure condition, makes the same call again, but doesn't
> provide the input data. In this case gpg returns an exit code of 2
> (expected) but resets the file mode of the output file to 0100644, where =
it
> had originally been set to 0100700. Under 2.5.20, the mode of the file
> wasn't changed. So the behaviour has changed between 2.5.20 and 2.5.21: is
> there a good reason for this regression, or should an issue be raised? In
> case it is helpful, I show below some relevant messages from gpg and the
> test harness for both cases.

This is probably a side-effect of this change in 2.5.21:
   - gpg, gpgsm: Use partial file on decryption, remove on failure.
     Disable with "--compatibility-flags=3Dno-partial-file-guard".
     [T7873]

Check if running gpg with --compatibility-flags=3Dno-partial-file-guard wor=
ks for=20
you.

Regards,
Ingo
--nextPartD-BOu-zJTpCNPJtPVq9SJA
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iJEEABYKADkWIQTbjgIOMowwlCBgvyGxb1mVFkdKugUCalYg9xsUgAAAAAAEAA5t
YW51MiwyLjUrMS4xMiwyLDIACgkQsW9ZlRZHSrrOgAEAlyjQ7uLLU1E31f01prFB
1ayY2SCatmLOehnksCapCZ0A/24codXSwyBgNY9rkE1Z0+LAfU4YyhDv2Buxs8bq
PWkF
=zkCE
-----END PGP SIGNATURE-----

--nextPartD-BOu-zJTpCNPJtPVq9SJA--





--===============0966599101879806850==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Gnupg-devel mailing list
[email protected]
https://lists.gnupg.org/mailman/listinfo/gnupg-devel

--===============0966599101879806850==--