@botiverse/porthole 0.14.4 → 0.14.5
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/CHANGELOG.md +18 -0
- package/dist/check/page-source.js +1 -1
- package/dist/conformance/harness-source.js +1 -1
- package/dist/host/create-host.js +2 -0
- package/dist/host/outcome.d.ts +4 -0
- package/dist/host/outcome.js +43 -0
- package/dist/host/types.d.ts +12 -4
- package/dist/react/frame.d.ts +2 -1
- package/docs/ADOPTING.md +5 -0
- package/docs/DECISIONS.md +92 -0
- package/docs/DESIGN.md +3 -1
- package/docs/THREAT_MODEL.md +32 -3
- package/package.json +1 -1
- package/src/host/create-host.ts +2 -0
- package/src/host/outcome.ts +49 -0
- package/src/host/types.ts +12 -4
- package/src/react/frame.tsx +2 -1
package/CHANGELOG.md
CHANGED
|
@@ -4,6 +4,24 @@
|
|
|
4
4
|
section); the reasons for every change are in [docs/DECISIONS.md](docs/DECISIONS.md), by the
|
|
5
5
|
P-numbers below.
|
|
6
6
|
|
|
7
|
+
## 0.14.5
|
|
8
|
+
|
|
9
|
+
- **Security (P124, after the audit raft-security-audit#16):** any frame could say
|
|
10
|
+
`porthole/notifications/frame-status` (an opaque widget, a served page, an MCP Apps view, a
|
|
11
|
+
nested page through its shell), and the host took it as Porthole's server's word: its `outcome`
|
|
12
|
+
became `blocked` with the content's reason and code, and a host drew its fallback in Porthole's
|
|
13
|
+
wording ("Open this in a new tab to sign in") with a link out. Now an opaque frame's frame status
|
|
14
|
+
is never taken, and a frame that speaks is heard only before anything else it says in the run
|
|
15
|
+
(its first document, a page of Porthole's; content always runs after Porthole's own first word).
|
|
16
|
+
One not taken is no outcome and no code: the host hears a `hostError` of the new kind
|
|
17
|
+
`frame-status`, once a run. A url-mode app's word is taken as before (THREAT_MODEL S6). Changed:
|
|
18
|
+
a frame that speaks no longer tells a later block itself; a display without files starts again
|
|
19
|
+
and its next run says it, and in one with files a page answered by a status page (access revoked)
|
|
20
|
+
shows the server's page in the frame without a `blocked` outcome.
|
|
21
|
+
- **Tests (P124):** `test/outcome.test.ts` ("who may say how loading went"); four forgers in
|
|
22
|
+
`leak/served/outcome.spec.ts` (a served shell's content, an artifact page, an opaque widget, a
|
|
23
|
+
nested page), negative control `frame-status`.
|
|
24
|
+
|
|
7
25
|
## 0.14.4
|
|
8
26
|
|
|
9
27
|
- **Docs (P123):** a display taking the keyboard is an accepted risk (THREAT_MODEL §5): the guard
|