Ship the extension as a signed CRX from our own update server
The dashboard-hosting stack from the previous commit is gone; it was answering a question nobody asked. What was actually needed is Chrome's real update channel, which an unpacked extension does not have and cannot be given. So the extension is now signed into a CRX with an update manifest beside it, served from the droplet, and installed on the trading machines by policy (ExtensionInstallForcelist). From there Chrome installs it, updates it on its own schedule, and puts it back if it goes missing. The manifest gained the `key` that fixes the extension id, so an unpacked development load keeps the same identity as the published build. The self-update check now branches on how it was installed: policy installs ask Chrome to check the update server now rather than waiting out its five-hour cycle, and unpacked loads keep the reload-from-disk path. chrome.management .getSelf() tells the two apart and needs no permission to do it. The signing key lives at /opt/autofirmer-updates/key.pem on the droplet and nowhere else. It is the extension's identity: a different key is a different extension, and no browser would take it as an update. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
ece6aab9cf
commit
035f93d220
@@ -2,11 +2,8 @@ import { NextResponse } from 'next/server';
|
||||
|
||||
/** The Chromium extension calls these routes from a background service worker,
|
||||
* whose Origin is `chrome-extension://<id>`. The id changes every time the
|
||||
* unpacked extension is reloaded, so we allow any origin.
|
||||
*
|
||||
* That was harmless while this only ever answered on the LAN behind the
|
||||
* port-3000 firewall rule. The hosted dashboard has no such fence — see
|
||||
* deploy/README.md, "No login". */
|
||||
* unpacked extension is reloaded, so we allow any origin — these routes are
|
||||
* only ever reachable on the LAN behind the port-3000 firewall rule. */
|
||||
export const CORS_HEADERS = {
|
||||
'Access-Control-Allow-Origin': '*',
|
||||
'Access-Control-Allow-Methods': 'GET, POST, PATCH, DELETE, OPTIONS',
|
||||
|
||||
Reference in New Issue
Block a user