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
closing and opening new tasks is the best option
Mar 15 2023
works. tested with VSD 3.1.26 (gpg 2.2.41) and keyserver entry in dirmngr.conf only.
works, server can be added to dirmngr.conf via kleopatra
works with AD, too. Even with an "a" ;-)
Yes, the installation was with the unmodified Installer GnuPG-VS-Desktop-3.1.26.0-Standard.msi
Mar 14 2023
Mar 13 2023
Mar 10 2023
works
It effects Yubikeys and ZeitControl cards (version 3.4)
We got a user report that the issue did not occur before their update from 3.1.25 to 3.1.26
Mar 6 2023
Mar 2 2023
Feb 22 2023
works if you use a valid IP address
Feb 17 2023
well, this user made a backup and it went wrong anyway ;-) See T6377
I'm sorry, I got a bit confused, it works in Kleopatra on 3.2.0, but not in 3.2.26
Feb 16 2023
Feb 8 2023
Jan 26 2023
Jan 19 2023
Dec 15 2022
works
Dec 13 2022
works
works: the process is canceled without any notification.
works
Dec 8 2022
With GnuPG VSD 3.1.25 the Certify action is not disabled for me. Neither on Windows nor on Linux system.
Dec 7 2022
Dec 6 2022
works
I would ideally like a result message like "Could not connect to keyserver ks.example.org" if the server is not reachable and
"the key has not changed on keyserver ks.example.org" or "the key could not be found on keyserver ks.example.org" if one of those is true.
At least the last two not if the key was found via wkd, obviously, in that case a similar message for wkd.
