top | item 47065622 (no title) nickburns | 11 days ago Zerconf ≠ zero trust. The difference could not be more material in this context. discuss order hn newest tonyplee|11 days ago If both sides of your ssh tunnel (pub,private keys) are under your control, in theory, that's "zero trust".Unless one considers the meta data such as src/dest IP are visible to Tailscale sw.Right? nickburns|11 days ago 'Zero trust' has a technical definition that's not really relevant here. See: https://en.wikipedia.org/wiki/Zero_trust.The concept is separate from 'zero config' (https://en.wikipedia.org/wiki/Zero-configuration_networking), which Tailscale's low technical barrier to entry evokes.
tonyplee|11 days ago If both sides of your ssh tunnel (pub,private keys) are under your control, in theory, that's "zero trust".Unless one considers the meta data such as src/dest IP are visible to Tailscale sw.Right? nickburns|11 days ago 'Zero trust' has a technical definition that's not really relevant here. See: https://en.wikipedia.org/wiki/Zero_trust.The concept is separate from 'zero config' (https://en.wikipedia.org/wiki/Zero-configuration_networking), which Tailscale's low technical barrier to entry evokes.
nickburns|11 days ago 'Zero trust' has a technical definition that's not really relevant here. See: https://en.wikipedia.org/wiki/Zero_trust.The concept is separate from 'zero config' (https://en.wikipedia.org/wiki/Zero-configuration_networking), which Tailscale's low technical barrier to entry evokes.
tonyplee|11 days ago
Unless one considers the meta data such as src/dest IP are visible to Tailscale sw.
Right?
nickburns|11 days ago
The concept is separate from 'zero config' (https://en.wikipedia.org/wiki/Zero-configuration_networking), which Tailscale's low technical barrier to entry evokes.