was fixed in gpgol 2.5.15

In light of the ticket T7630 this one is obsolete

We decided to

• remove the "Cancel" Button in case only one secret key is imported (as this does the same as "No")
• in case of importing more than one secret key we want to change the text from "Cancel" to "No for all".

When you've implemented the link solution here, do the same for T5006

Please solve this the same as our solution in T7630: add a button in the results window to open a new window with all the imported certificates.

Possibilities for the button text:
"Show import window"
"Show import tab" (I know it is no tab but its shorter)

After completion of T7553, the result for one file looks like this:

For illustration:

Checked with Gpg4win-4.4.1-beta59, too, which contains gpgme 1.24.3. Works!

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.