Kleopatra: improve first part of decryption/verification message
Testing, NormalPublic

Assigned To
Authored By
ebo
May 21 2026, 3:36 PM

Description

Hint for testing: T8332 and T7795 change these texts, too. These tickets have to be seen together.

„Success“ messages (no failures or cancellation) when decrypting and or verifying. The verification text will follow after this and are addressed in another ticket.

I think the failure messages are all OK.

Current message versions verify only:
  • Verified <filename>%2</filename> with signature in <filename>%3</filename>.
  • Verified <filename>%2</filename> with %1 signatures in <filename>%3</filename>.

→can stay as is.

Current message decrypt+verify:
Successfully decrypted and verified <filename>%1</filename> as <filename>%2</filename>.
Recipient[s]: xxx

Alternatives (for the part before recipients), in order of my preference:
* Decrypted <filename>%1</filename> as <filename>%2</filename>. For verification result[s] see below.

  • Decrypted and verified <filename>%1</filename> as <filename>%2</filename>.

* <filename>%1</filename> was verified and decrypted as <filename>%1</filename>.

Current message decryption only:
Successfully decrypted <filename>%1</filename> as <filename>%2</filename>.
Recipient[s]: xxx

Alternatives (for the part before recipients), in order of my preference:

  • Decrypted <filename>%1</filename> as <filename>%2</filename>.

* <filename>%1</filename> was decrypted as <filename>%1</filename>.

Edited on 2026-06-05 and 2026-06-08 with discussion results

Event Timeline

ebo triaged this task as Normal priority.May 21 2026, 3:36 PM
ebo created this task.
ebo created this object with edit policy "Contributor (Project)".
ebo mentioned this in Unknown Object (Maniphest Task).Jun 1 2026, 9:01 AM

It occurred to me that users may find the wording "evaluated FILE with signature" strange, because if you have a paper document you check the signature and not the content of the file.
Opinions?

After discussion various other wordings like:

  • Evaluated <filename>%2</filename> with signature in <filename>%3</filename>.
  • Integrity of file <filename>%2</filename> checked with signature in <filename>%3</filename>.
  • Checked the integrity of file <filename>%2</filename> with signature in <filename>%3</filename>.
  • Checked <filename>%2</filename> with signature in <filename>%3</filename>.
  • Compared <filename>%2</filename> with signature in <filename>%3</filename>.
  • Data and signature have been verified to match

We decided to only remove the word "Successfully" and keep everything else as is.

fwiw: it should be possible to show a different text in the case of "bad signature" but currently we want to keep it as simple as possible, i.e. no additional conditions.

ikloecker moved this task from Backlog to WIP on the gpd5x board.
ikloecker changed the task status from Open to Testing.Thu, Jun 11, 2:39 PM

Done and backported for GPD 5.1

ikloecker mentioned this in Unknown Object (Maniphest Task).Mon, Jun 15, 8:59 AM

Questions

  • I tested all cases for openpgp and smime and noticed, that smime decrypting a file encrypted for multiple recipients does not show the list of recipients (probably only the first). is this known or should a ticket be created?
  • Shouldn't this also be backported to vsd34?

Looks good to me on gpg4win-5.1.0-beta653 @ win11:

  • verify only
    • single signature
    • multiple signatures
  • decryption only
    • single recipient
    • multiple recipients
  • decrypt+verify
    • single recipient
    • multiple recipients:
timegrid edited projects, added gpd5x (gpd-5.1.0); removed gpd5x.

is this known or should a ticket be created?

not known yet. When you make a ticket, please test the command line, too.

Regarding backport: I would like it but @hej has started with the screenshots for the vsd 3.4 documentation…

In T8273#219806, @ebo wrote:

is this known or should a ticket be created?

not known yet. When you make a ticket, please test the command line, too.

The new ticket for that smime recipient issue: T8334: Only one recipient shown in decryption feedback for files S/MIME encrypted for multiple recipients