justme
fbda9487d5
feat: serve the web apps from the Backend (embedded, allow-listed, no filesystem access) so passkeys bind to the panel's own domain [CI]
ci/woodpecker/push/main-amd64-build Pipeline failed
2026-10-08 04:09:40 +08:00
justme
a2f88a344b
feat!: genesis-pinned operator set, server identity with an encrypted control link, key-less join codes; release key continuity
...
ci/woodpecker/tag/gitea-release Pipeline is pending
ci/woodpecker/tag/linux-release Pipeline failed
ci/woodpecker/tag/windows-release Pipeline was canceled
Join codes need no passkey touch and carry only public values (genesis
fingerprint, owner credentials, installer hashes). Nodes pin the genesis and
owners at enrollment and only follow passkey-signed operator set versions.
The panel's server key is listed in the set; pinned nodes require its
signature and run the control link under AES-256-GCM. Password sessions carry
no capabilities. The updater adopts a next_key from a signed manifest.
Bump version to 0.2.0. [CI SKIP]
2026-10-08 03:21:44 +08:00
justme
9bb6841dce
feat: pinned agents and probes only accept peers carrying the operator's proof; the panel ships the signed operator chain with the rosters [CI SKIP]
2026-10-07 23:24:33 +08:00
justme
fc2bbdcc6d
feat: operator trust root: passkey-signed operator set, signed join codes, nodes verify and pin the chain at enrollment [CI SKIP]
2026-10-07 23:19:59 +08:00
justme
36f9816f40
test: allow the installer manifest paths in the OpenAPI layout check [CI SKIP]
2026-10-07 23:02:50 +08:00
justme
310b2b5b19
feat: the one-line installer verifies the CI-signed release manifest and pulls the image by digest [CI]
2026-10-07 23:01:45 +08:00
justme
a19e6548d3
feat: trust forwarded client addresses only from configured proxies (rate limit, audit, SSE) [CI]
...
Docs: access.md covers the missing node-side Backend identity and the hash-first install flow.
2026-10-07 22:51:44 +08:00
justme
ff45ad086e
feat!: sensitive actions need a fresh passkey touch (elevation windows), plus login page hint cleanup [CI]
2026-10-07 22:29:24 +08:00
justme
1379b8c7cb
feat: audit log of admin writes, sign-ins and key creation, with an audit tab [CI]
2026-10-07 22:17:52 +08:00
justme
359313a57b
feat: record who created join codes and who added each node [CI]
2026-10-07 22:12:15 +08:00
justme
6385c1b9a3
feat: sign in with a passkey (WebAuthn, ES256, discoverable credentials) and manage your passkeys [CI]
2026-10-07 21:57:19 +08:00
justme
ddb6608e32
feat!: capabilities replace API token scopes; every admin endpoint declares one, with a picker UI [CI]
2026-10-07 20:56:36 +08:00
justme
af2962fc58
feat: one-line install for agents and probes from one shared script (curl | bash, zsh, PowerShell) [CI]
ci/woodpecker/push/main-amd64-build Pipeline was successful
2026-10-07 20:02:38 +08:00
justme
b99b95c738
feat!: pre-handshake knock on the agent TCP ports; probes get the agent certificate public key [CI]
ci/woodpecker/push/main-amd64-build Pipeline was successful
2026-10-07 18:56:40 +08:00
justme
f03988d68b
feat: detect an agent's public IPv4 and IPv6 addresses automatically, manual values still win [CI]
ci/woodpecker/push/main-amd64-build Pipeline was successful
2026-10-07 18:12:17 +08:00
justme
a9f562441f
feat!: probes generate their own keys and enroll with a join token; node and peer keys are separate [CI]
ci/woodpecker/push/main-amd64-build Pipeline was successful
2026-10-07 16:57:34 +08:00
justme
1ff847e45a
feat: declare every protocol method's direction and enforce it in the router; add the zero-trust design [CI]
...
ci/woodpecker/push/main-amd64-build Pipeline was successful
Methods, roles and binary channels are declared in one table per plane (node and peer). RpcRouter checks direction, kind and role when handlers are registered, when messages arrive (fleet_protocol_violation, disconnect after repeated violations) and before sending. NodeConnection is split by responsibility.
2026-10-07 16:17:02 +08:00
justme
9bcef56497
feat: daily node restart controlled from the admin, connect timings as a default line task [CI]
...
ci/woodpecker/push/main-amd64-build Pipeline was successful
Agents and Probes exit in order at a configured time (default 04:30 UTC+8, switch and time zone in the admin settings) and the service manager starts them again; a local restart_at or MOSHIRO_RESTART_AT wins. The connect kind (TCP connect and TLS handshake timings) is now a default continuous line template, with a section on the line page.
2026-10-07 14:56:50 +08:00
justme
84f9d211bc
backend: require confirmation for signed channel updates [CI]
ci/woodpecker/pr/verify Pipeline failed
ci/woodpecker/pr/web-build unknown status
2026-10-07 12:57:20 +08:00
justme
0eda0600cc
shared: add independent IPv4 and IPv6 collection [CI]
ci/woodpecker/pr/verify Pipeline was successful
ci/woodpecker/pr/web-build Pipeline was successful
2026-10-07 11:44:01 +08:00
justme
c974a7dddb
docs: merge the Fleet docs into backend/fleet/README.md, add TODO.md, unify the Backend compose, fix stale references [CI SKIP]
2026-10-07 03:36:34 +08:00
justme
ef75c9f510
fix: API tokens use the mos_ prefix [CI]
ci/woodpecker/push/main-amd64-build Pipeline was successful
2026-10-07 02:31:32 +08:00
justme
2e146d4da7
refactor!: rename the project from Monitor to MoShiro [CI]
...
ci/woodpecker/push/main-amd64-build Pipeline was successful
Namespaces, assemblies, solution, binaries, images, systemd units, config paths, environment variables, protocol methods and the Linux user are all renamed. Breaking: existing databases, node identities and installed units must be recreated.
2026-10-07 02:03:25 +08:00
justme