poltertab 1.10.0 → 1.10.1-beta.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/mcp-server/bridge.js +3 -3
- package/package.json +1 -1
package/mcp-server/bridge.js
CHANGED
|
@@ -44,13 +44,13 @@ const path = require("path");
|
|
|
44
44
|
|
|
45
45
|
// ── Trusted extension IDs ─────────────────────────────────────────────────
|
|
46
46
|
// Upload config/log WS messages are restricted to origins paired via
|
|
47
|
-
// `poltertab uploads pair`. The CWS-assigned ID
|
|
48
|
-
//
|
|
47
|
+
// `poltertab uploads pair`. The CWS-assigned ID (below) is also trusted
|
|
48
|
+
// unconditionally — the Store build does not need to be paired separately.
|
|
49
49
|
//
|
|
50
50
|
// Caveat (design §4): a non-browser local process can forge any Origin header;
|
|
51
51
|
// this gate stops other Chrome extensions, not a hostile process with raw socket
|
|
52
52
|
// access. The always-blocked list and allowlist are the server-side guards.
|
|
53
|
-
const CWS_EXTENSION_ID = ""; //
|
|
53
|
+
const CWS_EXTENSION_ID = "lcijocampajjmennelacdfehmhndfmbd"; // Chrome Web Store extension id
|
|
54
54
|
|
|
55
55
|
// isUploadsAuthorized and isPaired may throw on malformed config.json —
|
|
56
56
|
// callers must catch and send uploads_error.
|
package/package.json
CHANGED