4 Commits

Include renames

Author	SHA1	Message	Date
mrambossekandClaude Fable 5	3cdbccee18	cli: serving is an explicit verb; no arguments prints usage ... Running an unfamiliar binary by name should tell you what it does, not bind a dozen ports and start answering the internet. --serve (or --daemon) now does that, and a bare invocation prints usage and exits 2 - non-zero on purpose, so a service manager sees a failure rather than concluding the server ran and finished cleanly. The hazard this creates is worth spelling out, because it bites once and silently: three places started the binary with no arguments - the systemd unit, the unit template, and the Dockerfile - and --self-update replaces the binary but never the unit. A routine update would therefore leave a service that cannot start, discovered whenever the host next rebooted. So the updater repairs it: after replacing the binary it appends --serve to an ExecStart that has no flags, but only in a unit this program wrote (identified by its description). Editing an operator's hand-written unit would be overreach; leaving ours broken would be negligence. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-08-01 17:42:20 +02:00
mrambossekandClaude Opus 5	43e1ba778a	server: multi-address listeners, env-file config, self-update timer + checksums ... - Comma-separated ECHOLOT_{CONTROL,UDP,TCP}_LISTEN; one listener/socket per address. Explicit binds matter on multi-IP hosts (a wildcard would also claim the SSH-only management address) and per-address UDP sockets are the substrate stun-5780 needs. - systemd unit reads /etc/echolot-server.env (seeded once, never overwritten); --install-systemd with --self-update-api also installs a daily randomized update timer that try-restarts the service. - selfupdate: SHA256SUMS verification is now mandatory before the atomic replace (integrity, not authenticity — signing still TODO). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-07-31 19:40:36 +02:00
mrambossekandClaude Opus 5	b7658a6777	server: selfupdate must normalize namespaced tags; build-status: pipeline green ... Release tags are server-v1.2.3 but binaries are stamped v1.2.3 — the raw comparison would re-download the current version on every check. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-07-30 16:38:08 +02:00
mrambossekandClaude Opus 5	8a80026d49	server: Go skeleton — control plane, UDP data plane, Docker + systemd modes ... Pure stdlib. Implements the spec's core: enrollment (single-use tokens), profile (SPKI pin, only real capabilities advertised), sessions with the §2.4 HKDF-SHA256 key schedule; UDP data plane with the 32-byte ELT1 header, 4-byte HMAC gate, 1024-wide anti-replay window, ECHO_RESP with observation block, TIMESYNC, and the §3.4 anti-amplification cap. Wire format has tests (roundtrip + silent-drop cases); enroll→profile→session smoke-tested live. Modes: container (autodetect /.dockerenv|/run/.containerenv|cgroup, or --docker/ECHOLOT_DOCKER=1; config via ECHOLOT_* env; distroless image; network_mode host required — Docker NAT would falsify observed sources) and native (--install-systemd/--uninstall-systemd with a hardened unit, opt-in --self-update from Gitea releases; refused in containers). CI: tests on any server/ push; server-v* tags build+push the image to the Gitea registry and attach linux amd64/arm64 binaries + SHA256SUMS to a release — the artifact self-update consumes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-07-30 13:09:08 +02:00