Verzeichnis von C:\Users\g10code.WIN-TEST3\Documents\testordner\Unterordner 05.04.2023 09:34 <DIR> . 05.04.2023 09:34 <DIR> .. 30.03.2023 15:18 36 Textdatei3.txt 1 Datei(en), 36 Bytes 2 Verzeichnis(se), 19.342.049.280 Bytes frei
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Apr 5 2023
works with gpgtar (GnuPG) 2.2.42-beta102, too
Only Sign results in the same error as Sign+Encrypt (which was the picture above)
Apr 3 2023
closed, as the remaining subtask is found at T6436
On gpg4win 4.1.0 (and GnuPG VSD 3.1.26) there are no longer password prompts for the subkeys when exporting (or making a backup from) secret keys.
Aborting does not result in a general error any more. Testet with 3.1.26
Mar 29 2023
It's partially resolved, the rest is wontfix at the moment
works
works in 3.1.27.0-beta44
For Testversion 3.1.27.0-beta44 for "Regenerate key" now the same algorithms as in 3.2.0 are offered for a Yubikey and it is possible to move them to the smart card.
This is fine even for not VSD-compliant keys, as they are marked as such.
Mar 27 2023
works. Tested on 3.1.26 with AD configured as keyserver.
closing, as the remaining issue is covered by T6093
Mar 24 2023
Should we also differentiate between wrong PUK and no PUK set?
Mar 23 2023
closing with reference to external testing
Mar 22 2023
works in gnupg24.
works
I'd say yes.
The "Secret key backup error" does not appear any more.
But if I hit "cancel" on the pinentry window, still a second pinentry window for the subkey pops up. No matter if I give the correct password in the second pinentry window or not, the backup is silently abandoned.
Mar 21 2023
yes, confirmed. And if I insist on choosing this certificate via the selection dialog I can not encrypt to this certificate, as sign/encrypt is grayed out. (As long as there is no valid key chosen additionally.)
closing with reference to external testing
ok, ticket for the new issue is T6418
Mar 20 2023
This exact step works. But if you misspell the repeat its unintuitive again what you should do.
closing with reference to external testing
closing with reference to external testing
closing with reference to external testing
closing with reference to external testing
closing with reference to external testing
closing with reference to external testing
closing with reference to external testing
closing with reference to external testing
closing with reference to external testing