News for hackers. Stuff that matters.
Re:Tailscale bug allowed a person to share nodes from other ... by dave_universetf on Tuesday January 17, 2023 @06:49PM (#34421205)
(bulletin co-author) Yeah that bit could have been spelled out more. It's a random 64-bit int.
Re:Tailscale bug allowed a person to share nodes from other ... by bhawks on Tuesday January 17, 2023 @07:08PM (#34421388)
What about the insider risk prospective? A random int64 isn't that hard to guess if you can easily look at a database.
Re:Tailscale bug allowed a person to share nodes from other ... by tptacek on Tuesday January 17, 2023 @07:19PM (#34421496)
If you're looking at a database, you're not guessing. Otherwise: a random int64 is in fact difficult to guess.
Re:Tailscale bug allowed a person to share nodes from other ... by bhawks on Tuesday January 17, 2023 @07:52PM (#34421848)
Exactly - which is why I was asking what is the nature of the insider threat risk if someone did not have to guess.

In a prod deployment who has the rights to see this info without raising too many flags?

Re:Tailscale bug allowed a person to share nodes from other ... by tptacek on Tuesday January 17, 2023 @10:18PM (#34423040)
The database that gives you all the random 64 bit IDs for devices: that's another vulnerability.
Re:Tailscale bug allowed a person to share nodes from other ... by tsujamin on Tuesday January 17, 2023 @08:13PM (#34422103)
(reporter) I spent _a long time_ trying to derive how this value was generated :’)
Re:Tailscale bug allowed a person to share nodes from other ... by fragmede on Wednesday January 18, 2023 @04:36AM (#34424939)
Did you spend any time trying to see if you could steal the values from somewhere else? Given the other breaks in Tailscale, I'd bet there's an info leak somewhere. Deriving it from first principles is hard. Stealing it from somewhere should be easier.
Re:Tailscale bug allowed a person to share nodes from other ... by tsujamin on Wednesday January 18, 2023 @07:03AM (#34425730)
I had a good look for usable info leaks, some GitHub dorking for how the IDs might’ve been generated, but came up naught in the end
Re:Tailscale bug allowed a person to share nodes from other ... by j16sdiz on Tuesday January 17, 2023 @09:26PM (#34422712)
I guess this could be mitigated by not trusting the coordination server? https://tailscale.com/blog/tailnet-lock/
Re:Tailscale bug allowed a person to share nodes from other ... by d4l3k on Tuesday January 17, 2023 @10:17PM (#34423035)
I just tried to set this up and couldn't. Seems like it's invite only with a waitlist :/
Re:Tailscale bug allowed a person to share nodes from other ... by dave_universetf on Tuesday January 17, 2023 @10:45PM (#34423222)
Yeah, we're adding people slowly because decentralized authorities like the one that tailnet lock implements can have nasty failure modes, e.g. some bug that prevents any new addition to the tailnet at all and forces manual recovery on each of your devices separately. So, we're putting miles on it with a little care, and making sure folks who sign up are aware of the current limitations and risks.
Re:Tailscale bug allowed a person to share nodes from other ... by ikiris on Tuesday January 17, 2023 @10:52PM (#34423265)
Oh is that all the problem is?

Anyone with automated deployments and self provisioning should be fine with that risk. I thought it was a lot more premature than this.

Re:Tailscale bug allowed a person to share nodes from other ... by rollcat on Wednesday January 18, 2023 @08:22AM (#34426301)
Good ops is more than automated deployments. Complex systems have complex failure modes.
Re:Tailscale bug allowed a person to share nodes from other ... by tailscaletom on Tuesday January 17, 2023 @11:56PM (#34423573)
If you're excited about tailnet lock and want to get on the alpha sooner rather than later, feel free to drop me an email. As Dave mentioned we are slowly crunching through the waitlist to get some miles in, but I'm also happy to take on enthusiastic testers ahead of that!

You can email me at tom@ (tailscale dot com)