+1 for native TLS on the server listener. My use case is Linked environments between machines on my lab network (172.16.x).
Linking fails today with:
| 1 | PeerLinkError: This environment could not reach <machinename>: http://172.16.16.xxx:3773/ is plain http, which would send the link's credentials unencrypted. Use its https address, or its Tailscale address. |
I can issue certs to these machines from my own CA and reach them by DNS name, so a bring-your-own cert option would solve this cleanly. I would rather not run a reverse proxy or add Tailscale on every box just to get TLS. Something along the lines of what #26428 proposed:
T3CODE_TLS_CERT/T3CODE_TLS_KEY(plus matchingt3 serveflags and a desktop setting) so the server listens on https directlyt3 pairand the advertised routes use the https address when TLS is on- Peer links trust the OS store or
NODE_EXTRA_CA_CERTSfor private CAs
At the moment the only options are Tailscale, T3 Connect, an SSH tunnel or a reverse proxy, and each one adds another moving part to run and maintain.
Related: #26840 tracks the peer link refusal itself.
Happy to test a build if that helps.