You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(cli): keep the Remote Control link token-free and make the relay configurable
The tunnel client already adds the bearer token to every request it
replays against the local server, so the link needs no credential. Drop
the token fragment that was leaking the machine-wide server token into
the terminal, the QR image on disk, and the remote browser's URL bar.
Add --relay-origin and PYTHINKER_CODE_REMOTE_CONTROL_RELAY: this build
ships no relay, so the relay had no way to be set outside tests. Restrict
the lock file and the QR image to owner-only permissions.
Copy file name to clipboardExpand all lines: docs/guides/remote-control.md
+10-2Lines changed: 10 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,11 +24,19 @@ The terminal prints a QR code, a link, and the path of a PNG copy of the QR code
24
24
25
25
## Security
26
26
27
-
The link grants control of this machine. It carries the access token in its URL fragment, which the browser keeps to itself and never sends to the relay. Do not share the link or the QR code.
27
+
The link grants control of this machine. Do not share the link or the QR code.
28
+
29
+
The link carries no access token. Requests reach the local server through the tunnel, and the Pythinker Code process on this machine adds the bearer token to each one, so the token never leaves this machine.
28
30
29
31
## Relay
30
32
31
-
Traffic reaches the remote device through a relay. Set `relayOrigin` to point at your own relay; the default is `https://code-rc.pythinker.com`.
33
+
Traffic reaches the remote device through a relay. Point Remote Control at your own relay with `--relay-origin`:
0 commit comments