Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open source server #498

Open
toonsevrin opened this issue Jun 22, 2020 · 6 comments
Open

Open source server #498

toonsevrin opened this issue Jun 22, 2020 · 6 comments
Labels
L2 Few Likelihood P3 Can't get started Priority level T6 Major usability Issue type

Comments

@toonsevrin
Copy link

toonsevrin commented Jun 22, 2020

I think Tailscale is a beautiful project, it would be even more perfect if the server was open-source.

Are there ever going to be any plans for this?

If this is not planned, I'd like to propose a zero-trust extension, to mitigate the risk of the tailscale platform being compromised.

The simplest version would be tailscale up <private signing key>. All servers publish their status (interface, public keys...) periodically, signed by this key. This way a compromised tailscale admin cannot forge anything.

@bradfitz
Copy link
Member

bradfitz commented Jun 22, 2020

Thanks for filing.

When we did our initial open source release earlier, the server was in no way releasable (full of hard-coded strings, URLs, customer policies, etc). It's getting better, but we're still planning a major protocol change before we'd want to release anything ourselves. We'd also have to decide which parts to release & how to refactor the code to make it more modular. It's a lot of work (and ongoing support) and we have tons of other priorities at the moment.

But on Twitter the other day, an open source server ("Headscale") was announced: https://twitter.com/juanfont/status/1274652518128201728 ... maybe that'd work for you?

As for a key that proves the server hasn't been compromised, yeah... we'd been discussing such a thing. Can you file a separate bug about that? (It's hard to have a single bug tracking separate things)

@toonsevrin
Copy link
Author

toonsevrin commented Jun 22, 2020

@bradfitz that's amazing to hear. I understand the separation of priorities.

But you do make a fair point with regards to headscale: Having a community edition would be wholesome.

This way you only have to worry about tidying up your client-server interface and the OS free labor market will take care of the rest.

#499 for the security related topic.

@fti7
Copy link

fti7 commented Jun 16, 2021

One Year later. Any update on this? :-) would be awesome if you opensource it

@boehs
Copy link

boehs commented Feb 6, 2022

Would subscribe to personal pro if it was open source, FWIW

@ItalyPaleAle
Copy link

ItalyPaleAle commented Feb 6, 2022

Personally, I'd pay for this to be self-hostable, even if not OSS.

@boehs
Copy link

boehs commented Feb 6, 2022

Personally, I'd pay for this to be self-hostable, even if not OSS.

Not a fan of this, what about selling binaries? Would be the best of both worlds, open to contribute but still a commercial product

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
L2 Few Likelihood P3 Can't get started Priority level T6 Major usability Issue type
Projects
None yet
Development

No branches or pull requests

6 participants