We now propose "<fingerprint>.rev" in the last used export directory as file name. This is the same file name as for the revocation certificates that gpg automatically writes to the openpgp-revocs.d folder when a new OpenPGP key is generated.

The SEGV was due to access to gpgme library after self.wrapped is set to None in the __del__ function.

The commit is: rMb2f224a471fe: python: Reset passphrase callback correctly..

Thank you for the patch. You are right.

I have kept a backup copy of a WKDRefreshJob locally. ;-) But that's stuff for a different task.

Thanks, the update button this is now more what I think is expected. Still I am not sure if removing it completely was neccessary, well we have it in the history now. Because I see the need to also update via WKD. Currently we only update from there if a key is expired but we would never see revocations. That is a problem that we will need some solution for at some point. But yeah in that case calling it "RefreshOpenPGPKeysJob" would be a misleading API Name anyhow. So its probably good that you removed it before the upcoming release.

Looks good. After entering a wrong passphrase three times Kleopatra now reports

Moving the key to the card failed: Bad passphrase

See T5903: Kleopatra: Add refresh button in certificatedetails for the corresponding Kleopatra task. Kleopatra now uses the good old ReceiveKeysJob for doing a key refresh from the configured key server. The RefreshOpenPGPKeysJob has been removed.

For an OpenPGP key, Update now performs a simple "retrieve key" operation for the existing key, i.e. it refreshes the key with the public key found on the configured key server.

@gniibe Perfect, I got the update during the night actually. Thanks a lot for your work 🙏 .

For the firmware 5.4.3, I confirmed that it works well with the changes:
https://dev.gnupg.org/T6070#160150

Did you restart Kleopatra after enabling the high contrast mode? I have implemented that Kleopatra doesn't change/set any background or foreground colors if high contrast mode is detected. Maybe the detection (in SystemInfo::isHighContrastModeActive) doesn't work.

All issues were addressed.

Hi lovely people,

Most things look good to me, it was automatically enabled when I switched Windows to high contrast mode. The only thing I noticed is that the fields where we explicitly set the background may not look to readable. Especially the Sign&Encrypt buttons because there we don't set the text color.

Fixed in 2.2 and master. Did a couple of manual tests using 2.2 on Linux. gpgsplit comes handy to add a couple more tag-3 packets (same algos or one patched to camellia for the negative test)

I have exactly this problem with yubikey here,
since i upgraded to gpg4win version 4.0.3 which contains gnupg 2.3.7 i get the same error as openpgp key not recognized.

The original issues have been addressed. Moreover, the actions are now available as buttons additionally to being available as context menu items.

@tigernero 2.3.8 is not yet released. Pretty sure gpg4win is a separate project, presumably you'll see a changelog entry here (as there is bumping to 2.3.7 in the latest 4.0.3) when it's in:
https://www.gpg4win.org/change-history.html
https://www.gpg4win.org/support.html

I can't find a url to download gnupg 2.3.8 for windows is it possible to know when gpg4win v.4.0.4 is out which fixes this bug? because currently on windows systems I am stuck using yubikey.

Fixed quite some time ago.

The table is now (more) accessible.

Fixed in master.

The table is now (more) accessible. The second issue doesn't apply anymore because of T6108: Kleopatra: Information on storage location of OpenPGP key should be per subkey.

I just confirmed that firmware 5.4.3 works fine with the changes (to be 2.2.37 and 2.3.8).

The fix has been merged to the 2.2 branch.

Should be much more accessible now. Only tested with orca which has its own quirks.

I have used the same header blurb as gpg-agent (https://dev.gnupg.org/source/gnupg/browse/master/agent/trustlist.c$60-73) with an additional comment about the include-default statement.

Kleopatra now silently ends the "backup secret key" operation if the password dialog was canceled.

I have improved the cursor positioning:

• Keep the cursor position when a key/group is updated in the background.
• Move the cursor to the start when the user finishes editing (with Return), selects a key/group via the selection dialog, or moves focus to another UI element.
• Otherwise, we keep the default behavior.

Fixed.

Does Yubico furnish you with devices for test...

Ready for testing.

Thanks @gniibe. Does Yubico furnish you with devices for test, or did you have to order that at your own/the project's expense?

Ready for testing.

Ready for testing. See https://dev.gnupg.org/T6073#160145.

It will be in 1.10.2.

It will be in 1.10.2.

It will be in 1.10.2.

Applied to 1.10.

I'm going to backport this to 2.2, as it found useful.

Pushed the change.

Lookups can now be started after entering a single character. Wildcards like * do not seem to be supported by OpenPGP key servers.

I have also improved the workflow when verifying detached signatures without corresponding signed file from Kleopatras UI in "non-automatic" mode, i.e. if "Automatically start operation based on input detection for decrypt/verify." is disabled in the settings.

Fixed. This was actually a regression introduced many years ago.

Ready for testing.

Thanks. Applied. Also, fixed about a warning for ChaCha20.

Here's another one related to this: https://lists.gnupg.org/pipermail/gcrypt-devel/2022-July/005344.html

Move from g10code to gpgcom, as discussed with Andre.

Applied and pushed.

Applied the changes to master.

We removed assuming "OPENPGP.3" means for ssh.

Having "Use-for-ssh" flag now, experience shows that including OpenPGP.3 keys by default is not convenient.

The general functionality should work now. I looked for labels showing links and converted most of them to HtmlLabel.

Text labels that get keyboard focus are now indicated with a focus frame. It depends on the Qt style how the focus frame looks like (or whether it is drawn at all). For the Breeze style, that is used on Linux systems, I have pushed a merge request (https://invent.kde.org/plasma/breeze/-/merge_requests/229). The necessary changes will be included in the next release of KDE Plasma.

ACK. P[ease add it also to 2.2.

What about rejected changes to "Key:"?

What about rejected changes to "Key:"? Other this command would make it too easy to mess up the actual private key.

Applied to 1.10 branch.