Done. Will be tested with T5903: Kleopatra: Add refresh button in certificatedetails .

Importing certificates now raises the mainwindow the same way as previously "--import-certificates" would have done. To have it raised even before the job is started gives the widget a bit of a backdrop with the progress and result.

Ah and we should remove the help button in case the PDF Group config help is not available (e.g. on normal linux systems) because opening the kleopatra handbook does not make sense when there is no documentation about groups in there :)

Minor correction of the interface changes:

qt: toLogString                            NEW.

Yeah this is a know issue with kconfig, I ended up in many places in NeoChat and other apps to just call sync directly after every set because I'm often quitting apps with Ctrl+C and the settings were often not saved for me.

I am giving this wishlist priority for now.

For the record I tested it on Windows that this now saves the config when logging out.

No problem ;) Sorry for my snarky reply. Hope it worked for you now.

Noticed this issue was still open. This was resolved.

OK, I'm sorry, please accept my apologies for not having read the dialog message carefully enough. It seems I ignore the second sentence, replacing it with the omnipresent "Do you want to continue?" in my mind. Maybe the excuse is that it was terribly hot and damp in my office, preventing me from thinking.

We should not backport this to 2.2; better update to the current stable version (2.4)

Using Ubuntu, it's GnuPG 2.2 (which doesn't have the fix of T4585). Without the fix, killing gpg (by CTRL-C) causes problematic situation where pinentry remains asking.
That's because gpg-agent and pinentry don't know the frontend side has been killed. T4585 introduced a watching thread into gpg-agent, so that it can correctly detect lost of frontend.

I think that fixes the biggest issue here as long as kleo is not just killed it should save the current configuration state. Maybe we should add it in some more places explicitly, too where many things are stored in the config, like with the certifydialog?

😂 Skandal! Ein BUG!: "Möchten Sie die Installation ohne Administrator-Rechte fortfahren?" und Sie sagen "Nein". Ja dann brechen wir ab weil sie eben *nicht* fortfahren wollen.

Strong objection to close: When answering the question with "no", installation aborts!

Hi @gniibe - thanks for your fix.

Backport to VSD, as leaving out WKD is a bug.

result from meeting:

This could have something to do with our changes to g4wihelp.c to adapt to the new plugin API.

You can install Gpg4win without admin rights. It requests "Highest available" rights by default to be installed into the protected Program Files (x86) folder. When you are not in the Administrators group It will install into your home directory much like firefox does. Any maybe if you don't want to leave a footprint installing Gpg4win on the System (without admin rights) where you don't have admin rights is kind of beside the point. You either leave a footprint by the installation or you could just use the installed Gpg4win there.

Pushed the fix for SIGINT handling of pinentry-tty and pinentry-curses by: rPa6f63fe37dbf: tty,curses: Upon SIGINT, let pinentry exit gracefully.
This fix should improve the situation.

Thank you for the report.
I found a bug in pinentry-curses and pinentry-tty for handling SIGINT. I am going to fix this.

Pushed the change to:

• libgpg-error
• libassuan master
• libgcrypt master
• ntbtls
• npth
• libksba
• gpgme
• scute

Regarding PIN, they should be set first.

1. A temporary Admin / User PIN is be generated and stored in gpg-agent.
2. Then the keys are created as mentioned above.
3. The user is asked to set a new PIN and Admin PIN for the card.
4. Optionally set a RESET CODE

For generate new keys we see four use cases

1. Create card and backup card. -> Creates at least two cards with the same keys. Keys might be stored in ram: TODO: Add subtask
2. Full backup of all keys - Allows for copied cards at a later time.
3. Only backup encryption Key. - There is a backup of the encryption key on the computer.
4. No backup - Keys will be generated on the card.

Yes, gpgtar emits a SUCCESS status. gpgme should probably check for this.

[For bug reports please don't refer to some other site - at least a brief but useful description should always be included]

Yes i think we need something like that, maybe shorter like this message is (VS-NfD compliant) encrypted and this message was (VS-NfD compliant) signed by "user.name@foo.bar" as a single line each, with "Details" available. And then in details show some more information like who the message was also encrypted to, ideally with the user ids when we have the keys in the keyring already and not the fingerprints of the keys. Or maybe just a status indication icon like we have in GpgOL which provides more information when you click it or as a tooltip. At the very least we need to make sure that this cannot be faked by e.g. HTML Mails :) so it needs to be removed a bit from the actual mail body.