Hej thinks that she would expect the dialog to show which certificates were uploaded.
I think if we want to do that, we should make a new ticket for it. Here we wanted the easy quick fix.

Tooltip: Save this secret key to share with other team members.
dt. Menüeintrag: Geheimen Team-Schlüssel speichern
Tooltip: Geheimen Schlüssel speichern und mit Team teilen.

Werner strongly prefers to include it in the self-tests instead of adding a command to the drop-down list.
I will therefore update the description accordingly.

I forgot the differentiation between singular and plural…
Maybe "Upload successful" would be enough.

Well it kind of works but it is a bit ugly and the encoding in the "Encrypt" message is broken:

Note that screenshot was made with a gpg from the 2.2 branch.
And on a Windows VM which was (I'm quite sure) installed in German from the start.
In case it matters…

You cannot trust any signatures made with a compromised key because the signature creation date can easily be forged.

In T6869#200687, @ikloecker wrote:

Most of the texts (most are proper sentences) lack a full stop. It's unclear whether this is a bug in the German translation or also in the original texts. This should be fixed.

One thing: The message for the valid signature from a revoked key looks less worrisome from the user perspective as an invalid signature. Is this intended?
One does not see here if the signature was made before or after the revocation. In the latter case the signature can not be trusted for sure. In the first case it might be ok.

yes please!

We decided to

@TobiasFella: please ping on screenshot in MR

This issue does not occur on master, only on 2.2 and 2.4 branches.

There was another customer wish for this, RT #34722

Fixed:

turned out that not the flowcrypt encryption is the issue here. The cause seems to be the usage of Proofpoint "Email Warning Tags".

regarding the 403: one has to try the correct page AFAIK. Didn't research which one, look in the update checker code.

This is resolved in the final Beta15.

Forgot a screenshot:

Yes. I did only one test though, with an inline PGP mail sent with Claws.

https://flowcrypt.com/
They use OpenPGP.js according to https://flowcrypt.com/docs/getting-started/overview/openpgp-compatibility.html
They have a cooperation with Google.

this exact case is fixed in VS-Desktop-3.3.90.12-Beta
Adding further UIDs and making more certifications still works, too.

yeah, I did not have exactly the same setting for the tests in the different versions… so no regression

turns out that this seems to be a timing issue/race condition and disappears if more debug output is added

Well, I could not reproduce this at any time but tested decryption with long file paths to be sure nothing broke and it worked fine.

with VSD-Beta-3.3.90.10:

With VS-Desktop-3.3.90.6-Beta:

this is not yet in master and not included in the current testbulid

My above comment is true for the main case described in the ticket, cancelling decryption followed by "permanently decrypt".

I see no improvement in VSD-Beta-3.3.90.6, the issue persists.
Btw: Is this maybe related to T7596: GpgOL: Draft is not decrypted after cancelling decryption once?

After further testing:
The new level 3 icon is shown for most test cases. This ticket here is only for the new icon, therefore I'm setting this to done. I'll make a new ticket for the cases where the level is not detected correctly.

with Version VS-Desktop-3.3.90.6-Beta: