Re:Add ability to choose a custom coordination server
by yencabulator on Monday August 15, 2022 @07:18PM
(#32476830)
I think the Tailscale part that actually knows what auth keys look like is proprietary, but at least for Headscale they seem to be just unguessable database row identifiers: https://github.com/juanfont/headscale/blob/ade4e23e149e7846b...
Nothing in the Tailscale design has ever pointed to features that would guard your infrastructure from them.
Re:Add ability to choose a custom coordination server
by stavros on Monday August 15, 2022 @02:35PM
(#32473526)
Yeah, they control this setting so they can just disable it, or override it.
Since Headscale exists, though, this problem is solved quite neatly.
Re:Add ability to choose a custom coordination server
by yencabulator on Monday August 15, 2022 @04:36PM
(#32475027)
You can't generate a secret with a webapp they control without them controlling the secret too.
But it still seems like they could flip that feature off if they got compromised. To remedy that, feels like they could support a preshared secret that they don't control / see being shared as a first step: https://tailscale.com/kb/1099/device-authorization/#generate...