> ...by architecting our infrastructure with security and privacy in mind. The blog and the website loads in so many trackers (reasonable, given metrics are important when you're busy hyperscaling a venture-backed startup), that folks at Tailscale should seriously reconsider positioning themselves as some paragons of privacy. No offence (:
Tailnet Lock
11–20 of 119 posts
Re: Tailnet Lock
#12Re: Tailnet Lock
#13Hey @dang can you update this to "Tailnet Lock"? This is about a feature named "tailnet lock", not a hiring freeze :)
Re: Tailnet Lock
#14Re: Tailnet Lock
#15This solves the #1 concern I had with tailscale. Now I feel comfortable recommending this software to anybody.
It still makes me jittery how much stuff they've packed into the client. The RCE vulnerability in their windows client is pretty strong indicator that things are moving a bit too fast for comfort.
Re: Tailnet Lock
#16Hey @dang can you update this to "Tailnet Lock"? This is about a feature named "tailnet lock", not a hiring freeze :)
Re: Tailnet Lock
#17Why is there a post by tailscale on the front page every single day?
They're not. It's just roughly when the post a new blog entry, which is... usually about once a week? Sometimes it's about new features, sometimes it's about internals which might be helpful for other people to know about (like the previous entry was about internals of the TUN/TAP, and how they managed to speed it up a bunch).
Re: Tailnet Lock
#18This solves the #1 concern I had with tailscale. Now I feel comfortable recommending this software to anybody.
It still makes me jittery how much stuff they've packed into the client. The RCE vulnerability in their windows client is pretty strong indicator that things are moving a bit too fast for comfort.
Re: Tailnet Lock
#19Earlier quoted context omitted.
It still makes me jittery how much stuff they've packed into the client. The RCE vulnerability in their windows client is pretty strong indicator that things are moving a bit too fast for comfort.
Agreed: I do feel the Windows client in particular is a little scary. In general, Tailscale clients feel reasonable, if light; but the Windows client is kind of iffy. There's a bug that I believe still exists where on some machines, it will crash on startup most of the time, seemingly the result of a race condition or other bug where GetLastError returns something unexpected, in a not-very-well maintained Win32 API w…
Re: Tailnet Lock
#20Earlier quoted context omitted.
It still makes me jittery how much stuff they've packed into the client. The RCE vulnerability in their windows client is pretty strong indicator that things are moving a bit too fast for comfort.
Agreed: I do feel the Windows client in particular is a little scary. In general, Tailscale clients feel reasonable, if light; but the Windows client is kind of iffy. There's a bug that I believe still exists where on some machines, it will crash on startup most of the time, seemingly the result of a race condition or other bug where GetLastError returns something unexpected, in a not-very-well maintained Win32 API w…
There were a few things going on with that issue you mentioned; one of them is the way the wrapper library was written, the other was with some stuff in the GUI client that was happening on a background goroutine but shouldn't have been. That should be fixed in the current stable release.
As for the Windows client in general, it is going to be receiving a lot of love over the next few months!