11 Commits

Include renames

Author	SHA1	Message	Date
justme	ad5efc62ff	agent: unify listening and dialing with directed mutual measurements ... Replace Probe with Agent across node runtime, Fleet contracts, backend state, API and storage. Report incoming sessions and outgoing link health through each Agent uplink, and retain directed link controls and retry. Update protocol fixtures and end-to-end coverage for the unified model; accept requested cancellation during the Fleet timeout test cleanup.	2026-10-21 11:55:36 +08:00
justme	a7ebf61551	[CI] [SKIP TESTS] Add detailed Probe-Agent connection diagnostics	2026-10-20 19:12:11 +08:00
justme	d95acc6575	refactor(link): bound every teardown and handler wait behind one helper [CI]	2026-10-19 10:07:36 +08:00
justme	1a3feddc9d	fix(link): actually bound the server connect with a timeout [CI]	2026-10-18 03:30:43 +08:00
justme	2ae63653c4	feat: the node itself requires an owner passkey (shared by agent and probe) and reports it; the panel derives the account and passkey it is bound to [CI]	2026-10-08 06:15:07 +08:00
justme	a2f88a344b	feat!: genesis-pinned operator set, server identity with an encrypted control link, key-less join codes; release key continuity ... 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	321cacac32	feat: operator trust chain library (passkey-signed operator set, grants and code-key bindings) [CI SKIP]	2026-10-07 23:09:09 +08:00
justme	b99b95c738	feat!: pre-handshake knock on the agent TCP ports; probes get the agent certificate public key [CI]	2026-10-07 18:56:40 +08:00
justme	1ff847e45a	feat: declare every protocol method's direction and enforce it in the router; add the zero-trust design [CI] ... 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] ... 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	26620707a0	chore: initial project import	2026-10-04 21:46:39 +08:00