Details
Fri, Jan 17
Hm, "Names for the certificate" seems wrong to me. Shouldn't it better be "Names in the User IDs [of this certificate]"? I would leave of the part in [] as redundant. Likewise for the mail addresses.
Thu, Jan 16
Thinking about this some more, i came up with some more ways of showing some nice-to-have information in the tooltips:
works with VS-Desktop-3.2.94.481-Beta
works in VS-Desktop-3.2.94.481-Beta. The "Trust Root Certificate" is no longer offered in the context menu.
works in VS-Desktop-3.2.94.481-Beta
Mon, Jan 13
"Tested" with VSD-beta-478, looks as expected
works with VSD-beta-478
Works fine in VSD-beta-478
Fri, Jan 10
https://invent.kde.org/pim/kleopatra/-/merge_requests/355 makes both components use the same tooltips; we can then change both when we decide on what exactly to show in the tooltips in general
Thu, Jan 9
Yeah, I guess we can word this a bit less spec-like. It has more or less the same purpose as an admin PIN except that it's a 128 (?) bit key. And, if I understand correctly, it can also be used by the (admin) user to make sure they are talking to the correct card (if all cards are provisioned with unique keys). Kleopatra automatically tries to authenticate with the standard key so that we never see the prompt for the key unless we have changed it.
Wed, Jan 8
The additional changes were also backported for VSD 3.3
Backported for VSD 3.3
There's a different (but very similar) bug here for RSA keys; fixed in https://invent.kde.org/pim/libkleo/-/merge_requests/177
Maybe the title should be "Password - Kleopatra" (or similar) if the operation was triggered by Kleopatra.
We noticed in the above mentioned ticket, that this needs to be backported
Tue, Jan 7
as far as I understand both the Gtk and Qt implementation are using pinentry_get_title which does the /proc stuff, but this is only on Linux. On Windows, pinentry_get_title will return the value set in pinentry_init, in our case pineentry-qt or pineentry-qt5.
Check out the GTK version which scans /proc for the process to find the command line. Very handy for ssh sessions.
I can still reproduce the issue with VSD beta 478
Backported for VSD 3.3