Repository navigation
Replies: 2 comments
|
Closing as a duplicate of #26431, which tracks the same request. Please follow along there. |
0 replies
|
I assumed it would be automatic but I can't see the references I made to this discussion from #37309 to resolve this discussion |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
With Network access on, the server listens on
0.0.0.0:3773over plain HTTP and the WebSocket runs overws://. Anyone who can see LAN traffic (a shared office network, hotel Wi-Fi, one box doing ARP spoofing) reads every prompt, diff, file and terminal line, and the session token with them. Agents often run at Full access, so that token is effectively a shell on the host.What I checked on 0.1.3 (Windows desktop):
server-runtime.jsonshows"host":"0.0.0.0";desktop-settings.jsonhas"serverExposureMode":"network-accessible".node:httpand nothing for TLS. I found no cert or key setting among theT3CODE_*variables.:3773fails, and a plainGET /returns 200.GET /api/orchestration/shellgets 401, from loopback too. Auth isn't the problem here. The transport is.The encrypted routes today are Tailscale Serve, T3 Connect, or a reverse proxy you build yourself. The first two depend on an outside service, and I'd rather not need one for two machines on the same desk. The DIY proxy works: I have Caddy in front with a self-signed cert, and the server already honours
X-Forwarded-Proto(fixed in #328). But everyone who wants this ends up building the same thing, and the plaintext port stays reachable until they add a firewall rule too.What I'd like:
T3CODE_TLS_CERT/T3CODE_TLS_KEY, plus matchingt3 serveflags and a desktop setting. The server then listens withhttps.createServeron the same port, and the client switches towss://.T3CODE_HOME.sha256:<fingerprint>in the pairing link next to the token, and have the desktop and mobile clients accept exactly that cert for that environment (in Electron, viacertificate-errororsetCertificateVerifyProc). Right now the desktop main process has nocertificate-errorhandler, so a self-signed cert only works after each client box imports it into its user Root store.Related: #17965 (cert approval in the browser panel, a different surface), #22214 (MCP OAuth clients refuse plain-HTTP LAN addresses), #26421 (T3 Connect hidden over plain HTTP), #21286 (end-to-end encryption for T3 Connect), #13582 (
t3 pair --base-url, which is what makes the proxy route usable now).Written up with Claude Code from a session on the affected machine.
All reactions