In VSD 3.3.0 I can not check with "Rückstellcode" as the error message is now "Falsche PIN".
And the same in the released version Gpg4win 4.4.0.
Seems the gpg version now returns a different string:
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Feb 27 2025
No totally new install: I quit Kleopatra, then deleted %APPDATA%\kleopatra\kleopatrastaterc and %APPDATA%\gnupg and restarted Kleopatra. Then I imported the shown test certificate which has no expiry date.
Carl found some issue with this himself.
Checked again with VSD 3.3.0: no error any more. Therefore setting this to resolved, I probably made a mistake the last time.
works as described.
Closing this ticket after creation of two follow up tickets for the remaining issues.
Feb 26 2025
VSD 3.3.0:
Feb 25 2025
The button for "Encrypt to others" is gone:
VSD 3.3.0: The buttons work as soon as the certificates are imported. (Depending on the card this will take some time)
Feb 24 2025
VSD 3.3.0:
Haven't seen this in a while.
works in VSD 3.3.0:
VSD 3.3.0:
VSD 3.3.0: OK.
ok in VSD 3.3.0, too
Feb 20 2025
You have imported a certificate with secret key.
Fingerprint: XXX User ID: ABC
Feb 19 2025
Also, we should not forget the context of the whole dialog in the window. So we get the wording right, especially regarding key / certificate.
Feb 18 2025
Feb 14 2025
Background of my "reminder" comment: we were discussing to establish a sane workflow for sharing keys. Which is quite commonly done e.g. for functional mail addresses, but usually people seem to share the whole secret key which is not advisable. We would want people to only share subkeys for that purpose.
It was the case that somebody gets a subkey for such an "offline" primary for the first time which I was thinking of.
Reminder: we have to keep in mind the workflow of the import of secret subkeys. Do we need different behavior conditional on "is primary key present" or not?
Feb 13 2025
Another thing (should definitely go into a new ticket if we want to do something regarding this):
Again for Gpg4win 4.4.0, this time with better attention (and definitively encryption only):
Feb 12 2025
Shorter version:
Possible explanation text for the user regarding the background of the question (probably to long):
Feb 11 2025
Looks the same in VSD 3.3.0 ans in Gpg4win:
Everything mentioned above was translated and is now shown that way in all three languages.
I would keep the "create group", too.
Feb 5 2025
changed the workboard to gpd5x as this is still the case in Gpg4win 5.0-Beta versions.
same with VSD 3.3.0 with gpg 2.2.46
Feb 4 2025
Gpg4win-5.0.0-beta32
Works!
Gpg4win-5.0.0-beta32:
The remaining attempts are listed:
Feb 3 2025
For Gpg4win 4.4.0:
Encryption: ~2:35
Decryption: ~0:44