Tested with Fedora 42 (which includes gpgme 1.24.3): this works now, you can drag a public or secret key from Kleopatra to a file manager to export the public key.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Aug 7 2025
Fixed and backported for VSD 3.4
Aug 6 2025
Solved by focusing the result message after the notepad operation is complete. I think that's an acceptable compromise for ensuring that users of assistive tools are informed about the result even if the focus is moved to a different UI element (which, in general, should be avoided because users can get lost).
Aug 5 2025
Finally came around to check this.
On Fedora with Kleopatra 25.04.03, gpg 2.4.5 and pinentry 1.3.1 the pinentry window ist above the Kleoaptra windows.
Aug 4 2025
The gold rule of tab order is that tab order follows the usual reading direction, i.e. line by line from left to right. If you press Enter after entering the password in the first input field then the focus should jump to the second input field.
That look s like a problems with logging to stderr in --server mode. On Windows fds 0,1,2 are special.
Looks good to me on gpg4win-5.0.0-beta357 @ win10 for the following migrations (as stated in the description):
- gpg4win 4.3.1 -> gpg4win 5.0
- gpg4win 4.4.1 -> gpg4win 5.0
Looks good to me on gpg4win-5.0.0-beta357 @ win10.
Looks good to me on gpg4win-5.0.0-beta357 @ win10:
The advantage of using a fingerprint for referencing a key is that there won't be any collisions in the keyid. Further this unifies the schema with an LDS (Windows) installation where DNs must anyway be unique. But take care the client needs to support this new flag. This will be the case for gnupg >= 2.5.12 (cf. T7756)
Do you have a gpgme log?
I created a new issue for the "Keine Daten" error: T7768
Looks good to me on gpg4win-5.0.0-beta357 @ win10
Looks good to me on gpg4win-5.0.0-beta357 @ win10:
1.11.2 has been release see T7642
Release done.