Skip to content

Releases: Privatae/cseries

v0.1.12

Choose a tag to compare

@github-actions github-actions released this 27 Oct 07:42

C-Series 0.1.12

This release also includes everything in 0.1.11, which never became the latest release: setting up a Cloud machine takes one button and one passkey, and each row of a Cloud machine's access log says whether a program, an AI agent or a person did it.

Remote access, for network members. Reach your own Host from a phone or a browser anywhere, through the Privatae network, while it keeps running on your machine. Your Host opens the connection to the network's relay and keeps it up; the relay passes the still-encrypted connection to a door on your machine, which ends TLS with a certificate whose key never leaves the machine. Turn it on in Settings, Remote access, after a passkey check; Settings shows the address, each relay link and when the certificate expires. Add a phone from your desktop with a QR code; the phone gets its own passkey. The remote address takes passkey or recovery-code sign-in only, never a password. Remote access needs a network membership, which is not on sale yet.

  • The install now includes the door, a new image (ghcr.io/privatae/cseries-remote-door), pinned by digest like the Host's, on a private network that only the Host is on. It does nothing until remote access is turned on.
  • If the door's setup on your machine is broken, setup stops and says why, and Settings shows the problem.
  • On an install made with npx cseries (Windows, macOS or Linux), a firewall now lets the remote-access door reach only the Host's web page and nothing else, and the door no longer fails its first start in a race over the storage it shares with the Host.
  • Pairing a bastion is refused over the remote address, recovery-code tries have one limit across the whole Host, and the vault's audit log believes a forwarded address only from a proxy you configured.

Desktop. The taskbar no longer loses a tap when the desktop redraws it. Fixed: an app could make its icon run script on the desktop; every icon is now rebuilt from a short list of allowed shapes before it is shown.

C-Series Cloud. A Cloud machine includes a network membership, and its Host now joins the network during setup, with no extra step.

Support requests. The Host checks where a request can go before it writes anything, and never shows a raw error. A Host that is not on the network can prepare a public GitHub issue with addresses, paths, keys and similar details taken out; you read it and post it yourself. A network member can post to the members' board, only after approving the text.

Backups. A member Host keeps its backups in its own folder until the network can store them; before, such a Host could fail every backup.

App Store. No membership needed; Settings and the help pages now say so.

MCP sign-in. Fixed races between moving to another authorization server, a token refresh and a new sign-in that could leave an old server's tokens on a connection. Every wait and name lookup now has a time limit.

Source and documents. A shorter README, a new ROADMAP.md (what is free, what is paid and when the rest is expected) and docs/GUIDE.md; network membership will be $9 a month when it opens. Platform-only and unused code is gone from the public source, and the Host's git skill now keeps other authors' commit trailers.

Also in this release. When the Host reads a web page, a name that points at your own machine or your home network (your router, say) is now refused, as an address written out already was, and the page is fetched from exactly the address that was checked. Addresses in 100.64.0.0/10, which carrier-grade NAT and private overlay networks use, are refused too. The Host's image no longer includes an SSH client; its git works over HTTPS only, as before. An app's icon is always the image file in its bundle, never something the app's own server sends. For remote access, a Host or relay that ends a stream twice, or sends data after ending it, now loses its tunnel instead of slowly using up the other side's memory.

Images (multi-arch, linux/amd64 and linux/arm64):

  • ghcr.io/privatae/cseries:0.1.12 sha256:8993c5c4c6a242806f7bf0c2bbb26c50b7fc4a288ae957b3c0ee15ed4491d1ae
  • ghcr.io/privatae/cseries-postgres:0.1.12 sha256:9e86d8ea56704c4002103a7b3042c87de4b056dce7c421367d84d6993b3eb5e2
  • ghcr.io/privatae/cseries-remote-door:0.1.12 sha256:dc928af1004a62d62b27513a0cb6c2c7325506b9dd54bce15a3fcceffabaf085

Guest images for x64 and arm64 are attached, each with its .sha256: WSL's root filesystem (Windows) and Lima's qcow2 disk (macOS and Linux).
Install with npx cseries@0.1.12.

