This change also avoids the accessibility problem (from the report) that tool tips close automatically if one moves the mouse cursor out of the tool tip.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Fri, Apr 5
Apr 4 2024
Apr 3 2024
Apr 2 2024
Note that the keys do not have origin information before they have been imported. My idea was to keep track of which job generated the results and somehow add this as origin information to the key list model.
Okay. 2342304000 in the colon output is 2044-03-23T00:00:00+00:00.
Yes, this ticket was made as a task to be completed for vsd33, so we left out the refinement you suggested on purpose.
As we are running as 32bit software on Windows, the "?" in the output below are a matter of course.
Since we can have multiple servers for S/MIME it could be nice in the search results to sow from which server the reply came. But I think that is out of scope or better a different issue since the current API does not provide that info.
Mar 28 2024
What does gpg -k / gpg -k --with-colons say?
yes, the box comes up, the second "user-level"-Kleopatra exits again after clicking the "ok" Button.
After quitting the Kleopatra process with the admin rights again the privileged background processes remain, like I mentioned in https://dev.gnupg.org/T7050#184583.
Yes, the kleopatra.exe process ist shut down for me with that version, too.
But I wonder if the remaining gpg-agent and scdaemon processes which remain may cause issues later on. The are still running with elevated rights according to the process explorer after restarting as normal user. It does not cause any immediately obvious issues, though.
No more additional dirmngr.exe processes come up in VS-Desktop-3.1.92.39-Beta, too.
Following your suggestion I have created T7067: Kleopatra: Add origin information in search results for the last open point
Note to self: The error message that nothing was found on the keyserver will still come up if one is configured. That will be fixed with T6493.
The certificates from the same test smart card work in Version 3.2.2.231170 (Gpg4win-4.3.1), too, but there all certificates are shown, that is one more than in the VSD version. Seems gpg2.4 can handle certificates which 2.2 does not accept. But that is nothing to complain about.
Mar 27 2024
Sure WKD is still checked if the conditions for an update via WKD are fulfilled.
It's not a different kind of data. In both cases it's the serial number of the smart card either in human readable form (often as printed on the smart card/USB token) or in "untranslated" raw form. It's a bit like short Git hash vs. full Git hash.
what about the case that the key has a mail address? Is WKD still checked?
works for latest VSD Beta, too (VS-Desktop-3.1.92.39-Beta)
looking at my private key directory, the data for the display serial number seems to not always be there FWIW.
While reviewing the changes I had some doubt about some of the columns.
In a current version I see this at least if I do not quit Kleopatra completely and restart to another screen setting. Further testing at the moment is not warranted, as there will be changes to the columns handling with the switch to Qt6. (T6924)
From your description it is not clear what you did exactly.
Mar 26 2024
Works for me using the latest vsd beta (3.1.92.39)
I think last time we talked about some generic solution for this. And ended up trying to research if we could add this in the end after linking is done to avoid having to patch/add an RC file for every library like GnuPG. Kleopatra and GpgOL already has one as you can see in windows with right click / properties and then details. Maybe we need to change the values there.
Mar 25 2024
I agree with the column save /restore but i disagree with adjust to contents since this can create a "jumpy" layout e.g. with long comments and the user might be annoyed if she changed thr layout and it is then automatically changed again
Mar 23 2024
Mar 22 2024
Done and backported for 3.2.
Sorry I just noticed that I mixed up the duplicate closing. I wanted to close 7050 as a duplicate of this and not the other way around. Since this description was more general and better.
Just to triage this
Mar 21 2024
More changes:
- If no certificates are found then an overlay "No certificates found" is shown on top of the certificate list.
- I have removed the confusing and unhelpful message "x certificates without name and mail address were ignored".
Fixed in master.
Mar 20 2024
Mar 19 2024
Changes so far:
- I have removed the error message that was shown when nothing was found on the OpenPGP key server. We don't show an error for S/MIME or WKD lookup. And I think the error message was just annoying. The user sees whether something was found.
- Kleopatra now shows a simple progress dialog with the text "Searching for matching certificates ..." and with up to 3 steps (for the up to three lookups). I don't think anybody (except testers) are interested in details where something is looked up.
Mar 18 2024
So, what is the state of this. Did a change already land in Kleopatra and how can we assure that all binaries have a W32INFO_PRODUCTNAME in their rc file?
Testing:
- Verify that T5359: Kleopatra: Loop in DeviceInfoWatcher with GnuPG 2.3 on Windows doesn't happen anymore.
- When you remove a smart card then Kleopatra should remove it from the smart card view.
- When you insert a smart card and then access it with gpg or gpg-card then Kleopatra should add the smart card to the smart card view.
Mar 15 2024
Mar 14 2024
Mar 13 2024
Mar 12 2024
Changes:
- The maximum allowed difference of the expiration between subkey and primary key is now +/-1 hour.
- If the user has no choice whether to update the subkeys together with the primary key (because either all subkeys will be skipped because they don't fulfil the conditions mentioned in the first comment or because the subkeys share the expiration of the primary key) then the checkbox is not shown. That was easier to implement and it doesn't confuse the users with a "choice" they are not allowed to change.
Done.
this should be easy since we already start gpg-agent on start