Skip to content

GB-285: the directory binds our previous signing key, and the seed that hands it over is missing

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

What it means

Phase 5's directory step publishes our pointer signed by the key that signed our package. The directory binds our sovereign_id to the first key that wrote it, and takes a new key only through the entry, when the request is signed by the key it replaces. The directory binds another key than ours: our signing key was rotated, and FED_PREVIOUS_SIGNING_KEY is not set, is not readable or holds the seed of a third key, or the pointer names another of our peerings' packages. Nothing was published; the directory still serves what it held. The step is advisory, so phase 5 goes on.

Why it happens

  • our signing key was rotated (FED_SIGNING_KEY names the new seed) and FED_PREVIOUS_SIGNING_KEY was not set
  • FED_PREVIOUS_SIGNING_KEY names a seed other than the one the directory binds (the message names both keys)
  • with one package per counterparty, the pointer names another peering's package, and the key is handed over only through the pointer

What to do

One line per step or alternative:

FED_PREVIOUS_SIGNING_KEY=<file of the seed that signed our last package> goatbuilder federate <partner> --from 5
with several peerings, run phase 5 of the peering whose package the pointer names first; the others then publish under the new key
if the previous seed is lost, the directory's operator clears the entry (saltlick clear), and the next write claims it again

Read more

Exit code

goatbuilder exits with 0.