Ilker ManapandClaude Opus 5.5
0bd5305e9a
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>
2 lines
45 B
Plaintext
2 lines
45 B
Plaintext
DrmKRQmeI7w0xSnBThCpfMvyqBVrxYcbJGJT52fl6J8=
|