mirror of
https://github.com/garrytan/gstack.git
synced 2026-09-10 15:09:00 +02:00
Garry Tan
a2751b7cf2
GET /health is now liveness/status only in every mode — both token carve-outs (headed-mode disjunct AND chrome-extension:// Origin disjunct) are removed. Token bootstrap is POST /extension-token on the local listener: the Origin header must be exactly chrome-extension://<GSTACK_EXTENSION_ID> and the Host header's hostname must parse to 127.0.0.1 or localhost (parsed via new URL, never literal equality — Host arrives as '127.0.0.1:34567'). Wrong origin/host → 403 with no detail. The tunnel surface 404s the endpoint (not in TUNNEL_PATHS, verified by test). The extension ID is pinned by a new "key" field (RSA public key) in extension/manifest.json; browse/scripts/extension-id.ts reproduces the ID derivation (first 16 bytes of SHA-256 of the DER public key, hex mapped 0-9a-f → a-p). The private key is not committed anywhere — unpacked/baked-in loads only need the public key. Extension side: background.js bootstraps and refreshes the token via POST /extension-token (403 → disconnected state); sidepanel.js direct connect path does the same; sidepanel-terminal.js's dead /health token fallback (read AUTH_TOKEN/authToken keys the server never sent, hardcoded port) is replaced with the window.gstackAuthToken path. MIGRATION NOTE: the manifest key pins the extension ID, so existing installs' side-panel local state (saved port, snoozes) resets once — explained in-product via a one-time notice (flag gstack_id_migrated_v162). After upgrading the server, restart the browser so the old service worker stops polling for a token GET /health no longer serves. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> (cherry picked from commit e9a0b6847a2d17fe6656a4686b4efd0c8380eb09)
46 lines
1.7 KiB
TypeScript
Executable File
46 lines
1.7 KiB
TypeScript
Executable File
#!/usr/bin/env bun
|
|
/**
|
|
* Derive the Chrome extension ID from the "key" field in
|
|
* extension/manifest.json.
|
|
*
|
|
* Chrome computes an extension's ID as the first 16 bytes of the SHA-256
|
|
* hash of the DER-encoded public key, with each hex nibble mapped from
|
|
* 0-9a-f to a-p (the "mpdecimal" alphabet). Pinning the public key in the
|
|
* manifest pins the ID, which lets the browse server verify the Origin
|
|
* header on POST /extension-token against a single known extension
|
|
* identity (GSTACK_EXTENSION_ID in browse/src/server.ts).
|
|
*
|
|
* The private half of the keypair is intentionally NOT in the repo — the
|
|
* extension is loaded unpacked (or baked into Browser.app), so only the
|
|
* public key is needed to pin the ID. Regenerating the keypair changes
|
|
* the ID and requires updating both the manifest "key" and the
|
|
* GSTACK_EXTENSION_ID constant.
|
|
*
|
|
* Usage: bun browse/scripts/extension-id.ts [path/to/manifest.json]
|
|
*/
|
|
|
|
import { createHash } from 'node:crypto';
|
|
import * as fs from 'node:fs';
|
|
import * as path from 'node:path';
|
|
|
|
const manifestPath = process.argv[2]
|
|
?? path.join(import.meta.dir, '../../extension/manifest.json');
|
|
|
|
const manifest = JSON.parse(fs.readFileSync(manifestPath, 'utf-8'));
|
|
if (typeof manifest.key !== 'string' || manifest.key.length === 0) {
|
|
console.error(`No "key" field in ${manifestPath}`);
|
|
process.exit(1);
|
|
}
|
|
|
|
export function extensionIdFromPublicKey(publicKeyBase64: string): string {
|
|
const der = Buffer.from(publicKeyBase64, 'base64');
|
|
const hex = createHash('sha256').update(der).digest('hex').slice(0, 32);
|
|
let id = '';
|
|
for (const c of hex) {
|
|
id += String.fromCharCode('a'.charCodeAt(0) + parseInt(c, 16));
|
|
}
|
|
return id;
|
|
}
|
|
|
|
console.log(extensionIdFromPublicKey(manifest.key));
|