Kleopatra now shows:

works in 22, too (tested with VS-Desktop-3.2.0.0-beta214)

Does not work yet on VS-Desktop-3.2.0.0-beta214:

Tested in VS-Desktop-3.2.0.0-beta214 by encrypting a large file with Kleopatra. The progress bar shows percentage finished, progress looks all right

I've added a footnote in the VSD user documentation regarding this difference as a very minimal measure and a reminder for support.

Re-open to add auto-detection.

Relevant lines from Arch's qconfig.pri:

QT.global.enabled_features = shared pkg-config rpath reduce_relocations signaling_nan zstd thread future concurrent dbus openssl-linked opensslv30 shared shared rpath reduce_exports no_direct_extern_access reduce_relocations openssl
QT.global.disabled_features = static cross_compile debug_and_release separate_debug_info appstore-compliant simulator_and_device force_asserts framework c++20 c++2a c++2b c++2b wasm-simd128 wasm-exceptions opensslv11
QT.global.disabled_features += release build_all
QT_CONFIG += shared rpath reduce_exports no_direct_extern_access reduce_relocations openssl release
CONFIG +=  shared plugin_manifest

Per IRC discussion, this could be autodetected in qt6.m4 by querying Qt6Platform.pc for mkspecsdir and grepping ${mkspecsdir}/qconfig.pri for QT_CONFIG.*no_direct_extern_access.

Thank you very much, we will try it and let you know
Regards
Lukas

I have added the additional suffixes. And I have added a patch to gpg4win which makes the fix work on Windows.

Not sure yes If I rather fix this or do: T6331

No need for QA on build issues.

In T6725#175868, @ikloecker wrote:

No. Windows has a file selection dialog where you can only select files and a folder selection dialog where you can only select folders. We cannot change Windows (and we will not use a non-native file dialog).

This is a release blocker for me.

Ingo can you investigate? This is very important because this is a regression caused by the change to pass filenames directly. I wonder if we pass this as UTF-8 and gpgtar needs a fix or if we pass it somehow else.

The Qt 6 bindings will now be compiled with the -mno-direct-extern-access flag if --enable-no-direct-extern-access is passed to configure.

Fixed by ingo

Could we then clarify this for the user somehow? Maybe both
a) add "Sign/Encrypt Folder" to the default menu bar - it would need an icon added for that, too
b) make it clear in the documentation

In T6696#175866, @antonio-rojas wrote:

This is a Qt issue. Reported at https://bugreports.qt.io/browse/QTBUG-117398

Sure. That's why I wrote that my fix needs to be checked on Windows. And if the regression T6726 wouldn't have blocked the test of my local fix for Windows, ....

No. Windows has a file selection dialog where you can only select files and a folder selection dialog where you can only select folders. We cannot change Windows (and we will not use a non-native file dialog).

This is a Qt issue. Reported at https://bugreports.qt.io/browse/QTBUG-117398

There has been another report on the Gpg4win Forum which might be related that mails now cause endless syncs and might even break further when they are saved back to the same exchange server as there is no MAPI to MIME conversion done anymore and other clients cannot read the mime structure.

For clarification: encrypting a file via Kleopatra (not GpgEX) with unicode characters in name works, only the folders don't

As eva wrote the problem is that if you decrypt only the archive and not immediately extract it, which is an option for our users this results in a broken extension. And it also looks wrong even at first glance so it does not look like we intended this. Also wouldn't we then need mime types for the tar.p7m tar.p7s, too and tar.pgp?

I'm using the standard pinentry provided by Homebrew: https://formulae.brew.sh/formula/pinentry#default

This is a serious regression.

This is as intended, in Kleopatra you either encrypt files or folders (via File-> Sign/Encrypt Folder).

gpg -v -K does not require a pinentry. You can check this by adding debug-pinentry and log-file /some/file to the gpg-agent.conf - you should not see any pinentry invocation.