Page MenuHome GnuPG
Create Task
Maniphest T3992

Kleopatra: Bad handling of non standard detached ASCII-armored signature
Open, NormalPublic
Actions

Description

When I try to open https://bitbucket.org/ligos/readablepassphrasegenerator/downloads/ReadablePassphrase%201.1.1.plgx%20signatures.txt with Kleopatra (or GpgEX), I get the error:

An error occurred: Kleopatra: Could not open file "H:/Downloads/ReadablePassphrase%201.1.0.plgx%20signatures" for reading: Input/output error (218136625)

But it looks like it wiped the extension off and tried to open it without the .txt.

It also looks like Kleopatra can't generate armored or Base64 signatures... when did you stop supporting this format?

Details

Version
Kleopatra 3.1.0-gpg4win-3.1.0

Related Objects

Event Timeline

NHarvey created this task.May 19 2018, 4:22 AM
aheinecke claimed this task.May 22 2018, 9:09 AM
aheinecke triaged this task as Normal priority.
aheinecke added a subscriber: aheinecke.

Thanks for the report. This is indeed a bug.

The behavior is expected in that it can't automatically find the signed file, as it does not follow the usual naming convention of <signed_filename>.sig
But Kleopatra should then query you to which file the signature belongs to and not fail with that Input/Output error.

I'll change the task name accordingly so that its easier to find.

It also looks like Kleopatra can't generate armored or Base64 signatures... when did you stop supporting this format?

Under settings -> Crypto Operations there is "Create signed or encrypted files as text files"

We have an issue (can't find it quickly) already to change that to an "Ask" where we make the option add a checkbox again in the dialog.

When looking at Usability for Gpg4win 3.0 users were confused and did not know what this option meant so we mad it an option.

aheinecke renamed this task from Cannot verify detached ASCII-armored signature to Kleopatra: Bad handling of non standard detached ASCII-armored signature.May 22 2018, 9:09 AM
TeeLittle mentioned this in T4355: GpgEX/Verify: signature with non-standard file name causes misleading error message .Jan 30 2019, 5:22 PM