Tailscale SSH

“It is insanely straightforward and very robust.”

“tailscale allows you to manage remote login at the same layer as connectivity, with better logging and alerting”

“Clearly the ACL methodology provided a false sense of security in this instance in the presence of this bug.”

“sounds like just adding complexity over traditional method of OpenSSH + key distribution”

“This was a decision I made in my old job, seems to be proved correct.”

“Tailscale strongly encourages you to use it in lieu of auth”

“It's handy to open a TTY connection in the browser, or to delegate your tailscale MFA account as remote authentication.”

“It interferes with sshd features and adds to your attack surface.”

“I gather the bug allows people you've explicitly authorized to ssh into some account on your machine”

“I always just disable it and use normal opensshd.”

“Letting Tailscale handle VPN and SSH at the same time is basically once again a single point of failure”

“I fully understand being carefully worded when you need serious brain power just to figure out every claim in the logorrhea”

“I personally feel the impact is still quite big, especially since SSH leads directly to control of the server.”

“Why would I want to swap the well tested auth in ssh for auth managed by tailscale?”

“damn you guys ought to be more careful with such a sensible and important component”

“There is some weaselly language.”

“Makes me think that they could also be investigating a full on unauthorized connection issue”

“I think it's so invasive that they ship this per default.”

“Good that they published an interim mitigation before the full advisory instead of staying quiet until the patch.”

“But why should insecure argument handling bugs (as per your recent SSH bulletin) be found after release ?”

“The advantage of tailscale ssh is that the machine doesn't need to have the ssh port open publicly.”

“Tailscale should not be relying on the random goodwill of others to do random audits of unknown coverage at random intervals.”

“Well, they clearly don't if they have an "insecure argument handling" vulnerability.”

“Feels pretty weird practice to advise upgrading to a non-existent version.”

“This is incredibly bad engineering, on level of a SQL injection”

“This is shocking amateur hour!”

“not to mention root ssh access to hosts. This is a serious issue.”

“I don't see the point of publishing a security bulletin if you are not going to timely push the fix to artifacts on all affected platforms.”

“Otherwise it’s been great for me”

“why not just fix the permission issues instead of restricting users?”

“Arguably that's a more secure starting point than vanilla ssh to publicly accessible machine.”

“replacing a 25-year-old battle-tested codebase with a startup's Go rewrite and then acting surprised when it has bugs”

“It was simple and convenient and access was easily revocable.”

“Convenience for the most part but in general, I agree. I like having it as an option.”

“A proper fix is to use "--" to separate arguments.”

“Glad to see they're still makin' 'em like they used to.”

“using Tailscale SSH is brilliant”

“It already disables ssh encryption because your connection is encrypted with WireGuard anyway.”