search for "example" works now, Gpg4win-Beta-50

Okay, okay: s/private key/secret key/

The test with Gpg4win 4.3.1 (using GnuPG 2.4) seems to indicate that:

1. gpg didn't update the trustdb automatically after importing the extended trusted certificate.
2. gpg updated the trustdb automatically after deleting and re-importing the expired trusted certificate, but Kleopatra still showed the certificates signed by the trusted certificate as "certified". This could be a bug in the trustdb calculation (note the log message "Schlüssel C5D6C919005F36A4 ist als ultimativ vertrauenswürdig gekennzeichnet" which could indicate that gpg treats the key as valid although it's expired). On the other hand, my test with GnuPG 2.4 on Linux doesn't reproduce this problem.

And I can replicate it with the Appimage for VSD 3.2.2, too.

The issue is the same on import on the command line. So it's a gpg issue.

This was implemented by Tobias

Backported the changes in Kleopatra for VSD 3.3.

Since VSD 3.3 will likely include this change in gpgme I add the vsd33 tag.

Backported for VSD 3.3

Works fine.
For special DOS names only COM/LPT1-9 are supported names like COM12 are not handled.
But that is not really an issue as these names are always prepended with the temp-pathname and c:\tmp\COM12 are valid names.

Backported for VSD 3.3

Implemented in https://invent.kde.org/pim/libkleo/-/merge_requests/132 and https://invent.kde.org/pim/kleopatra/-/merge_requests/277

Backported for VSD 3.3

Everything has been backported for VSD 3.3

I consider this done. I suggest to open follow-up tickets for further changes.

Backported for VSD 3.3

Backported for VSD 3.3

Backported for VSD 3.3

I have opened T7268: Kleopatra: Existing groups are not saved after editing them for the issue that was found while testing this ticket. The issue is a regression caused by changes made for T7233: Kleopatra: Certificate details dialog non-interactible when opened from group edit dialog.

Backported for VSD 3.3

Fixed.

Copying the file to the new location works as proposed in the description, tested with update from 3.2.2 to VS-Desktop-3.2.93.33-Beta

In Debugview I see, after only opening the group configuration dialog:

Migrating kleopatragroupsrc to new location worked for update 3.2.2.0 to VS-Desktop-3.2.93.33-Beta on Windows.
kleopatragoupsrc in old location is not deleted, but a copy is written to %APPDATA%/gnupg/kleopatra

Tested with VS-Desktop-3.2.93.33-Beta, works!

Tested with VS-Desktop-3.2.93.33-Beta:

Tested with VS-Desktop-3.2.93.33-Beta, where everything necessary is backported:

Should also work in VSD 3.3

Should work (if correct path is set in qt.conf).

The Down button should be disabled if no suitable certificates are selected. That may not be the case (in Qt 5) because Qt seems to add disabled rows to the selection and the work around is applied when the Down button is pressed.

Without administrator rights it does not work for me, since it then cannot write to %PROGRAMDATA% to install the VS-NfD mode config files. But the only thing for "does not work anyway" that I know and could quickly see is that "IPC connect call failed" problem with GPGEX (which we are planning to remove / replace anyway). So I don't think it is very important to remove this and addtionally we do not know if this is something that is used, we have offered it from the beginning but have no data if our customers use it. We can suspect that we would have seen more support questions about the gpgex error if it was widely used. But I always thought that the "only for me" installation option was useful for some use cases.

I think the executables also use the same values for translation.

works in VS-Desktop-3.2.93.33-Beta

I wouldn't hide the table. We don't hide any tables (e.g. also in smart card view) if they are empty. I would resize ones on very first show (if restoreColumnLayout() returns false). This fixes the initially cut column titles. And then I'd resize to content when the search results are shown, but also only the very first time (i.e. we'd need to remember the first show).

Okay, I see now that this is US-English and Unicode.

Okay. let me do that for the next library releases.

afaik "Valid Until" is actually available for keys coming from WKD

• The status column is already removed in the gpg4win branch but not yet in the test version
• afaik "Valid Until" is actually available for keys coming from WKD
• For the column widths, we could hide the table until the initial search results come in and then resize to content, or just always resize to content when results come in

Looking at why this isn't working correctly, my understanding is that we need to do very specific things to make this work on windows at all, see https://doc.qt.io/qt-6/qwindowsmimeconverter.html and https://doc.qt.io/qt-5/qwinmime.html (which i did not realize before yesterday). Since this would require spending probably a few days on this (and writing different code for qt5 and qt6, unfortunately), I'm proposing to remove this from the release and postponing the implementation for Qt6 until after the next release

I went for the placeholder text because you asked what should be shown on error. And I would rather not follow your suggestion and show an empty widget but keep the placeholder text then.

I like it. BTW, even the unblocking should not be easy to access because users will anyway enter the wrong PUK and then the card is bricked (ready for a factory reset).

NetKey card widget with Card Actions button (because pictures say more than words)

This is way too much text, people. And changing the placeholder widget wasn't part of the original description. Please create a new ticket for this.

In T7018#190062, @ebo wrote:

Suggestion for the "placeholder" screen:
Only show "Please insert a compatible smartcard." And then below: "Known supported smartcards are listed at https://gnupg.com/kb/smartcards.html".

Suggestion for the "placeholder" screen:
Only show "Please insert a compatible smartcard." And then below: "Known supported smartcards are listed at https://gnupg.com/kb/smartcards.html".

Mh, in the past I would have thought that drag & drop might be worth it for the use case of browsers where you sometimes need to have your key as a text representation. That was originally the Use Case that stood behind the "Text export" in Kleopatra -> Details -> Export. But nowadays I feel that every text box I write into in browsers somehow supports also to drag a file in there for uploading. Or related I sometimes paste image data directly to phabricator and it is attached as a file. And if browsers can handle that, maybe we are even better suited if we would just export it as application/pgp-keys ? But I can't really specify that as I would develop this myself by trying some mime types on windows and see how the relevant software -> Windows Explorer, Outlook, Browser and maybe some other Office software handles that mime type.

inserted as a text block and not as a file attachment

I tested it doesnt seem to work reliably on windows, it always exports into my home folder regardless of where I drag and drop in explorer or on the desktop window. The drop also seems to require an additional click while it usually works on windows on release and in Outlook it was inserted as a text block and not as a file attachment. Also, but that might be specific to the broken dev installation i have right now it seems to keep handles to the exported files open so I can't delete them or move them right after.

https://invent.kde.org/pim/kleopatra/-/merge_requests/272 and https://invent.kde.org/pim/libkleo/-/merge_requests/126

First: we should do something about the placeholder text, too. It is a bit misleading ("But it says Netkey cards work, why doesn't mine?"…)

Open:

• The lower left corner of the screen shows a spinner while scanning for smartcards. this changes to the number of found smartcards.

Screenshot of the "placeholder" screen while loading smart cards:

T7245 which fixes selection on multiple results has been backported for VSD 3.3

Backported additional changes for VSD 3.3

Backported for VSD 3.3

Backported for VSD 3.3

Backported for VSD 3.3

Backported for VSD 3.3

Backported for VSD 3.3

I'd say go it it.