To make the test complete for VSD, here the times for decryption (and verification) of the 3G file from above:
The cli was done in both tests with the gpg version from VSD 3.3.0
Tested encryption (+ signature) via Kleopatra with a 3 GB file (random data) with:
Ok, then this will not be included in the VSD versions until we switch away from gpg 2.2
Closing as there are now 2 follow up tickets for the open issues I found.
VS-Desktop-3.3.0.0 now has the translation. Will be in Gpg4win in the next release.
In contrast to Gpg4win 4.4 in VSD 3.3.0 dragging a plain file onto Kleopatra will return an error. Decryption and importing certificates works, though.
There is a new report where mails are not shown with the following settings:
HKCU\Software\Microsoft\Office\16.0\Outlook\Options\Mail:ReadAsPlain ->0<- HKCU\Software\Policies\Microsoft\Office\16.0\Outlook\Options\Mail:ReadAsPlain ->1<-
Works as well for VS-Desktop-3.2.94.481-Beta
In VS-Desktop-3.2.94.481-Beta the feature is not available in the context menu in Kleopatra.
So in VSD 3.3.0 this will be missing. What works is disable/enable on the command line and Kleopatra will then not list a disabled certificate with most filters.
VS-Desktop-3.2.94.481-Beta: OK
VS-Desktop-3.2.94.481-Beta: OK
VS-Desktop-3.2.94.481-Beta: looks the same as with Gpg4win 4.4.
With VS-Desktop-3.2.94.481-Beta:
If an Ldap NtdsKeyserver is configured, there is now no warning on the upload. But the success message is wrong or at least not right:
"OpenPGP certificates exported successfully." Made me think I did mistakenly choose something other than "Publish on server".
And the menu entry is "Publish on Server..." so there has to be another window before action is taken.
Same in VS-Desktop-3.2.94.481-Beta
Ok now:
VS-Desktop-3.2.94.481-Beta: We now bring up the German version for the SecOps, as we do not have an official translation yet. The document will be replaced when we have that
Works in VS-Desktop-3.2.94.481-Beta and you even see beforehand which algo will be used:
VS-Desktop-3.2.94.481-Beta: same as for the Gpg4win version.
And there is a hint if you enter "hkps://something" that this is not the right format (that is included in Gpg4win 4.4.0, too)
VS-Desktop-3.2.94.481-Beta: the option is removed in the Kleopatra settings and the tags are shown in the main certificate list as well as in the tabs of the certificate details.
The Signature Card V2.0 is automatically loaded in VS-Desktop-3.2.94.481-Beta.
Other Telesec Cards, too, though this might take quite a while (e.g. the NetKey 3.0 card) and often a new reload is required.
VSD-Beta-481: Encrypting/signing with gpgtar on the cli and decrypting/verifying with Kleopatra works
I set this to resolved after a quick replay of the original report situation did not show any issue.
If it occurs again please reopen.
What is the status (or maybe better scope) of this ticket? Why was it set to the milestone 2.4.5?
I do not see any improvement in Kleopatra from Gpg4win 4.4 (with gpg 2.4.7) regarding the behavior when trying to unblock a card.
In VSD Beta-481 the translation is missing
Hm, "Names for the certificate" seems wrong to me. Shouldn't it better be "Names in the User IDs [of this certificate]"? I would leave of the part in [] as redundant. Likewise for the mail addresses.
works in VS-Desktop-3.2.94.481-Beta
works for VS-Desktop-3.2.94.481-Beta, too
works with VS-Desktop-3.2.94.481-Beta
VS-Desktop-3.2.94.481-Beta: works, if no kleopatragroupsrc is found at the new location, the one at the old location is used.
This is only relevant in the case that after the update to this version GpgOL is used without starting Kleopatra in between.
Because when Kleopatra is started it will copy the kleopatragroupsrc from the old location to the new one. After that the config file in the old location is ignored.
works in VS-Desktop-3.2.94.481-Beta. The "Trust Root Certificate" is no longer offered in the context menu.
works in VS-Desktop-3.2.94.481-Beta
works in VS-Desktop-3.2.94.481-Beta, the certificate for the newly generated key has the default expiry date of 3 years there.
Werner says this won't be fixed…
Because the system can be configured to use constraints which we can't explain except in ABNF, which won't help users.