2.5.21 regression with file mode

Vinay Sajip vinay_sajip at yahoo.co.uk
Wed Jul 15 10:05:03 CEST 2026


Dear Ingo,
> Check if running gpg with --compatibility-flags=no-partial-file-guard works for you.

Thanks for the suggestion. I tried it, but the result is the same. Does the --compatibility-flags argument have to be in a particular position in the argument list?
Kind regards,
Vinay Sajip
# Run failing decryption with compatibility flag
gpg2 --pinentry-mode loopback --status-fd 2 --no-tty --no-verbose --fixed-list-mode --batch --with-colons --homedir /tmp/keys-eidfw1_9 --passphrase-fd 0 --debug-quick-random --decrypt --yes --output /tmp/pygpg-test-qjrpzkgk.dec --compatibility-flags=no-partial-file-guard
# Status output from gpg
[GNUPG:] NODATA 2
[GNUPG:] FAILURE decrypt 429496729
gpg: decrypt_message failed: Unknown system error
# Messages from test harness
gpg returned a non-zero error code: 2
# The compatibility flag didn't change the result - the mode was still changed
Mode changed for /tmp/pygpg-test-qjrpzkgk.dec: 0o100664 vs. 0o100700

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20260715/9d970780/attachment.html>


More information about the Gnupg-devel mailing list