6 Commits

Include renames

Author	SHA1	Message	Date
justme	904ea2b0ae	refactor: remove the runtime binary binding; every release registration path verifies the CI signature [CI] ... The hash a node reports about itself cannot be trusted (a swapped binary can copy the old hash), so the runtime binding only caught files that were replaced by something that did not lie. Provenance stays where it can be verified: the signed release manifest (digest) and the signed SHA256SUMS. - Remove BinaryBindingService, the node_bindings table (schema v15 drops it), BinaryPolicy, the handshake hash/manifest fields and the admin binary column. - Drop the per-platform "binaries" list from the release manifest, the hash scripts and the updater's installed.manifest copy. - ReleaseService.PublishAsync now verifies the release signature, so the admin POST /releases route is no longer an unsigned path; tests sign with a test key. - Docs: section 16 explains why the runtime check is gone.	2026-10-08 18:30:05 +08:00
justme	4841f7b15b	feat: bind each node to the binary it runs at its first handshake; refuse changes that are not in a CI-signed manifest [CI]	2026-10-08 05:39:13 +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	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	84f9d211bc	backend: require confirmation for signed channel updates [CI]	2026-10-07 12:57:20 +08:00
justme	2e146d4da7	refactor!: rename the project from Monitor to MoShiro [CI] ... 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