nats: a WebSocket listener for a page in a browser, from the overlay only (hq research 036)
mesh/merge-gate head e6d5ead50dfd merged into trunk 44e7002d3c84 — fail: builds nats, sent nowhere; merging this needs a person's bus upgrade; 1 wait(s) fo…
mesh/repo-check head e6d5ead50dfd merged into trunk 44e7002d3c84 — fail: head e6d5ead50dfd does not merge cleanly into trunk 44e7002d3c84: in conflict modu…
mesh/delivery stopped: the pull request closed unmerged
mesh/merge-gate head e6d5ead50dfd merged into trunk 44e7002d3c84 — fail: builds nats, sent nowhere; merging this needs a person's bus upgrade; 1 wait(s) fo…
mesh/repo-check head e6d5ead50dfd merged into trunk 44e7002d3c84 — fail: head e6d5ead50dfd does not merge cleanly into trunk 44e7002d3c84: in conflict modu…
mesh/delivery stopped: the pull request closed unmerged
The bus has no way for a browser to reach it (research 036, gap G1). The server now also listens over WebSocket on 4223: published from the mesh like 4222, so the machine's filter admits it from the overlay and nothing else; no TLS, acceptable only because the overlay is WireGuard and a browser cannot be made to trust the mesh's own certificate; compression on. The user a page connects as is the read-only view the controller composes (mesh-controller, `bus view-credential`). A test parses the declared configuration with the server itself, holds the opening, the published port and the listener to one port, and connects a client over WebSocket. The bus module's policy is `record`: this reaches the bus's machine only through the planned step a person starts (`bus upgrade`), as every bus change does.
This commit is contained in:
@@ -4,6 +4,17 @@ The bus server (novox/hq design 25), the configuration the module owns (`nats.co
|
||||
JetStream's store) and the user list the controller composes (`accounts.conf`), reloaded in place by
|
||||
the entrypoint. Its tools (`cmd/nats-tools`) are served by the node's runtime and only read.
|
||||
|
||||
## Its ports
|
||||
|
||||
`4222` is the bus: TLS, the mesh's own certificate, every link the mesh has. `4223` is the same server over
|
||||
WebSocket, for a client in a browser (nats.ws): the issue tracker's view page, connecting directly as the
|
||||
read-only user the controller composes for it (`bus view-credential`; novox/hq research 036). Both are
|
||||
published from the mesh only — the machine's filter admits them from the overlay and nothing else — and the
|
||||
WebSocket listener has no TLS *because* of that: the overlay is WireGuard, so every byte reaching it crossed
|
||||
the tunnel, and a browser cannot be made to trust the mesh's own certificate. The user still authenticates
|
||||
with the password the mesh minted, and is granted reads and nothing else. `8222` is the server's monitoring,
|
||||
on the machine's loopback alone.
|
||||
|
||||
## Its data, and how it is backed up
|
||||
|
||||
Everything the bus keeps is in JetStream: every stream, and every key-value bucket (a stream named
|
||||
|
||||
Reference in New Issue
Block a user