Repository navigation
fir 1.10.3
Highlights
Fixed
- The remote tools now detect that the target IS this host and run locally. An agent on a fleet box asking for its own machine by ssh alias got
Permission denied (publickey)— a host's key is not in its ownauthorized_keys— and then burned turns, or "fixed" it by installing a loopback key.rexec,rjob,rputandrgetnow drop the ssh prefix and run the identical supervisor argv locally under an sshd-shaped scrubbed environment ($HOME cwd, bare PATH, noTMUX/FIR_*/SSH_AUTH_SOCK, the passwd login shell), disclosing it aslocal: truein the envelope;rhostsmarks the entryself: true. The identity test never compares hostnames —--net=hostcontainers, cloned VMs and stale reverse lookups all make that signal worthless. Insteadssh -Gresolves the target, aProxyCommand/ProxyJump, a non-22 port or a non-local target user bail straight back to ssh, and otherwise each resolved address isbind()-tested, which succeeds only for an address configured on a local interface.via_ssh=True(orFIR_REMOTE_FORCE_SSH=1) forces the wire for the one case transparency would lie about — probing reachability or auth; an ssh call that does fail withauth_failedagainst a lookalike name now carries a hint instead of a dead end.ip_nonlocal_bind(routinely on for keepalived/anycast) makes every bind succeed and so bails to ssh rather than classifying the whole fleet as self, and the local environment suppliesXDG_RUNTIME_DIR/DBUS_SESSION_BUS_ADDRESS— whichpam_systemdprovides over ssh — sodetach=Truestill gets a transientsystemd-run --userunit rather than silently degrading to a forked process group.rtmuxstays on ssh and refuses a self-host outright, sincesend-keysinto the local tmux server can land in the agent's own pane.
Changed
- Model catalog regenerated: removed 4 aggregator model(s); 16 model(s) with changed pricing/limits.
Full Changelog: v1.10.2...v1.10.3