A bookmark attestation clients can't verify breaks every fetch of the repository (bomberman94: unknown key 1527a41c720a) issue #266 closed: completed andymccall opened this 16 days ago · 0 comments

Since about 01:49 BST on 2026-10-19, every fetch or clone of doomsdayone/bomberman94 fails:

error: attestation for origin/area12-131: unknown key [1527a41c720a](/andymccall/oxygenhub/change/1527a41c720a)

It fails on all three runners (flow ca5011e8), with released oxy 0.4.6, and with oxygen main. The bookmark area12-131 was last moved at 01:49 by a push from the project's agent, and the hub accepted it. So the hub could verify the move, but the identity of the key that signed the attestation is not served to clients. Every bomberman94 job has errored since; plex-1 drew five in a row and was drained (by design, after 5 infrastructure errors).

To do:

1. Find whose key 1527a41c720a is (keyless certificate, delegate, or other) and why the fetch doesn't carry its identity, when the hub had it to accept the push (compare oxygenhub#129, where a delegate's first bookmark move lacked its identity).
2. Fix the cause so clients get what they need to verify, plus a test.
3. Robustness: one bookmark whose attestation a client can't verify should not fail the whole fetch. Skip that bookmark's update with a warning and fetch the rest (security: the bookmark stays unverified, and is not adopted).

Reported by Andy (plex-1 stuck draining).