Skip to content

fix installer fingerprint bootstrap by loading trust bulletin#84

Merged
ian-pascoe merged 3 commits intomainfrom
fix/installer-runtime-fingerprint
Mar 2, 2026
Merged

fix installer fingerprint bootstrap by loading trust bulletin#84
ian-pascoe merged 3 commits intomainfrom
fix/installer-runtime-fingerprint

Conversation

@ian-pascoe
Copy link
Contributor

Summary

  • Stop hardcoding the core registry fingerprint in both install scripts and resolve it at runtime from docs/trust/core-registry-fingerprint.txt.
  • Validate trust bulletin fields (source, kind, url, fingerprint_sha256) and fail closed when fetch/parse/validation fails, with explicit override support.
  • Update user/operator docs to remove stale hardcoded fingerprint guidance and document runtime resolution behavior.

Test Plan

  • sh -n scripts/install.sh
  • crosspack registry list
  • crosspack update (currently fails in this environment with source-snapshot-missing, unrelated to these script changes)
  • PowerShell syntax check could not run in this environment because pwsh is not installed.

Avoid stale hardcoded installer fingerprints by loading and validating docs/trust/core-registry-fingerprint.txt at install time, with explicit override support for controlled/offline use.
Fetch crosspack-registry registry.pub at install time and hash it to compute the pinned fingerprint, avoiding stale repository-side constants.
Switch guidance to deriving the core source fingerprint directly from crosspack-registry registry.pub and drop stale in-repo fingerprint distribution references.
@ian-pascoe ian-pascoe merged commit cf059ab into main Mar 2, 2026
6 checks passed
@ian-pascoe ian-pascoe deleted the fix/installer-runtime-fingerprint branch March 2, 2026 16:05
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