VS-Desktop-3.2.94.481-Beta: the option is removed in the Kleopatra settings and the tags are shown in the main certificate list as well as in the tabs of the certificate details.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jan 21 2025
Jan 20 2025
The Signature Card V2.0 is automatically loaded in VS-Desktop-3.2.94.481-Beta.
Other Telesec Cards, too, though this might take quite a while (e.g. the NetKey 3.0 card) and often a new reload is required.
VSD-Beta-481: Encrypting/signing with gpgtar on the cli and decrypting/verifying with Kleopatra works
I set this to resolved after a quick replay of the original report situation did not show any issue.
If it occurs again please reopen.
Jan 17 2025
In VSD Beta-481 the translation is missing
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.
Jan 16 2025
Thinking about this some more, i came up with some more ways of showing some nice-to-have information in the tooltips:
works in VS-Desktop-3.2.94.481-Beta
works with VS-Desktop-3.2.94.481-Beta
VS-Desktop-3.2.94.481-Beta: works, if no kleopatragroupsrc is found at the new location, the one at the old location is used.
This is only relevant in the case that after the update to this version GpgOL is used without starting Kleopatra in between.
Because when Kleopatra is started it will copy the kleopatragroupsrc from the old location to the new one. After that the config file in the old location is ignored.
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
works in VS-Desktop-3.2.94.481-Beta, the certificate for the newly generated key has the default expiry date of 3 years there.
Jan 14 2025
Tested with VSD-beta-478 and performance is fine
Jan 13 2025
Works with VSD-beta-478
Works with VSD-beta-478
I have seen this when doing the following:
Works with VSD-beta-478
Works with VSD-beta-478
works fine with VSD-beta-478
"Tested" with VSD-beta-478, looks as expected
Works with VSD-beta-478
Fixed. No backport needed because we use gpg4win-tools master also for VSD 3.3
@werner: gpg4win-tools needs to be updated in gpg4win master.
works with VSD-beta-478
works with VSD-beta-478
VSD-beta-478: works fine
Works fine in VSD-beta-478
Jan 10 2025
The file path of the group config file in line
https://dev.gnupg.org/source/g4wt/browse/master/src/resolver/resolver.cpp$171
has to be changed to the one in line
https://dev.gnupg.org/source/kleo/browse/master/src/kleopatraapplication.cpp$355 .
It may be best to add a function returning the default path to libkleo. Or to use the new path by default if no other path is passed to the c'tor of KeyGroupConfig. It's unfortunate that the path is GNUPGHOME/kleopatra/kleopatragroupsrc although the groups are also used by GpgOL and they should likely also be supported/used by KMail.
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
One year later, I also did translation work for kleo and libkleo, which are pushed by Andre.
So, closing this task.
Jan 9 2025
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.
Backported for VSD 3.3
Tested with the VSD beta 478. Works
Jan 8 2025
The additional changes were also backported for VSD 3.3