Changes since v0.1.11:

  • WSL boot test: a runaway in the Host is stopped, nothing outside it is touched, and the Host serves again, whichever process the kernel takes; Caddy and lego run in the door and Caddy listens on 8443
  • Remote access in the Compose install: the door reaches the Host's web port and nothing else; Caddy and lego run in the door, whose image no longer gives them file capabilities
  • Comments on the no-SSH gate and the glyph test name no person and no other repository (and 2 earlier changes)
  • Remote access: a second FIN on a stream, or DATA after one, closes the tunnel
  • read_url on a Host with no proxy: a name that resolves inside is refused and only the address that was checked is dialled; a literal in 100.64.0.0/10 (carrier-grade NAT) is refused like a name; a trailing-dot name is pinned as written
  • The design's bar keeps a button's element when the shell redraws it, so a press is released on the button that was pressed; every app icon is rebuilt from an allowlist before the design receives it, closing a script injection through an app's icon
  • ROADMAP for v0.1.12: your Host from anywhere is built and opens with membership
  • The WSL boot test runs the guest with the release's door too; the guest refuses an update whose Host unit did not take the door's settings; Settings says when the Host is not on its door's network; the Lima guest is checked to share the WSL guest's door units; two boot-test checks hold under load
  • Remote access door: Caddy 2.11.7, so the release vulnerability gate passes
  • Four gates red on main: a Host text that offers, a missed re-export, a stand-in request, a mount(8)
  • Remote access, the Host side: Settings turns it on (after the fresh passkey check Add a phone asks for) and off; the Host makes its own certificate account and a job keeps the certificate renewed; the Host keeps a tunnel up to each relay; the release installs the door on a private network with no way out
  • Remote access, slices 4 and 5: the door on the machine, the remote address, adding a phone; pairing refused over the remote address, a Host-wide cap on recovery-code tries, and the vault audit trusts X-Forwarded-For only from a trusted proxy
  • MCP sign-in: races between a move, a refresh and a new sign-in are closed, and every wait and name lookup is bounded
  • Cloud claim joins the Host to the network with the included membership
  • Support: decide where a request can go before drafting and never show a raw error; a board post goes out only when the owner presses Post it
  • Remote access, slice 1: the Host's outbound tunnel and a reference relay
  • Membership is $9 a month
  • A member Host keeps its backups in its own folder until the network keeps them; the App Store needs no membership
  • Public source: platform-only and dead code removed, git skill keeps trailers
  • README and ROADMAP: what is free, what is paid, and when the rest arrives

v0.1.11

v0.1.11 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 25 Oct 16:12

Images (multi-arch, linux/amd64 and linux/arm64):

  • ghcr.io/privatae/cseries:0.1.11 sha256:b3962655709edb0b37e117d9c38f969794f2c5f3ac2f700a99b0642514e7d021
  • ghcr.io/privatae/cseries-postgres:0.1.11 sha256:cf128a9460864372c435f71c7b42c5cb7c6da24c0a3d5b6c07e07fd938ba3c82

Guest images for x64 and arm64 are attached, each with its .sha256: WSL's root filesystem (Windows) and Lima's qcow2 disk (macOS and Linux).
Install with npx cseries@0.1.11.

Changes since v0.1.10:

  • A release becomes GitHub's latest only after both signatures are uploaded
  • Route policy: the unlock page's claim and sign-in routes are listed, with the ticket that guards them
  • Cloud claim: one button and one passkey; the machine signs the owner in to the Host
  • Cloud machine page: each access-log row says whether a program, an AI agent or a person did it
  • session.py: the tool loop is a method of its own, and the values it shares live on TurnState

v0.1.10

Choose a tag to compare

@github-actions github-actions released this 23 Oct 20:31

Images (multi-arch, linux/amd64 and linux/arm64):

  • ghcr.io/privatae/cseries:0.1.10 sha256:9295d3dbb364dbd7d26ee9981a26a78cc9728faaa311de683071246fe8b66327
  • ghcr.io/privatae/cseries-postgres:0.1.10 sha256:67ee7ba7f9933b44ad40ae25db18aeb97fef2ca066d0c7604741fae3afa81a59

Guest images for x64 and arm64 are attached, each with its .sha256: WSL's root filesystem (Windows) and Lima's qcow2 disk (macOS and Linux).
Install with npx cseries@0.1.10.

Changes since v0.1.9:

  • Nothing creates a directory at import; the runtime gates read nothing of their machine
  • Cloud machines: the customer holds the disk key; the cloud box's comments describe the platform side plainly (and 1 earlier change)
  • Invented test data; an unknown peer state is never active; CI runs the tests; release notes list each change
  • Forge CI: every pull request runs the gates, store-app gates, image build, smoke and CVE scan
  • Delete two unused tool helpers: _ShimRequest and _gh_rate
  • Split runtime/tools.py: each tool's handler moves to the module named by its category
  • Ports from the dev line: session.py stage 2 (reply recorder class, five turn steps as methods)

v0.1.9

Choose a tag to compare

@github-actions github-actions released this 23 Oct 00:50

Images (multi-arch, linux/amd64 and linux/arm64):

  • ghcr.io/privatae/cseries:0.1.9 sha256:c616053a166d984a03d9262233801c29584d1a8fe16c6a971d8c1245a4dea010
  • ghcr.io/privatae/cseries-postgres:0.1.9 sha256:9d8e08222fc2ea8ea6eeeb552de30f5324f58439391746e1d4ad2aba025d163f

