LM 22.2 Cinnamon ISO failed Verification with misleading errror message

Open
#137 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
cli, security

Research direction

Start with the mint-iso-verify command and trace the handling of the unknown-signature and key-not-found results shown in the report. Confirm how the GUI and command-line messages are produced; done means a missing Linux Mint signing key is explained clearly instead of only reporting an unknown signature.

Written by the indexing model from the issue text.

Description

The tool shows an error message which might be misleading for unexperienced users:

mint-iso-verify linuxmint-22.2-cinnamon-64bit.iso
Checking /home/[user]/Downloads/linuxmint-22.2-cinnamon-64bit.iso
Importing 27DEB15644C6B3CF3BD7D291300F846BA25BAE09 from hkp://keyserver.ubuntu.com
Deleting 27DEB15644C6B3CF3BD7D291300F846BA25BAE09
Importing 27DEB15644C6B3CF3BD7D291300F846BA25BAE09 from hkp://keys.openpgp.org
Deleting 27DEB15644C6B3CF3BD7D291300F846BA25BAE09

(GUI:)
unknown signature
key not found on key server
signed by: 27DEB15644C6B3CF3BD7D291300F846BA25BAE09

Reason is ONLY the missing Linux Mint signing key which must be re-imported
gpg --keyserver hkp://keys.openpgp.org:80 --recv-key 27DEB15644C6B3CF3BD7D291300F846BA25BAE09

For the default mint-iso-verify tool it seems a little strange that just its very own signing key is marked only as "unknown signature" and "key not found on key server" without any further explaination.

This type of error message didn't pop up in previous releases (?)

Dominant language
Python
Stars
173
Forks
64
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linuxmint/mintstick

All issues in linuxmint/mintstick

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.