After talking with Werner, I edited T7155 to include displaying the protocol column, too, because this is useful in combination with his wishes regarding the origin keyword which are:
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jun 17 2024
Jun 14 2024
Looking only at the text used, you get exactly the same messages used for single certificate updates, "The certificate has been updated" or "The certificate was not found.", both in the singular.
And "But "Update certificate" does still not query WKD (not even after restarting Kleopatra.)" seems to happen because the setting "Query certificate directories of providers for all user IDs" wasn't enabled.
Tested with Gpg4win-4.3.2-beta25:
Ok, follow up for the column is T7155.
Jun 13 2024
Tested with Gpg4win-4.3.2-beta25:
For Gpg4win-4.3.2-beta25: Compendium is now listed before "More documentation".
I'd say "PIN counters:" is enough in combination with a tool tip. An additional documentation in a manual is always nice, of course. But do we really need the "PIN" here? As long as after the colon PIN, PUK, etc is listed, I think we could drop it here and say "Retry counters"
One could also contemplate using something like "No. of tries left".
Should I make a new ticket for making the origin column default for the search?
This depends on what this ticket was intended to cover.
I always see the tags in the main certificate view in VSD 2.2 as well as the current Gpg4win-4.3.2-beta25.
Jun 11 2024
Tested with Gpg4win-4.3.2-beta25
Noticed when looking at the MR that there seems to be no error handling for the case that no ADSK is configured (or something is wrong with the configuration). At least I did not see any strings informing the user about an error.
Jun 10 2024
Tested with 2025-05_gpg4win_Beta_23:
- "no certificates found" message shows as expected
- "Searching for matching certificates ..." is shown while searching
- Aborting search in the progress window works
Jun 6 2024
Tested with Gpg4win-4.3.2-beta23: This works if I select the origin column for display. At least for WKD and keyserver.
Tested with Gpg4win-4.3.2-beta23:
Tested in Qt 5 build Gpg4win-4.3.2-beta23: Configuration dialog looks good.
Qt6 was tested by the developers
Jun 5 2024
While I was about it, I also moved the compendium entry above the "More Documentation" entry.
works, tested with Gpg4win-4.3.2-beta23
Jun 4 2024
works, tested with Gpg4win-4.3.2-beta23
Jun 3 2024
May 27 2024
May 24 2024
May 23 2024
I've moved the gpg task to a new ticket, T7133: Add feature to load designated revoker from LDAP
The Kleopatra task is obsolete, as it was noticed that the proposed option is already in gpg and should not be implemented twice.
May 21 2024
I assume you only implement this for encryption and not decryption. The latter should always be possible.
May 17 2024
Tested with VS-Desktop-3.2.93.391-Beta:
Does not work on windows at all. Seems it doesn't any more on Linux, either (info Tobias)
works, VS-Desktop-3.2.93.391-Beta
works, VS-Desktop-3.2.93.391-Beta
ok, its even on by default, VS-Desktop-3.2.93.391-Beta
tested with VS-Desktop-3.2.93.391-Beta, looks ok.
May 15 2024
May 10 2024
May 8 2024
Go ahead and split it of, then. And setting a key to disabled in Kleopatra itself is not that urgent that it has to be in vsd33.
May 6 2024
May 3 2024
What is the status here? Werners opinion is that only the kleopatragroupsrc needs to be migrated.