Guest images for x64 and arm64 are attached, each with its .sha256: WSL's root filesystem (Windows) and Lima's qcow2 disk (macOS and Linux).
Install with npx cseries@0.1.9.

v0.1.8

Choose a tag to compare

@github-actions github-actions released this 22 Oct 19:58

Images (multi-arch, linux/amd64 and linux/arm64):

  • ghcr.io/privatae/cseries:0.1.8 sha256:1230e2a3c939ea87083f95bd5c8247f9c968e9a3e2f2ba4b106918b47cf6feaa
  • ghcr.io/privatae/cseries-postgres:0.1.8 sha256:460a55ff49f9bc4fc00871a6082d900e9efa80286ae5352f9ea7a0e889fa6b5d

Guest images for x64 and arm64 are attached, each with its .sha256: WSL's root filesystem (Windows) and Lima's qcow2 disk (macOS and Linux).
Install with npx cseries@0.1.8.

v0.1.7

Choose a tag to compare

@github-actions github-actions released this 22 Oct 19:33

Images (multi-arch, linux/amd64 and linux/arm64):

  • ghcr.io/privatae/cseries:0.1.7 sha256:f98b18f302f179c527a15dab8d15b831a8d48cacf47963ecec862e608ca08c8b
  • ghcr.io/privatae/cseries-postgres:0.1.7 sha256:9c2e69f8f3694ef85cdba90d721ef2990df1c4183e2239c67f38e02b21b8e1e9

Guest images for x64 and arm64 are attached, each with its .sha256: WSL's root filesystem (Windows) and Lima's qcow2 disk (macOS and Linux).
Install with npx cseries@0.1.7.

v0.1.6

Choose a tag to compare

@github-actions github-actions released this 21 Oct 21:29

Images (multi-arch, linux/amd64 and linux/arm64):

  • ghcr.io/privatae/cseries:0.1.6 sha256:d15129b8b13e59e599191c9651b56742611ea65d94df37138bf462a4e7565178
  • ghcr.io/privatae/cseries-postgres:0.1.6 sha256:c342e3ad8b7171b91be15c94b89422bacaeea8ccfe6706cd7e5ebd192e568ba5

Guest images for x64 and arm64 are attached, each with its .sha256: WSL's root filesystem (Windows) and Lima's qcow2 disk (macOS and Linux).
Install with npx cseries@0.1.6.

v0.1.5

Choose a tag to compare

@github-actions github-actions released this 21 Oct 14:56

Images (multi-arch, linux/amd64 and linux/arm64):

  • ghcr.io/privatae/cseries:0.1.5 sha256:91fc19c2a7687e9dfaf4173ee6d35ad401872390a620a082788608d1de41ad7b
  • ghcr.io/privatae/cseries-postgres:0.1.5 sha256:6a9e41502f13b518c1d13ca36664c0105358879bd0e21c64f89f6410fcc3e11d

Guest images for x64 and arm64 are attached, each with its .sha256: WSL's root filesystem (Windows) and Lima's qcow2 disk (macOS and Linux).
Install with npx cseries@0.1.5.

v0.1.4

Choose a tag to compare

@github-actions github-actions released this 21 Oct 09:02

Images (multi-arch, linux/amd64 and linux/arm64):

  • ghcr.io/privatae/cseries:0.1.4 sha256:4d91f0c101f8caa43cd5d047cc554249833c2102dc355e00e23a414a760e1cd3
  • ghcr.io/privatae/cseries-postgres:0.1.4 sha256:fa67bd324f6724925ac2e057ec5b9f4367aa44bbe10c416e03fa630a11103a3e

Guest images for x64 and arm64 are attached, each with its .sha256: WSL's root filesystem (Windows) and Lima's qcow2 disk (macOS and Linux).
Install with npx cseries@0.1.4.

v0.1.3

Choose a tag to compare

@github-actions github-actions released this 21 Oct 07:58

Images (multi-arch, linux/amd64 and linux/arm64):

  • ghcr.io/privatae/cseries:0.1.3 sha256:920c712d34b5769b0c20b6fc873969b5eb78de5b04490c01af8ec9007dc59af2
  • ghcr.io/privatae/cseries-postgres:0.1.3 sha256:dff65914782b50a2c1dea835c7d408a8055a21cd70792ac995e588da68fcfa90

Guest images for x64 and arm64 are attached, each with its .sha256: WSL's root filesystem (Windows) and Lima's qcow2 disk (macOS and Linux).
Install with npx cseries@0.1.3.