127.0.0.1 by default vs 0.0.0.0
See original GitHub issuecode-server
version: v1.604-vsc1.32.0- OS Version: macOS 10.14.4 (18E226)
Description
It has been discussed that using 127.0.0.1 might be better than using 0.0.0.0 for the default host for security reasons when running code-server. A user should have to explicitly set 0.0.0.0 as the host if they want to use it with the -h
flag
Steps to Reproduce
- Start code server
INFO Starting webserver... {"host":"0.0.0.0","port":8443}
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
What's the difference between 127.0.0.1 and 0.0.0.0?
In the context of a route entry, it usually means the default route. In the context of servers, 0.0.0.0 means "all IPv4 addresses...
Read more >Difference between 127.0.0.1 and 0.0.0.0 - GeeksforGeeks
It is a loopback address(localhost address). It is a non-routable address. ; This address is used to connect to the same machine or...
Read more >What is the difference between 0.0.0.0, 127.0.0.1 and localhost?
127.0.0.1 is normally the IP address assigned to the "loopback" or local-only interface. This is a "fake" network adapter that can only ...
Read more >What is the Difference Between 127.0.0.1 and 0.0.0.0?
127.0.0.1 is the loopback address (also known as localhost). · 0.0.0.0 is a non-routable meta-address used to designate an invalid, unknown, or ...
Read more >What's the difference between ip address 0.0.0.0 and 127.0.0.1?
0.0.0.0 is a broadcast to any network. You can not assigne to any host or devices. · And 127.0.0.1 is a loopback address...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think the overwhelming use case of
code-server
would be to access it over the internet, not from the same machine. If this is a security issue why not just remove the--no-auth
flag from the docker one-liner?Yea I agree it would be a bad idea to change the behaviour. I guess what we really want is to listen on localhost if the
--no-auth
or--allow-http
flags are passed as at that point listening on 0.0.0.0 is potentially insecure.