Ilker ManapandClaude Opus 5.5 0bd5305e9a Install only releases signed with the key built in; fetch a node's release on the control plane ...

trusted.pub now holds the release signing key, so self-upgrade, agent
upgrade and node onboarding refuse a release whose checksums are not signed
with it. Onboarding fetched the release on the node and compared it with a
checksum from the same server; the control plane now fetches it for the
node's architecture with release.Fetch, checks signature and checksum, and
hands the bytes over. Release addresses must be https (loopback excepted).
LLMGW_RELEASE_KEY overrides the key only in development builds. The CI
release job fails instead of publishing an unsigned release while a key is
built in.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

2026-10-04 09:48:03 +02:00

..

release_test.go

Install only releases signed with the key built in; fetch a node's release on the control plane

2026-10-04 09:48:03 +02:00

release.go

Install only releases signed with the key built in; fetch a node's release on the control plane

2026-10-04 09:48:03 +02:00

sign_test.go

Install only releases signed with the key built in; fetch a node's release on the control plane

2026-10-04 09:48:03 +02:00

sign.go

Install only releases signed with the key built in; fetch a node's release on the control plane

2026-10-04 09:48:03 +02:00

trusted.pub

Install only releases signed with the key built in; fetch a node's release on the control plane

2026-10-04 09:48:03 +02:00