Tooltip: Save this secret key to share with other team members.
dt. Menüeintrag: Geheimen Team-Schlüssel speichern
Tooltip: Geheimen Schlüssel speichern und mit Team teilen.

Werner strongly prefers to include it in the self-tests instead of adding a command to the drop-down list.
I will therefore update the description accordingly.

Meanwhile we have some support for an empty subject but gpgsm still prints an error notice. See the T7171 for more.

Included in 1.11.1.

engl. Menu Entry: Save Secret Team Key
Tooltip: Save this secret key to share with other team members.

Discussion and background for naming things and german translation

For the icon:

We decided to

A brief update: This feature has not made it onto the roadmap of specific things to implement so far.

There was another customer wish for this, RT #34722

BTW, fingerprints for X.509 are not well defined because you get a different one when changing the *unsigned" attributes. Not a common case but one should be aware of it.

regarding the 403: one has to try the correct page AFAIK. Didn't research which one, look in the update checker code.

In any case, the actual connectivity test needs to be performed by GnuPG. Otherwise we might just test whether the Qt/KDE libraries can reach versions.gnupg.org, but not whether dirmngr can. Werner proposed something like gpg --fetch-key https://gnupg.org/index.html.

this is not yet in master and not included in the current testbulid

We have done all of this and the rest of the work is now in T7593

Hey there. I wanted to bring this up again, to see if we can perhaps get this changed after all:

BTW, do we really need a C++ API for this? Might make sense due to the need for a context.

Well I finally did some more tracing and removeOurAttachments_o is not called when the attachments vanish.

5.0Beta:145: OK and works, both for signing and encryption

Please grey out the "Anyone …" sentence, too.

The option is available now and it works:

If RestorePositionForNextInstance=false is still there after gpgpass has been quit then either KMainWindow::closeEvent() didn't run or the dirty state config wasn't sync'd to disk. When reading the code in KMainWindow I was wondering if a sync() was missing, but in Kleopatra it worked without this.

Version 4.0.0.250370 (Gpg4win-5.0.0-beta125):

After testing the feature again with Beta 5.0.0-125 I repeat myself: this works.
There is the action "Unblock card" for unblocking the card with the rest code / PUK.

New API gpgme_op_random_bytes is now in master (gpgme 2.0). Use tests/run-genrandom --help for testing. Extra features will come soon.

VSD 3.3.0: OK.

ok in VSD 3.3.0, too

Removed in https://invent.kde.org/pim/kleopatra/-/merge_requests/369

We do support "Decrypt & Verify" for multiple files (including the presentation of the status) so that it would be easy to do the same for all files in a folder (question is if this should even be recursive). Digging into the history I found that the desktop file was added shortly before Kleopatra 2.0.0-rc1, but that there wasn't any code for iterating a folder, i.e. this can never have worked.

As I am delving a bit into cryptocurrencies and since i have a ledger security token and a bip32 24 word mnemonic now backed up as stamped metal i have stumbled accross this topic:

I'm glad that inotify is already in use, that's a reasonable thing on the Linux platform.

This is the old code from gnupg-2.0/agent/gpg-agent.c:

inotify is already used used on Linux to check for a lost homedir. The once-in-a-minute check should be the same as with the other daemons and has proved to be very useful. The whole thing has been discussed over and over again a long time ago and - as with other system daemon - we agreed on scheduling at the full second.

I think there's some confusion.

changed the workboard to gpd5x as this is still the case in Gpg4win 5.0-Beta versions.

Gpg4win-5.0.0-beta32
Works!

Ok, then this will not be included in the VSD versions until we switch away from gpg 2.2

21f7ad563d9b was not backported to gnupg 2.2, so this can't be done yet

It's missing a check for the required gpg-2.2 version. I will add that

If you encounter real world certificates with these parameters we can bump up the priority.

In VS-Desktop-3.2.94.481-Beta the feature is not available in the context menu in Kleopatra.
So in VSD 3.3.0 this will be missing. What works is disable/enable on the command line and Kleopatra will then not list a disabled certificate with most filters.

I think I can understand you, too much complexity.

See this comment which is related to T4538:

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.

Thinking about this some more, i came up with some more ways of showing some nice-to-have information in the tooltips:

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

Fixed in 2.5.2.

it would be best to add an API to gpgrt to iterate over registry entries.