Why does Kleopatra add .out extension to the decrypted filename?

Me and a collegue are using Symantec PGP Desktop. My company is discontinuing the use of Symantec PGP Desktop, so I installed Kleopatra to test before making the switch. My collegue is still using Symantec PGP Desktop. When I receive an encrypted file from my collegue (e.g. filename.pdf.pgp), I use Kleopatra to decrypt it. But, for some reason, Kleopatra is adding the extension ‘.out’ to the decrypted filename (e.g. filename.pdf.pgp.out). If I use PGP Desktop, the output file has the original decrypted filename (e.g. filename.pdf). Why is Kleopatra adding another extension instead of removing the pgp extension?

I downloaded and installed gpg4win-4.4.1.exe and accepted all the defaults. When decrypting, I browse and select the pgp-encrypted file. Then I get a window that shows it has been decrypted successfully. It shows the original encrypted filename and the output (same filename) but with an added extension ‘.out’. It seems that when this window (Decrypt/Verify Files) appears, it is already decrypting. The message in this window has the progressbar at 100% indicating ‘All operations completed’. The log below that shows the original filename and the output (decrypted) filename (with .out extension added). Below the filenames it shows ‘Decryption succeedded’.

I have not changed the settings from the defaults. Any help as to why Kleopatra is adding the file extension would be greately appreciated. Thanks.

Versions:
Kleopatra 3.3.0

  • GnuPG 2.4.8
  • Libgcrypt 1.11.1

I cannot reproduce this issue on my machine (also with Gpg4win 4.4.1). @eebb do you have an idea?

Maybe the dots in the filename are not ASCII but unicode dots?

We only add “.out” if the filename has no extension. And an extension starts with a plain ASCII dot.

Please try to change the dots in the filename before decryption to be sure that they are ASCII dots.

And by the way: one should always change the view in the file explorer to show all filename extensions. That is another thing which often causes confusion.

Thanks for the replies. After peforming multiple tests, we found that the issue is only with pgp files generated by PGP Desktop from one of my collegues. I can encrypt and create a PGP file on my system and decrypt with Kleopatra without file extension issue. I read that PGP can include a suggested filename in its header. Is it possible that this is what may be causing Kleopatra to add the .out extension? PGP Desktop includes an option to “Ignore suggested filenames when decrypting”. I did not see this on Kleopatra config.

Here is a pic that shows Kleopatra’s ‘Decrypt/Verify Files’ window showing success as well as the original pgp-encrypted file and output file (with out extension added). I never uploaded so I hope you can see.

Interesting!

If I encrypt a file and replace the ending gpg to PGP in the process, it breaks: the file is classified as renamed (even though only the ending was changed in my test case) and “.out” is added. This is the same if I change the ending to an upper case “GPG”.

If I change the ending to pgp (that is in lowercase letters) instead, it works like you would expect and the ending “.pgp” is stripped.

Looks like we have a problem with upper and lower case here.
I’ll file a bug. Thank you for the report!

https://dev.gnupg.org/T7780

Fixed in gpg4win-5.0.0-beta369

1 Like