mirror of
https://github.com/lrnselfreliance/wrolpi.git
synced 2026-11-20 23:16:17 -05:00
Upgrade: mark the pinned GPG key trusted in the throwaway keyring.
verify-commit judges signature validity regardless of ownertrust, so the upgrade's security model (possession of the pinned key is the trust anchor) is unchanged — but gpg printed "WARNING: This key is not certified with a trusted signature!" on every healthy upgrade, making valid-signature logs look like something continued past a failure. Import ownertrust for the sole key in the keyring to silence it. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
parent
fdf65e218e
commit
ce05a073dd
1 changed files with 7 additions and 0 deletions
|
|
@ -109,6 +109,13 @@ git -C /opt/wrolpi fetch || exit 4
|
|||
GNUPGHOME=$(mktemp -d)
|
||||
export GNUPGHOME
|
||||
gpg --batch --quiet --import /opt/wrolpi/wrolpi/roland@learningselfreliance.com.gpg
|
||||
# The throwaway keyring contains only the pinned WROLPi key, so mark it
|
||||
# ultimately trusted: possession of the pinned key IS the trust anchor here,
|
||||
# and this silences gpg's web-of-trust WARNING noise that makes healthy
|
||||
# upgrade logs look scary. Cosmetic only — verify-commit already ignores
|
||||
# ownertrust when judging signature validity.
|
||||
gpg --batch --list-keys --with-colons | awk -F: '/^fpr:/ {print $10":6:"; exit}' | \
|
||||
gpg --batch --quiet --import-ownertrust || :
|
||||
|
||||
# Verify the fetched commit is signed by the trusted key before checking it out.
|
||||
if ! git -C /opt/wrolpi verify-commit origin/"${BRANCH}" 2>&1; then
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue