@ai-ecoverse/slicc 1.68.2 → 1.68.4

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.
Files changed (2) hide show
  1. package/README.md +2 -1
  2. package/package.json +7 -7
package/README.md CHANGED
@@ -933,6 +933,7 @@ Only browsers the user named are listed: the one seven runs in, `--cdp` and `--c
933
933
  `Fetch.continueRequest`, `continueResponse`, `failRequest`, `fulfillRequest`, `continueWithAuth` and `Network.continueInterceptedRequest` are refused with `slicc: refused: slicc didn't pass this paused request to the page, so it could be seven's` for any `requestId` or `interceptionId` the node hasn't passed to that session in a paused event, and for one whose pause the page has already answered successfully (until the next paused event for it). So a guessed id can't fulfil, change or fail a protected request, even one that is still paused. The node remembers the last 16 384 ids it passed on; an id older than that is refused too.
934
934
  - **Browser-wide commands**, refused with their own reason after `slicc: refused: `: `Target.exposeDevToolsProtocol` (it would give a page the whole browser) and `Target.sendMessageToTarget` (attach with `flatten: true` instead), on any target; `Fetch.enable` on the browser itself (a page session is fine); `Tracing.start`; `Extensions.loadUnpacked`; `Network.loadNetworkResource` on any session (Chrome follows its redirects itself, with the user's cookies, so an ordinary URL that redirects to seven would hand the page seven's page; a destination that is protected or doesn't parse keeps its usual refusal); `Page.captureSnapshot` (it serialises every frame, Chrome's error pages for seven's URLs included); and `Browser.setPermission`, `Browser.grantPermissions` without an `origin` and `Browser.resetPermissions`, except in a browser context this stream created.
935
935
  - **Auto-attach.** With `Target.setAutoAttach`, a session to a protected target is detached by the node at once (`Target.detachFromTarget` on its parent session), and the page never sees its `attachedToTarget` or `detachedFromTarget`.
936
+ - **Sign-in popups.** The node's guard does not hold seven's sign-in popups, and it doesn't hide the callback-only authorize tabs they lead to: seven's owner and slicc-bios do, and slicc-bios proves that with its own tests. The six shared slicc-browsers `C7.sign-in-hold.*` rows, their positives included (an ordinary popup and an ordinary authorize tab that must stay reachable), are skipped here by their own capability gate, since the guard run declares `signInHold` `false`. They will be measured on the link route once the vectors' hooks ship.
936
937
  - **Navigation by other means.** A script's `location = …`, a link, `window.open` or a server redirect isn't a command the node can refuse, so the node guards the network instead.
937
938
  - A target the stream attached to (`Target.attachToTarget`, or auto-attach that reached the page) or created (`Target.createTarget`) is *touched*, for as long as the stream is open, even after the page detached. That includes every tab the browser opens while the stream auto-attaches to new tabs. Attaching counts as touching. A protected tab opened after that touch from a page the client drives stays closable (the opener can't tell a user's click from the client's `window.open`); one that already existed when the stream started, even with that page as opener, does not.
938
939
  - On each touched page, iframe, background page or webview target the node attaches a session of its own, which the page never sees. On it, the node enables `Fetch` for document requests to protected hosts (`resourceType: Document`, request stage), and `Network` with `Network.setBypassServiceWorker`, so a service worker can't hand out a document without a request.
@@ -1018,7 +1019,7 @@ Only browsers the user named are listed: the one seven runs in, `--cdp` and `--c
1018
1019
 
1019
1020
  **`browsers` updates** (page cap `browsers`), node → page. When the list changes while a link is up and the page's HELLO has `browsers` in `caps`, the node opens `OPEN { "kind": "browsers", "browsers": [ … ] }` on the control channel with the full current list in HELLO's shape. It replaces the previous list; there are no deltas. The page answers OPENED `{}` and END, and the node sends END. Updates are sent one at a time per link, a change that comes while one is in flight is sent after it, with the list as it is then, and an update the page doesn't finish within 10 s is reset with `ETIMEDOUT`. A change between the HELLO and the link coming up is sent as an update right away.
1020
1021
 
1021
- `test/integration/testdata/link/link.js` is a page-side implementation of the link (framing, credit, both channel layouts, the violation rules, and `resolve` and raw-fetch helpers) that the integration tests run in Chrome against `slicc attach`. `cdp.js` next to it is a CDP client over `cdp` streams, `protect.js` probes the filter that keeps seven's origin and the browser's privileged pages out of reach, `guard.js` runs [slicc-browsers' guard vectors](https://github.com/ai-ecoverse/slicc-browsers#guard-vectors) through its `guard-runner.mjs`, with a second client straight to the test Chrome as the unguarded observer, every capability (`autoAttach`, `browserSession`, `browserContexts`, `chromeUrlsAttach`, since CDP over a DevTools port reaches `chrome://` pages, and `closeProtected`), and when `errorPageVault` remaps the C8 error-page rows onto the vault, vault documents are never closable, so the vault-remapped restore leg expects `closeRefused`, and the runner's `settleScale` at 3 on Windows, 2 on macOS and 1 on Linux, and its `refusalScale` at the default 1 (a row still running after 3 minutes fails on its own with the CDP calls it was waiting for, and the test fails after 4 minutes without a finished row, naming each row in flight and its pending calls), `fs.js` an op-shaped client for `fs` streams (`call`, `list`, `read`, `write`, `watch`), `loopback.js` is the page side of [loopback signalling](#linking-seven-in-your-everyday-browser), and `page.js` answers `browsers` and `mounts` updates. Through `linkTest.loopback`, `page.js` pairs from the fragment (`confirm`), signals again (`signal`, `reconnect`), unlinks in-band (`unlink`) and posts raw requests (`post`), with an optional `?ports=<first>-<last>` scan range. `page.js` keeps one link per `node` id from the hello. For tray links (no hello `node`) it replaces an older link with the same fingerprint only when HELLO's `node` matches, as seven does. `agent.js` is a fake agent behind the page's `agent` cap: the tests queue scripted runs, emit transcript events, hold and release a run, reset watch streams, and turn the cap off. Loaded with `?kernel`, the test page lists `kernel-in` and answers `kernel` OPENs with `kernel.js`, a small HTTP and WebSocket echo server in the page.
1022
+ `test/integration/testdata/link/link.js` is a page-side implementation of the link (framing, credit, both channel layouts, the violation rules, and `resolve` and raw-fetch helpers) that the integration tests run in Chrome against `slicc attach`. `cdp.js` next to it is a CDP client over `cdp` streams, `protect.js` probes the filter that keeps seven's origin and the browser's privileged pages out of reach, `guard.js` runs [slicc-browsers' guard vectors](https://github.com/ai-ecoverse/slicc-browsers#guard-vectors) through its `guard-runner.mjs`, with a second client straight to the test Chrome as the unguarded observer, the capabilities the link guard has (`autoAttach`, `iframeAutoAttach`, since the link route attaches out-of-process iframe targets under a page session, `browserSession`, `browserContexts`, `chromeUrlsAttach`, since CDP over a DevTools port reaches `chrome://` pages, and `closeProtected`), and `signInHold` declared `false`, since the link guard doesn't hold sign-in popups (see **Sign-in popups** in [`cdp`](#cdp-browser-control)). The six `C7.sign-in-hold.*` rows (`held-popup`, `callback`, `callback-encoded`, `callback-origin`, and the positives `ordinary-popup` and `ordinary-authorize`) are skipped by their own capability gate as `not-supported:signInHold`; `checkGuardSummary` accepts that reason only on those six rows, and any other reason on them, or that reason on any other vector, fails the run, and when `errorPageVault` remaps the C8 error-page rows onto the vault, vault documents are never closable, so the vault-remapped restore leg expects `closeRefused`, and the runner's `settleScale` at 3 on Windows, 2 on macOS and 1 on Linux, and its `refusalScale` at the default 1 (a row still running after 3 minutes fails on its own with the CDP calls it was waiting for, and the test fails after 4 minutes without a finished row, naming each row in flight and its pending calls), `fs.js` an op-shaped client for `fs` streams (`call`, `list`, `read`, `write`, `watch`), `loopback.js` is the page side of [loopback signalling](#linking-seven-in-your-everyday-browser), and `page.js` answers `browsers` and `mounts` updates. Through `linkTest.loopback`, `page.js` pairs from the fragment (`confirm`), signals again (`signal`, `reconnect`), unlinks in-band (`unlink`) and posts raw requests (`post`), with an optional `?ports=<first>-<last>` scan range. `page.js` keeps one link per `node` id from the hello. For tray links (no hello `node`) it replaces an older link with the same fingerprint only when HELLO's `node` matches, as seven does. `agent.js` is a fake agent behind the page's `agent` cap: the tests queue scripted runs, emit transcript events, hold and release a run, reset watch streams, and turn the cap off. Loaded with `?kernel`, the test page lists `kernel-in` and answers `kernel` OPENs with `kernel.js`, a small HTTP and WebSocket echo server in the page.
1022
1023
 
1023
1024
  ### Kernel services
1024
1025
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ai-ecoverse/slicc",
3
- "version": "1.68.2",
3
+ "version": "1.68.4",
4
4
  "description": "SLICC's command line for seven: links a machine's network, compute and browsers to seven over WebRTC",
5
5
  "license": "Apache-2.0",
6
6
  "repository": {
@@ -18,12 +18,12 @@
18
18
  "node": ">=18"
19
19
  },
20
20
  "optionalDependencies": {
21
- "@ai-ecoverse/slicc-darwin-arm64": "1.68.2",
22
- "@ai-ecoverse/slicc-darwin-amd64": "1.68.2",
23
- "@ai-ecoverse/slicc-linux-arm64": "1.68.2",
24
- "@ai-ecoverse/slicc-linux-amd64": "1.68.2",
25
- "@ai-ecoverse/slicc-windows-arm64": "1.68.2",
26
- "@ai-ecoverse/slicc-windows-amd64": "1.68.2",
21
+ "@ai-ecoverse/slicc-darwin-arm64": "1.68.4",
22
+ "@ai-ecoverse/slicc-darwin-amd64": "1.68.4",
23
+ "@ai-ecoverse/slicc-linux-arm64": "1.68.4",
24
+ "@ai-ecoverse/slicc-linux-amd64": "1.68.4",
25
+ "@ai-ecoverse/slicc-windows-arm64": "1.68.4",
26
+ "@ai-ecoverse/slicc-windows-amd64": "1.68.4",
27
27
  "@ai-ecoverse/slicc-jerk": "^1.9.1"
28
28
  }
29
29
  }