It is still there in VS-Desktop-3.2.1.0 insofar as 2 dirmngrs are started. It was only fixed insofar that it is no longer more than 2.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jan 12 2024
Jan 11 2024
Jan 10 2024
Jan 8 2024
Jan 5 2024
reopened. Because of reverted commits there is again no error message when trying to write to a write protected folder, see T6917.
moved to milestone 3.2.0, as 3.2.1 does not exist as column...
Works in VS-Desktop-3.1.91.9-Beta.
Jan 4 2024
Another hint: When they checked "write temporary files in the folder of the encrypted file" they got a message window from gpgex "Error returned by the GnuPG user interface: Input/output error".
Jan 3 2024
Dec 22 2023
Note for myself: This is the behavior for key resolving in GpgOL. GpgEX has different code for this and the above examples will not work.
In GpgEX the group is not resolved into its component keys currently.
Finally officially tested with Gpg4win-4.2.0 and a Yubikey 5 NFC. Works for both OpenPGP and PIV.
Tested with Gpg4win-4.2.0 and a Yubikey 5 NFC.
CSRs are generated for both available keytypes rsa2048 and nistp256.
Dec 19 2023
In T6891#180473, @aheinecke wrote:
Dec 15 2023
I saw this recently on a imap subfolder with between 4- and 5000 mails. I have marked a few hundred new ones as read in one go. The folder does not even have mail threads in it and I've never used that function anyway.
This was on my work account @gnupg.com (the only account where I use KMail). Should we ask Werner for details of the server?
Dec 12 2023
works with Gpg4win-4.2.0
Dec 11 2023
As it is so complicated to check all possibilities:
Dec 8 2023
Dec 7 2023
Dec 6 2023
This is not as intended. When doing a search, we wanted No error message and only WKD search should be executed.
Dec 5 2023
Nov 30 2023
This was already present in 3.1.26, where the error message was missing the output from gpgtar. So there was an improvement
Nov 29 2023
Nov 28 2023
Werner said it is ok
works with VS-Desktop-3.1.90.302-Beta, very nice!
Raising prio in reaction to some customer feedback
Nov 27 2023
When I do a search which is found on the keyserver, only the one without the multiple backslashes comes up, this seems to be started via gpgme call.
When starting again without a dirmngr and searching for a key which can only be found via WKD both entries appear in the taskmanager after only one search. The same is true if the key can be found in neither place. It seems the backslashes are associated with WKD and start is probably via gpgconf.
further improvement after the 3.2 release