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

Are we happy with the security issues around serving on 0.0.0.0 by default? #107

Closed
kortschak opened this issue Aug 9, 2014 · 2 comments

Comments

@kortschak
Copy link
Contributor

There is likely no problem with gaining control of the server host via otto, but the datastore is writable to anyone.

Perhaps we should serve on 127.0.0.1 by default, and until we implement permission control print a warning when not serving to localhost.

@barakmich
Copy link
Member

Yeah, I can be convinced. I was working on the "really, there should be a firewall and middleware" model, but it's easy enough to run that way (--host=0.0.0.0) if you know what you're doing.

What about 127.0.0.1 for a (safer) default, but no warning if you explicitly set it otherwise; assume the user knows what they're doing and why?

@tyteen4a03
Copy link

Yeah, works; if they want to bind elsewhere themselves, it's not Cayley's problem.

barakmich added a commit that referenced this issue Aug 20, 2014
Switch default to localhost. Fixes #107
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants