Skip to content

GB-272: the partner's acceptance result does not verify

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

What it means

In a bilateral acceptance session each side signs its phase 14 result and the other verifies it under the key bound to that side at phase 5, the same key that signs its federation package. The signature document beside the partner's result did not verify: it is malformed, it names another key, the result read is not the one it signs, or the signature does not verify under the bound key. Nothing from it is combined (docs/design/federation-acceptance.md §6.1).

Why it happens

  • the result or its signature document was altered, or the result was read before the partner finished writing it
  • the partner signed with a key other than the one bound to them at phase 5 (their federation key was rotated, or the wrong key file was used)
  • the signature document is not goat-acceptance-signature/v1, or a member is missing or malformed

What to do

One line per step or alternative:

check with the partner, on the call, the key fingerprint confirmed at phase 5 and the one their signature document names
ask the partner to run phase 14 again in the same session, so a new result and signature are published

Read more

Exit code

goatbuilder exits with 2.