[SERVER-15656] Improve bind_ip handling of badly formatted Internet address numbers Created: 14/Oct/14 Updated: 16/Feb/18 Resolved: 16/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking, Security, Usability |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Hannes Magnusson | Assignee: | DO NOT USE - Backlog - Platform Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | 28qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
bind_ip supports more then standard ipv4 dotted notation, which makes is easy to mess things up. --bind_ip 0 for example represents 0.0.0.0, which will listen to all available interfaces. --bind_ip 3232235521 becomes 192.168.0.1 the risk of supporting the decimal notation is when creating the config files, or passing the argument, a empty variable is in many cases treated as a 0 - so when you thought you were binding to a specific interface - and afterwards it does indeed listen to that interface - you actually are listening to all of them. In addition providing an empty net.bindIp listens to all interfaces. |
| Comments |
| Comment by Hannes Magnusson [ 14/Oct/14 ] | |
|
Also note, explicitly binding to 0.0.0.0 gives the warning:
while bind_ip 0 does not, even though it also results in listening on all ips |