Ready for testing in VSD 3.3
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Today
How about changing the text after sentence two simply to:
Do we agree to drop bolt font for QES certificates?
Will we change this for VSD 3.4?
What about always using PEM for all generated CSRs? As far as I can see, gpgsm command line always uses PEM when generating CSRs.
Fri, Feb 20
Thu, Feb 19
Backported for VSD 3.4
For all tables where the visible columns can be configured via the context menu of the table header the visible columns can now also be configured via the context menu of the table cells/rows. (The only exception is the result table in the selftest where it doesn't really make sense to change the visible columns. Instead we should disable the context menu of the table header.)
Fri, Feb 13
Thu, Feb 12
Wed, Feb 11
Maybe we could show instead the text "No keyserver is configured."? Need not be in the same place. This would also be helpful in the other case, where you go to the search via "Lookup on Server".
Make all table column headings accessible (see Update 2025-10-27).
Forget my comment above. Or consider it as the "before" part of the task description…
Fixed and backported for VSD 3.4.
The settings should work again. They are described at https://docs.kde.org/trunk_kf6/en/kleopatra/kleopatra/admin.html#admin-certificate-request-wizard-keys , but note that the documentation is severely outdated. Note that those settings are not officially supported by GnuPG (VS-)Desktop (see https://gnupg.com/vsd/kleopatra-settings.html).
Tue, Feb 10
Fixed for KF6 versions.