Tracking of the GnuPG VS Desktop version 3.3.x
Details
Wed, Dec 11
Backported the latest change for VSD 3.3
Tested with a Gpg4win-Beta and VSD-3.2.94.474-Beta:
Ingo prefers to hide the origin by default, so please make this one change so that the UID tab columns looks like this by default:
Name, Email, Trust Level, [Origin], [Tags]
Tue, Dec 10
VS-Desktop-3.2.94.474-Beta:
This is, what it looks like after generating the first key in a fresh installation:
Mon, Dec 9
ok, then we leave it in the certifications tab like it is.
What about the Uid tab? Keep it like it is, which is: Name, Email, Trust Level, Origin, [Tags] ?
While I do not think that the origin need to be shown by default, I don't think it's really a problem, as this is the last column
Fri, Dec 6
"Tags" are stored with certifications. Therefore, I think it's useful and makes sense to show the Tags column in the Certifications view.
Gpg4win 4.4:
Some questions (wishes):
- Will the upload also be done to an configured LDAP Server?
- Can the upload-checkbox setting be configure via the Windows registry?
Gpg4win 4.4: ok, now the date of the main key is preset as the expiry date of the main key if it is less then 3 years in the future. Otherwise 3 years from now is preset.
Ok, I'm not asked, therefore I set this to done, but not resolved yet, as I'm not sure if the gpg version might have an influence.
Gpg4win 4.4:
Contrary to the task description are:
a) In the certifications tab the "tags" column is shown by default
b) in the UID tab, the "origin" column is shown by default (only the "tags" column is hidden)
The only difference that you should see in the UI is that there is no longer a menu that pops up when you drop files, asking you what to do with the files. So I guess, if things works fine as you described them, you can consider the ticket done
This ticket description does not give me anything to test.
tested with Gpg4win 4.4
tested with Gpg4win 4.4
Thu, Dec 5
Better a new ticket for the rest, see T7441
Tue, Dec 3
Backported for VSD 3.3 / Gpg4win 4.4.1.
I'll backport this for VSD 3.3 / Gpg4win 4.4.1. Regression risk is minimal.
Backported for VSD 3.3.x / Gpg4win 4.4.1
I'll backport this because this issue is a really bad usability problem for people using the Windows Explorer integration to decrypt files. And the regression risk is minimal.
I think you are right, it is fixed. I tried it now again with Gpg4win 4.4 with several cards and it works as you describe.
Mon, Dec 2
Gpg4win 4.4:
When a keyserver is configured you can now check a box to directly upload the revocation there.
If no keyserver is configured, this is correctly not offered. Instead it is exported to the Documents folder, like the dialog informs,
Wed, Nov 27
Tue, Nov 26
Gpg4win-Beta-94:
Looks good, here the file was changed after the first two signed it:
with Gpg4win-Beta-94: about that speed on Windows, too.
Could be a bit more refined in the future, but this would be for another ticket.
With the fix, the dialog opens instantly (< 1 second loading time)
Gpg4win-Beta-94: ok
Gpg4win-Beta-94: done
Gpg4win-Beta-94: works
Gpg4win-Beta-94: works
With Gpg4win-Beta-94 now all is fine, even own deactivated certificates are now shown (using the "Disabled" filter) in bold font
Fixed in Gpg4win-Beta-94
Mon, Nov 25
Well, T6893 was removed from this release, at least for the windows builds, therefore it can not be tested on windows for vsd33
Yes, much improved, changes as described in https://dev.gnupg.org/T6933#181791
tested with Gpg4win-Beta-75++