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.

Tobias can you add this please and extend libkleos DocAction so that it handles a web URL as an alternative to a file?. And takes an optional additional paramter for "show" which then depends not on weather or not the file exists but on something like "is_vsd()"

On Mac OS X 10.5.8, PPC Leopard, it built with the patch, gpg-agent works.

Please wait investigating it, a downgrade of the *kernel* from 6.8.2 to 6.8.1 helped. It seemed the USB communication got broken with 6.8.2. I am investigating

I rebooted, edited the scdaemon.conf to match the above, and tried gpg --edit-card with the yubikey plugged in. It resulted in the same output:

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.

For the reference, for now i just did the dummy install in the Fedora spec file:

Please use

Tobias, if you find some time, can you please see how this can be done.

Trying to reach Ralph Seichter via the eMail address he is using failed – Osterferien?

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.

ok, then I set this ticket to resolved, as it now works in version VS-Desktop-3.1.92.39-Beta as far as in Gpg4win.
That is only the "Refresh Keys" does not work yet. Which we now track in the above mentioned Tickets T7036 and T7037

Please keep also in mind that the OpenPGP card specification has always and is still developed along with GnuPG . Thus if there are any uncertainties in the specification GnuPG's way of handling thing is the way to go. If there is a way to chnage things without risking any breakage we can of course fix that. In all other cases we need to continue wit the current way. For larger changes in the spec we can of course cleanup stuff - Achim is currently reworking on a revision.

Thanks. I wonder if we should inform distros about this?

Please keep in mind, that it is not only about GnuPG and the OpenPGP card, but also between GnuPG and other PGP applications. I'm not really sure what the recent commit is doing, if it only affect the reading or also the writing of the data. But IMHO GnuPG should stick to the standard also if writing the KDF DO data because eventually, it will be used for authentication with the card.

Fixed in 24.02.2

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.

FYI as a VSD customer you have access to support. Please check Help-> about Kleopatra for the infos,