Files
Dylan M. Taylor c59b50da54 Require a per-launch token on the --control channel
The control server listens on 127.0.0.1, which host processes (and, in a Flatpak with network
access, the host network) can reach. Each --control launch now generates a random token, writes it
to control-<port>.token in the FigCraft config folder (user-readable only) and requires the first
line of every connection to authenticate with it. figcraft-cli mcp --attach reads the file and
authenticates on every (re)connect; --attach-token FILE names another path, such as a Flatpak's
sandbox config folder. The app disables the channel if it can't write the token.
2026-10-28 13:45:12 -04:00
..
2026-10-25 22:23:40 +01:00