Relay secret rotates on every infra sync #25

New Issue

2026-04-17T17:52:41Z

userAdityaa commented

2026-04-17 17:52:41 +00:00

Description

Infra sync currently generates a new relay secret each time sync_relay runs and includes it in both create (POST) and update (PUT) payloads.
Infra sync is triggered by create_relay, update_relay, activate_relay, and deactivate_relay activities.
Because relay secret is not persisted and reused, routine updates can rotate secrets unintentionally.

Expected behavior

Relay secret remains stable per relay unless an explicit rotate-secret action is requested.

Looking at zooid spec here (https://gitea.coracle.social/coracle/zooid#zooid):

Every update sends a new secret to Zooid.
Zooid updates its config file with the new secret.
The relay's public key changes.
Next time a client connects, they see a different public key.
The relay appears to be a different relay.

### Description * Infra sync currently generates a new relay secret each time `sync_relay` runs and includes it in both create (POST) and update (PUT) payloads. * Infra sync is triggered by create_relay, update_relay, activate_relay, and deactivate_relay activities. * Because relay secret is not persisted and reused, routine updates can rotate secrets unintentionally. ### Expected behavior Relay secret remains stable per relay unless an explicit rotate-secret action is requested. ### Looking at zooid spec here (https://gitea.coracle.social/coracle/zooid#zooid): * Every update sends a new secret to Zooid. * Zooid updates its config file with the new secret. * The relay's public key changes. * Next time a client connects, they see a different public key. * The relay appears to be a different relay.

hodlbod commented

2026-04-17 18:55:51 +00:00

Absolutely, I think the solution is to change this request form a PUT to a PATCH

👍 1

userAdityaa referenced a pull request that will close this issue

2026-04-18 08:34:12 +00:00

fix: relay secret rotation on infra sync updates #26

hodlbod closed this issue

2026-04-18 13:24:09 +00:00

Sign in to join this conversation.