User Details
- User Since
- Mar 27 2017, 4:48 PM (397 w, 5 d)
- Availability
- Available
Oct 8 2024
Was the fix part of a stable release? The beta was 4.2.1b55. Stable download on https://gpg4win.de/ is 4.3.1. Am I correctly assuming, that 4.3.1 includes the fix and this issue here can be closed?
Aug 20 2024
2.2.44 seems to be released. Is it correct that this issue shows as "open"?
May 16 2024
Mar 9 2022
Jul 10 2019
We as GPGTools would also like to see this addition being integrated into GnuPG, since we do plan to switch to keys.openpgp.org in the near future, as we have long been hoping for a key server with better performance and among other things email verification. Without this change, revocations would not work as expected in combination with hagrid however. Preferably of course in the 2.2.X branch.
May 2 2019
Users keep showing up in our support, confused by this inconsistency. This problem continues in 2020. What's holding this back?
Feb 1 2019
Hi Werner and thanks for looking into this.
Jan 30 2019
Aug 8 2018
ping, what's the status of this bug? it has been in testing for over one year. is that the correct status?
Jun 15 2018
Mar 22 2018
Hi Werner. Did you by any chance already find the time to look into the changes?
Mar 5 2018
Aug 2 2017
Just for the protocol: This fix made it into the 2.1.22 release. Thanks a lot! (bug has tag "gpg22" though)