Skip to content

Adds gpg code signing ca for commit verification during manjikaze auto-updates#76

Open
rolandboon wants to merge 1 commit intofeature/yubikey-ssh-gpgfrom
feature/code-signing-ca-updates
Open

Adds gpg code signing ca for commit verification during manjikaze auto-updates#76
rolandboon wants to merge 1 commit intofeature/yubikey-ssh-gpgfrom
feature/code-signing-ca-updates

Conversation

@rolandboon
Copy link
Member

@rolandboon rolandboon commented Feb 23, 2026

Manjikaze's auto-update mechanism pulls and executes code from the repository without verifying who authored it. If someone gains push access (e.g. through a compromised GitHub account), they could inject malicious code that runs automatically on every developer's machine.

This PR implements a GPG Certificate Authority (CA) trust model. Instead of maintaining a list of individual trusted GPG fingerprints, we use a single trust anchor: the 10KB Code Signing CA to verify the entire chain.

A commit is only accepted if it is signed by a GPG key that has been certified by the CA. Keys not signed by the CA are rejected, regardless of whether they exist on a keyserver.

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

Successfully merging this pull request may close these issues.

1 participant