Tracking of the GnuPG VS Desktop version 3.3.x
Details
Fri, Aug 29
re 1: Only if the option --auto-key-upload is used/configured.
re 2: Do not configure --auto-key-upload but give it on the command line.
re 3: Do not use --auto-key-upload - maybe I should add a --no-auto-key-upload option.
Thu, Aug 28
Hi
I have some questions about the "auto-key-upload: If an LDAP keyserver is configured (in dirmngr), upload a newly created key directly to that server" feature:
- If an LDAP keyserver is configured, will every newly created key be uploaded? Is this upload behavior enabled by default?
- Even with an LDAP keyserver configured, what if we don’t want to upload by default? If we prefer manual approval or want to upload only a specific subkey, how should we handle that?
- What about keys created for testing, temporary use, or personal privacy-sensitive purposes that we don’t want others to discover?
People who use GPG tend to care deeply about privacy and don’t want to upload or expose unnecessary information.
Tue, Aug 26
The culprit seems to be commit rO6cb4ccf4d8db03e9922984d9c5f5bf7f8806954d but a brief inspection does not show any problematic code. Thus this might be due to an Outlook peculiarity.
Tue, Aug 19
Mostly looks good to me on GnuPG-VS-Desktop-3.3.90.8-Beta-Standard.msi (3.3.3 betaversion) @ win10
(tested with 10 restarts)
looks correct
Mostly looks good to me on GnuPG-VS-Desktop-3.3.90.8-Beta-Standard.msi (3.3.3 betaversion) @ win10
Looks good to me on GnuPG-VS-Desktop-3.3.90.8-Beta-Standard.msi (3.3.3 betaversion)
Looks good to me on GnuPG-VS-Desktop-3.3.90.8-Beta-Standard.msi (3.3.3 betaversion)
Fri, Aug 8
Thu, Aug 7
works in vsd3.3.3, tested with VS-Desktop-3.3.90.8-Beta
Tue, Aug 5
Mon, Aug 4
The gold rule of tab order is that tab order follows the usual reading direction, i.e. line by line from left to right. If you press Enter after entering the password in the first input field then the focus should jump to the second input field.
Looks good to me on gpg4win-5.0.0-beta357 @ win10:
Jul 29 2025
The fix should be available in gpg4win-5.0.0-beta350.
Jul 28 2025
Jul 25 2025
Jul 17 2025
I could not reproduce this issue with Gpg4win 4.4.1 and did not see it with Gpg4win-5.0.0-beta345, either.
I could not reproduce this issue with Gpg4win 4.4.1 (which should have it).