Skip to content

Bind Sparrow package verification to its publisher key #205

Description

@BenWestgate

The Sparrow installer fetches a configured SIGNING_KEY, but artifact acceptance uses generic gpg --verify against the user's persistent GnuPG keyring. The successful signer fingerprint is never compared with the configured Sparrow publisher fingerprint.

Affected code:

  • bails/.local/bin/install-sparrow

Impact: if the Sparrow release channel is compromised, an unrelated key already present in the user's GnuPG keyring can authenticate attacker-controlled package data. The accepted package is then installed and launched and can execute package post-installation code.

Expected fix: verify artifacts in an isolated keyring containing only the expected Sparrow publisher key, or parse machine-readable VALIDSIG output and require an exact canonical fingerprint match with SIGNING_KEY before processing package contents.

Bisq, Liana, Wasabi, and generic wallet installers are outside the supported scope.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions