Re:Google Ordered to Identify Who Watched Certain YouTube Vi...
by wutwutwat on Saturday March 23, 2024 @06:11AM
(#39798751)
The world’s largest MITM
[ Parent
| on HN ]
Re:Google Ordered to Identify Who Watched Certain YouTube Vi...
by chgs on Saturday March 23, 2024 @06:20AM
(#39798794)
Tech bros love it. And tailscale. And saas as a whole. Data sovereignty means you can’t be kind by the adtech industry so it’s not cool.
Re:Google Ordered to Identify Who Watched Certain YouTube Vi...
by vitno on Saturday March 23, 2024 @07:53AM
(#39799240)
Calling out tailscale here is odd considering it's peer-to-peer and encrypted.
Re:Google Ordered to Identify Who Watched Certain YouTube Vi...
by chgs on Saturday March 23, 2024 @07:59AM
(#39799264)
With keys controlled by a central entity
Re:Google Ordered to Identify Who Watched Certain YouTube Vi...
by Handprint4469 on Saturday March 23, 2024 @08:40AM
(#39799512)
do you have a source for that?
Re:Google Ordered to Identify Who Watched Certain YouTube Vi...
by mikehotel on Saturday March 23, 2024 @10:43AM
(#39800304)
Tailscale [0] says the private keys never leave the device.
“Security
Tailscale and WireGuard offer identical point-to-point traffic encryption.
Using Tailscale introduces a dependency on Tailscale’s security. Using WireGuard directly does not. It is important to note that a device’s private key never leaves the device and thus Tailscale cannot decrypt network traffic. Our client code is open source, so you can confirm that yourself.”
Re:Google Ordered to Identify Who Watched Certain YouTube Vi...
by sdht0 on Saturday March 23, 2024 @12:51PM
(#39801266)
To add to that, they also provides Tailnet lock [0], which protects from the only way the coordination server can mess with the tailnets, by connecting unauthorized nodes.
Re:Google Ordered to Identify Who Watched Certain YouTube Vi...
by d-z-m on Sunday March 24, 2024 @03:37PM
(#39809702)
That is true as far as it goes, but how does your node learn the public keys of the other nodes in your tailnet? My understanding is that they are provided by the coordination server, so you have to trust that the public key the coordination server gives you is actually the one for your peer device.
Tailnet lock helps mitigate this by requiring that node public keys are signed by a trusted signing node, but it isn't bulletproof.
Re:Google Ordered to Identify Who Watched Certain YouTube Vi...
by Aerbil313 on Monday March 25, 2024 @12:41AM
(#39812919)
Public key cryptography doesn’t work like that. If you were given wrong public keys you wouldn’t be able to connect to start with.
Re:Google Ordered to Identify Who Watched Certain YouTube Vi...
by d-z-m on Monday March 25, 2024 @09:08AM
(#39815818)
> Public key cryptography doesn’t work like that
Like what? I'm saying both sides of the connection would be given the wrong public keys by the coordination server. The private keys of which would be held by a MITM.
Re:Google Ordered to Identify Who Watched Certain YouTube Vi...
by j45 on Saturday March 23, 2024 @12:20PM
(#39800989)
Not sure what the issue is with Tailscale, especially since you can self-host Headscale server locally to get the same effect.
Re:Google Ordered to Identify Who Watched Certain YouTube Vi...
by chgs on Sunday March 24, 2024 @10:19AM
(#39807381)
Headscale is fine. With tailscale they control the deployment of public keys to devices, and can thus deploy anything they want to.
Re:Google Ordered to Identify Who Watched Certain YouTube Vi...
by j45 on Sunday March 24, 2024 @02:04PM
(#39808947)
Good to know.
Have they ever deployed anything they want to devices?
Re:Google Ordered to Identify Who Watched Certain YouTube Vi...
by brokenmachine on Monday March 25, 2024 @12:23AM
(#39812849)
The direction you're heading in sounds very similar to the arguments that may have been made pre-Snowden about mass-surveillance.