That is a feature not a bug. Make also sense if your threat model is store-trafic-no-decrypt-later. If you can get the key you will also be abale to get the cleartext. Any nobody can remember a passphrase on par with the claimed Kyber security level.

yes, it seems to be caused by one of the patches. I'm trying to figure out which one...

Or Window activity (which is related to focus). I'm wondering if one of my patches is to blame.

I can reproduce. It's not that the Button itself needs to be pressed twice, *something* in the dialog needs to be pressed before the button reacts. So this looks like it's something about focus

I wonder if we should better open a new ticket with all the relevant data when we get a report giving more information and set this one to invalid.

And meanwhile I have tested this a bit with VSD3.3.3 and in the case that the sender has a valid and *VS-compliant* key the automatic switching works.

I think Gpg4win will keep the language switch because for Gpg4win we don't disable any actions via action restrictions (as far as I know).

In T6568#208875, @timegrid wrote:

• Column sort order and visibility can be configured only via view and nowhere else. That's how it should be, right?

What do you mean?

The description says: The selection of visible columns and sorting should be possible **additionally** via the main menu.
I just wanted to make sure, "additionally" means additionally to the normal (non a11n accessible) context menu and not some other (a11n accessible) place i haven't found.

The preference option does already exist, it is "Prefer S/MIME". If not set (the default), then OpenPGP keys are preferred.

I'd prefer the language switch for testing, but I mostly had tests for translation issues in mind, e.g. wrong translation language, tooltip size in some language - which probably should be covered by setting the language via the envvar. I'll do some tests to see, if this would work.

• Column sort order and visibility can be configured only via view and nowhere else. That's how it should be, right?

What do you mean?

Yes, very likely it was with NVDA's (update) installer. Therefore I looked at NVDA's source code to find out how to make it work for Kleopatra just to find out that NVDA fakes it itself. I would close this ticket as won't fix.

In T7949#208870, @timegrid wrote:

Regarding the tests: Being able to set the language for Kleopatra via some environment variable would be fine, too.

Ah, I see. I heard the continuous beeps with another pitch once (probably in the installer then) and thought this was possible. Shall I set this to won't fix then?

In T6568#208750, @timegrid wrote:

Questions:

• Column sort order and visibility can be configured only via view and nowhere else. That's how it should be, right?

Regarding the tests: Being able to set the language for Kleopatra via some environment variable would be fine, too.

Separate ticket for the "initial language selection": https://dev.gnupg.org/T7949

The 50 % is when either WKD lookup or keyserver lookup are done and the other is still running. None of those two lookups can be partially done. Hence there's no way to do something with more steps (safe for faking it with a timer). The only alternative is an unspecified progress bar, but unspecified progress bars (aka busy indicators) are completely silent as you can see in the "Loading certificate cache..." busy indicator. (NVDA's code doesn't support unspecified progress except in their own installer which has special code for this, i.e. the installer makes the sound itself.)

This isn't a Kleopatra issue. I suppose this happens with Outlook. The security confirmation checks for the type of keys it's asked for. Either OpenPGP or S/MIME or unspecified.

This isn't reproducible on Linux. (Tested with a Yubikey but that should really make no difference.) Maybe a regression of our Qt patches.

Please create a separate ticket for "The initial language in kleopatra is not selected according to windows settings". This is a bug in KDE Frameworks that's orthogonal to the issues of this ticket.

Best test this with a newer installer than gpg4win-5.0.0-beta413 to avoid the regression with the raw HTML (see T7886#208675).

The problem with the raw HTML has been fixed already by Tobias.

Yes, sorry, a typo, I corrected it.

In T7759#208677, @timegrid wrote:

Forgot to note: Setting S/MIME debug level in kleopatra via GnuPG System will write the right key to gpg.conf (if I understood it right, this was also a problem)

git checkout gnupg-2.5.14, reverted the commits 46f4cb66125ee34e87e592cc02d38daead3427af and 0cc7759ed5a3890b4e28563a6b5e97f3aa551530, recompiled, and the error message gpg: keydb_search_first failed: SQL error no longer appeared. Also, in /root/.gnupg/public-keys.d/, the two files pubring.db.lock and .#lk0x0000... are present.

Looks good to me on gpg4win-5.0.0-beta413 @ win11.

I also tried to check all tables i can find and it mostly looks good:

• Certificates Lists:
  • Main
  • Import ("Show imported")
  • Cert Selection (e.g. Sign as)
  • Keyserver Lookup
  • Smartcard
  • Groups (both available and in group)
• Certificate Details
  • User IDs
  • Sub-keys
  • Certifications

Looks good to me on gpg4win-5.0.0-beta413 @ win11

Actually pinentry has the same behaviour, so this might be a general problem, if one form input field is changed.
It also applies to clicking on other form elements.

As this looks good to me on gpg4win-5.0.0-beta413 @ win11, I move this to done on the gpd5x board.

Looks good to me on gpg4win-5.0.0-beta413 @ win11:

Looks good to me on gpg4win-5.0.0-beta413 @ win11

Looks good to me on gpg4win-5.0.0-beta413 @ win11

Looks good to me on gpg4win-5.0.0-beta413 @ win11.

Looks good to me on gpg4win-5.0.0-beta413 @ win11:

Looks good to me on gpg4win-5.0.0-beta413 @ win11

Looks good to me on gpg4win-5.0.0-beta413 @ win11

Looks good to me on vsd-3.3.3-beta90.32 @ win10.

Looks good to me on gpg4win-5.0.0-beta413 @ win11: The option is removed in the S/MIME tab.

Note: Backup/Restore secret kyber keys looks good to me on gpg4win-5.0.0-beta413 @ win11 now.

Looks good to me on gpg4win-5.0.0-beta413 @ win11.
The error message in debugview is gone.

Looks good to me on gpg4win-5.0.0-beta413 @ win11:

Tested on gpg4win-5.0.0-beta413 @ win11

Looks good to me on gpg4win-5.0.0-beta413 @ win11.

Looks good to me on gpg4win-5.0.0-beta413 @ win11:

Looks good to me on gpg4win-5.0.0-beta413 @ win11.

Looks good to me on gpg4win-5.0.0-beta413 @ win11:

• Email/Name
  
• Name
  
• Email
  

Forgot to note: Setting S/MIME debug level in kleopatra via GnuPG System will write the right key to gpg.conf (if I understood it right, this was also a problem)

On gpg4win-5.0.0-beta413 @ win11

• The diagnostics button is displayed
• The message contains a hint to adsk
  

Looks good to me on gpg4win-5.0.0-beta413 @ win11

Still needs to be tested on VSD 3.4.

Looks good to me on gpg4win-5.0.0-beta413 @ win11

Looks good to me on gpg4win-5.0.0-beta413 @ win11

I think last time I didn't test the actual problem.

Looks good to me on gpg4win-5.0.0-beta413 @ win11

When --output option is used and the user uses temporary file and is ready for checking an error, that is, it's already prepared, it's redundant and useless, indeed.