git-ecosystem / git-ecosystem/git-credential-manager

Verification of debian package signature failing for 'origin'

Open
#1,615 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
9.3k
Forks
2.9k
Avg merge
7d 1h
Merged PRs (30d)
14

Description

I am trying to follow the instructions for verifying the signature of the debian install package.

I have the signature .gpg and policy file set up (Seem to be correct!)

When I run the signature verification on any of the packages since 2.4.0 and up to 2.5.0

debsig-verify -v gcm-linux_amd64.2.4.0.deb
I get:

debsig: Starting verification for: gcm-linux_amd64.2.4.0.deb
debsig: Using policy directory: /etc/debsig/policies/3C853823978B07FA
debsig:   Parsing policy file: /etc/debsig/policies/3C853823978B07FA/generic.pol
debsig:     Checking Selection group(s).
debsig:       Processing 'origin' key...
debsig:     Selection group(s) passed, policy is usable.
debsig: Using policy file: /etc/debsig/policies/3C853823978B07FA/generic.pol
debsig:     Checking Verification group(s).
debsig:       Processing 'origin' key...
debsig:     Verification group failed checks.
debsig: Failed verification for gcm-linux_amd64.2.4.0.deb.

If I try an earlier say 2.3.2 the key appears to have changed:

debsig-verify -v gcm-linux_amd64.2.3.2.deb 
debsig: Starting verification for: gcm-linux_amd64.2.3.2.deb
debsig: Could not find Origin directory for EB3E94ADBE1229CF

Any ideas? Is the signature bad? the download corrupt? or something else?

Installed on Debian - Bookworm (12)

Contributor guide

Open the contributing guide

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.

Research direction

Start by reproducing the debsig-verify commands for gcm-linux_amd64.2.4.0.deb and gcm-linux_amd64.2.3.2.deb, then inspect the referenced generic.pol policy and the reported key IDs. Done means determining whether the package signature, download, or policy/key setup causes verification to fail and documenting the required resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
debian, linux
Domain
security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.