For the Berta Key in the Testversion: *After* entering the Password for the signature, the new GpgOL message does show. When I choose "Retry" in spite of the warning, the mail is send out encrypted.
So I was only confused because I did expect another order of events. Something seems redundant and confusing here:
First you are shown the security confirmation dialog an click on OK (with the small warning sign and "not compliant" next to it), then you are asked for your password (if it is not in the cache) and then you get the new Warning message with the option to "Retry". Although you already in the first dialog chose to encrypt non-compliant.
Btw: The error message from gpg is for me not "end of file" instead it is: "Syntax error in URI"

If I repeat this with a totally empty keyring, I get the new message regarding the missing signing certificate.

With this certificate I do get the security confirmation dialog without "always show" on, but still no new message box.

Without "always show" I get a pinentry immediately after hitting "Send". So no warning.

I realized that I still had "always show confirmation dialog" on... When I turn that off I get the default error message, but with encoding errors:

I do not see the default error message, not even with a new, totally empty keyring.
I immediately get:

I had a look at the current state (VS-Desktop-3.2.0.0-beta229/231 from 2023-09-29):

again aheinecke:

aheinecke wrote regarding not showing the group at all (https://dev.gnupg.org/T6401#175847):

This is in contrast to the behavior for "single" keys. An expired key is not listed as available for encryption at all.

This looks nice! One down...

Yes, works now ( VS-Desktop-3.2.0.0-beta from today):

works, I only see the error in debugview.
Furthermore, I use the occasion to point to T6493, Improvements on search window ;-)

works: After generating a PIV key

gpg --edit-card

nevertheless shows the OpenPGP keys. Tested with gpg4win 4.2.0.

works as described

For me with Gpg4win 4.2.0 it works as expected, that is all UIDs which have a checkmark are certified in one go, entry of password only once. Used the key given in description for the test.

After the fix everything after the Signature block is now silently discarded

works

works

works

works, VS-Desktop-3.2.0.0-beta214

This is NOT the bug reporting form. You will find the form at https://dev.gnupg.org/maniphest/task/edit/form/5/

Edit: The text below was wrong. The error given below only occurs when the combined path+filenmae is to long on windows.
An emoticon in a file below the folder to be encrypted does not hinder encryption via GpgEX.

works, tested with VS-Desktop-3.2.0.0-beta214.
For the remaining issue with a certain date range see T6736

The choice in the calendar "widget" changed to in 1/2/3 years in all cases. Those options work but the last choice "no date" has no effect.

Works, setting "compatibility-flags vsd-allow-ocb" in the gpg.conf causes new keys to be generated with the AEAD feature flag OCB. And encryption to that key then uses OCB mode as long as the compatibility-flags is set.

This works insofar that it is now possible to set "none" (via the registry in VSD):

Encryption to the ADSK seems to work but I'm not sure if everything is displayed as expected.

How about adding "-2" to a document where before _signed already was in the name, i.e. foo_signed.pdf -> foo_signed-2.pdf and so on: foo_signed-3.pdf, ...

works with VS-Desktop-3.2.0.0-beta214, too.
You are now informed that you do not have permissions to write there.

For VS-Desktop-3.2.0.0-beta214 this does not work yet. If a keystub exists, it is not overwritten.

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.

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

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

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

Tested on the command line with

• a previously valid certificate after setting its root certificate to untrusted
• a expired certificate without the root certificate in the certificate list

With Gpg4win-4.2.1-beta31 I can no longer import the secret part of the edward.tester@demo.gnupg.com.p12 Testkey. Error is "Invalid object".

With VS-Desktop-3.2.0.0-beta214 and Gpg4win-4.2.1-beta31 the error is "Bad Passphrase" in this case.
I do not see a reason why this ticket is still open.
The already resolved Kleopatra Task T5713 is probably a duplicate of this one.

pkcs12 import should be backported, too

andre said this can not be left like this, on windows the name needs to be "Archive (1).tar.gpg", like in Linux.

In the VSD Testversion:

This did not fix the issue on Windows.

works

Yes the error message is better now. In German it is "Entschlüsseln fehlgeschlagen: Fehlerhafte Daten." Which could be a bit more clear, but its ok

well yes, it ends now in "_signiert.pdf" with German language settings and "_signed.pdf" in English.

ok, with the new testversion VS-Desktop-3.2.0.0-beta214 and without Debug redirection (mea culpa), the info window looks like this:

My issue was that it makes no sense to publish a revocation of a local certification...
I'm fine with it in the case if the certification was exportable.

this works now: