In T6481#181779, @gniibe wrote:Arch Linux: https://gitlab.archlinux.org/archlinux/packaging/packages/gnupg
FreeBSD: https://cgit.freebsd.org/ports/tree/security/gnupgI don't see the patch is applied. Please wait for GnuPG release 2.4.4.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Jan 23 2024
Jan 23 2024
juergenhoetzel added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).
Jan 22 2024
Jan 22 2024
juergenhoetzel added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).
In T6481#181724, @gniibe wrote:i still observe the same behavior:
What do you mean? I can't replicate the behavior described by you, using the GnuPG from the repo, or the one of Debian 2.4.3-2.
Jan 21 2024
Jan 21 2024
juergenhoetzel added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).
In T6481#171399, @gniibe wrote:
- It is also possible for GnuPG to keep the behavior of 2.4.0, so that it doesn't confuse EasyPG.
- This is a possible solution #2: change in master: rG2f872fa68c65: gpg: Report BEGIN_* status before examining the input.
- But... it is difficult for implementation of GnuPG to guarantee this kind of behavior.
For a while, distributions can apply rG2f872fa68c65 for 2.4 series.