Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detached signatures created with the CLI cannot be verified in the GUI #117

Open
grempe opened this issue Jul 30, 2020 · 2 comments
Open

Comments

@grempe
Copy link

grempe commented Jul 30, 2020

Binary or Armored detached signatures created with the CLI cannot be verified in the GUI. Only attached signatures work.

# GUI FAIL "failed to verify: failed to verify file: invalid data "
$ keys sign --signer grempe@github --in foo.txt --out foo-a-d -a -d

# GUI OK
$ keys sign --signer grempe@github --in foo.txt --out foo-a-t -a -t

# GUI FAIL "failed to verify: failed to verify file: invalid data "
$ keys sign --signer grempe@github --in foo.txt --out foo-b-d -b -d

# GUI OK
$ keys sign --signer grempe@github --in foo.txt --out foo-b-t -b -t
@gabriel
Copy link
Contributor

gabriel commented Jul 31, 2020

Hmm, yeah it could detect if detached and check against a file name in the same directory (minus the .sig), or otherwise ask what file to check against. Or allow 2 files to be chosen at once.

Thanks for the bug report.

@grempe
Copy link
Author

grempe commented Jul 31, 2020

I'd lean toward allowing selection of both files, but only if the source file (minus the .sig) isn't found in the same dir by an automated scan by the app.

The more you can do this lifting for the user automatically with some opinion the easier for the user.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants