News for hackers. Stuff that matters.
Re:Tailscale Traces Database Corruption to 16y/o SQLite WAL-... by inigyou on Wednesday August 12, 2026 @10:33PM (#49281183)
How about having devices generate and not share their private keys, instead?
Re:Tailscale Traces Database Corruption to 16y/o SQLite WAL-... by waterTanuki on Thursday August 13, 2026 @12:39AM (#49281851)
That's already how it works at the data-plane layer. I'm talking about the control-plane layer where tailscale needs to maintain a server that gets its state from somewhere (they need to know where to route your data, what your permissions ACLs are, device names, etc.). If everyone shared the same db cluster accessed over the network there is a real risk of an accident leaking the encryption keys (of the database itself, not your tailnet) to the db they would have to maintain, and leaking semi-sensitive info like these device names and IP addresses. Using sqlite means each tailnet's metadata is isolated to the container running it.
Re:Tailscale Traces Database Corruption to 16y/o SQLite WAL-... by inigyou on Thursday August 13, 2026 @05:06AM (#49283368)
Is it? They're backing them all up to S3 so what if the S3 keys leak?
Re:Tailscale Traces Database Corruption to 16y/o SQLite WAL-... by waterTanuki on Tuesday August 18, 2026 @01:47AM (#49341744)
It's harder to leak multiple S3 keys than a single postgres key.