Skip to content

fix(signer): handle go-livepeer v0.8.12 fail-closed no-auth check - #56

Draft
rickstaa wants to merge 1 commit into
mainfrom
docs/remote-signer-allow-no-auth
Draft

fix(signer): handle go-livepeer v0.8.12 fail-closed no-auth check#56
rickstaa wants to merge 1 commit into
mainfrom
docs/remote-signer-allow-no-auth

Conversation

@rickstaa

@rickstaa rickstaa commented Jul 1, 2026

Copy link
Copy Markdown
Member

Warning

livepeer/go-livepeer:v0.8.12 is not yet published on Docker Hub, so this image won't build until the release is cut. Opening now so the required entrypoint change isn't forgotten. @john please ping when v0.8.12 ships.

What

go-livepeer v0.8.12 (livepeer/go-livepeer#3959) makes the remote signer fail closed: a signer bound to a public -httpAddr with no -remoteSignerWebhookUrl now refuses to start unless -remoteSignerAllowNoAuth is explicitly set.

Our remote-signer/entrypoint.sh always binds -httpAddr=0.0.0.0:${SIGNER_PORT}. So:

  • Production (REMOTE_SIGNER_WEBHOOK_URL set): unaffected — the webhook flag is present.
  • Signer-only alive check (empty REMOTE_SIGNER_WEBHOOK_URL, README §1): would refuse to start on v0.8.12, because go-livepeer keys the check on the internal 0.0.0.0 bind, not on Compose's loopback-only port publish.

Changes

  • entrypoint.sh: add -remoteSignerAllowNoAuth on the no-webhook path. Safe because Compose publishes the signing port on 127.0.0.1 only.
  • Dockerfile: bump base image v0.8.11v0.8.12.
  • README.md: document the behavior.

Copilot AI review requested due to automatic review settings July 1, 2026 12:04
@rickstaa
rickstaa force-pushed the docs/remote-signer-allow-no-auth branch from 95a9024 to b496fbb Compare July 1, 2026 12:05
go-livepeer v0.8.12 (livepeer/go-livepeer#3959) makes a remote signer with a
public -httpAddr and no -remoteSignerWebhookUrl fail-closed at startup unless
-remoteSignerAllowNoAuth is set. The entrypoint always binds -httpAddr=0.0.0.0,
so the signer-only alive-check path (empty REMOTE_SIGNER_WEBHOOK_URL) would
refuse to start. Add the opt-in flag on that path — safe because Compose
publishes the signing port on 127.0.0.1 only.

Bump base image to v0.8.12 and document the behavior in the README.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@rickstaa
rickstaa force-pushed the docs/remote-signer-allow-no-auth branch from b496fbb to 66d3a78 Compare July 1, 2026 12:07
@rickstaa
rickstaa marked this pull request as draft July 1, 2026 12:07

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the remote-signer container to accommodate go-livepeer v0.8.12’s new “fail-closed” behavior when running a public -httpAddr without a webhook, so local signer-only “alive checks” can still run.

Changes:

  • Add -remoteSignerAllowNoAuth on the no-webhook execution path in remote-signer/entrypoint.sh.
  • Bump the remote-signer base image from livepeer/go-livepeer:v0.8.11 to v0.8.12.
  • Document the new go-livepeer behavior and the stack’s loopback-only port publishing in README.md.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
remote-signer/entrypoint.sh Adds the no-auth allow flag for the no-webhook path to keep the signer startable on go-livepeer v0.8.12.
remote-signer/Dockerfile Updates the base image tag to go-livepeer v0.8.12.
README.md Documents the v0.8.12 behavior and the loopback-only publishing rationale.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines 46 to 50
else
echo "entrypoint: WARNING: starting remote signer without identity webhook authorization" >&2
# Allow running the signer without a webhook (local alive checks only, not production).
set -- "$@" -remoteSignerAllowNoAuth
fi
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants