I think "not certified" is ok if several UIDs with different certification states exist.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Fri, Mar 7
Thu, Mar 6
Version 4.0.0.250370 (Gpg4win-5.0.0-beta125):
Works as described with Version 4.0.0.250370 (Gpg4win-5.0.0-beta125):
Wed, Mar 5
Point 1 from the list in the descryption seems to be covered.
Regarding point 2: Is there some visual feedback possible like in web forms when you type a not valid value?
And point 3 from the list: Ingo suggested to do the same as we do for the mail field when adding a UID or creating a key.
It is KF6.9.0 in Gpg4win-5.0.0-beta125
Ok, the behavior is different depending on if
Oh, then I mistakenly assumed that this behavior is the same in Gpg4win and GnuPG-VSD…
Then this seems to be by design although it does not make sense IMHO to handle this aspect differently between 4win und VSD.
Mar 4 2025
The point here is that I tried to reset with the resetting code, not with the Admin PIN.
As you said we do have an error code for the wrong reset code. Which does not come up.
Ok, with VSD 3.3.0 and 4win 4.4.0 both I see
--import-options only-pubkeys
in a gpgme log when importing a key from WKD.
Feb 28 2025
I remove the milestone tag, as that one means "fixed in version 2.2.46" and added the general gnupg tag
With Gpg4win-Beta60 before the Gpg4win 4.4. release it was "reset code", see https://dev.gnupg.org/T5960#191665, seems there was a change after that
I have no idea how to test this aside from the test done in T7146.
Feb 27 2025
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:
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: