this is 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.