Skip to content

docs: document secure Mac control path - #1246

Open
vesselsystems wants to merge 9 commits into
kunchenguid:mainfrom
vesselsystems:fm/shadowbyte-mac-control-path
Open

docs: document secure Mac control path#1246
vesselsystems wants to merge 9 commits into
kunchenguid:mainfrom
vesselsystems:fm/shadowbyte-mac-control-path

Conversation

@vesselsystems

Copy link
Copy Markdown

Summary

  • Add secure Mac-to-server access documentation using authenticated SSH/Tailscale access and explicit loopback forwarding.
  • Keep infrastructure placeholders in public documentation; exact host, user, launcher, and Lavish session values remain private.
  • Document Pi as the sole Firstmate primary, the authoritative named Herdr session firstmate, and supervised-crewmate restrictions.
  • Harden the Lavish tunnel pattern with an explicit Mac loopback bind and isolated SSH forwarding settings.
  • Separate maintainer verification evidence from the operator-facing guide.

Validation

  • Automated review completed.
  • Focused SSH configuration and loopback-forwarding checks completed against an ephemeral local SSH harness.
  • Documentation verification completed, including busy-port and ExitOnForwardFailure behavior.
  • The live Lavish listener was not restored or disturbed; the bounded incomplete-live-proof limitation was accepted.
  • ShellCheck was unavailable. No shell files were changed by this pull request.

Safety

  • No credentials, tokens, private Tailscale values, or live session identifiers were committed.
  • No SSH, Tailscale, firewall, service-bind, or active runtime settings were changed.
  • The public guide does not expose the server's private infrastructure values.

Document how a laptop attaches to a server-resident Firstmate and reaches
its loopback-only web tools without publishing anything.

- docs/remote-access.md (operator-current) owns the Mac-side SSH config
  entry, the attach command, the Lavish forward, the reusable forward
  pattern, the forwarding-safety classification, and troubleshooting.
- docs/verification/remote-access.md (maintainer-verification) records the
  reusable client-side evidence: config expansion, a forward reaching a
  loopback-only service, and ExitOnForwardFailure behavior against a busy
  local port, all against an ephemeral loopback SSH server.
- Classify both surfaces, add the owner pointer, and route them from README.

The tool's own CLI already prints current session URLs, so no wrapper
script is added for that lookup.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e2635f2764

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/remote-access.md
Comment on lines +115 to +118
Host shadowbyte-agent
HostName <server-host>.<tailnet>.ts.net
User <server-user>
ForwardAgent no

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Include the OpenSSH identity in the tunnel config

Captain, on the documented host-OpenSSH path, this minimal file omits IdentityFile while -F selects it as the alternative per-user configuration file, so a key configured only in the normal ~/.ssh/config is ignored. If that key has a non-default filename and is not loaded into the agent, the attach can work while this tunnel fails authentication despite the public key already being installed; include an identity placeholder or explicitly require -i/agent loading.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant