Skip to content

GB-193: our verifying key cannot be read, or does not verify our half

Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-193 is printed by goatbuilder. The same text offline: goat explain GB-193 or goatbuilder explain GB-193.

What it means

Phase 5 shows our verifying key to read aloud, derived from the Ed25519 seed that signs our package (FED_SIGNING_KEY: 64 hex characters or 32 bytes base64). It is unset, unreadable or not a seed, or the key it gives does not verify the signature on our half, so the partner would bind a key that cannot verify our package.

Why it happens

  • FED_SIGNING_KEY is not set in this environment
  • it names a file that is not the package-signing seed, or a different seed than phase 3 signed with

What to do

One line per step or alternative:

set FED_SIGNING_KEY to the seed that signed our package (the same one phase 3 uses)

Read more

Exit code

goatbuilder exits with 1.