What do you mean "at startup"? I click "start service" in my service control panel, and then... where would that warning be displayed?
Seriously though, there are many ways to solve this problem, binding to private IPs is one way to do it, but not necessarily the best way, and definitely not the only way. If you run memcached you should realize that there's no security whatsoever on it, and leaving it open to the internet at large is a pretty stupid idea. How to best secure it depends greatly on the local circumstances, and that is not something memcached itself should start second-guessing the local admins about. /Henrik On Sat, Aug 7, 2010 at 14:09, samwyse <[email protected]> wrote: > I've just now suggested this on Slashdot: At startup, issue a big > multi-line warning if the IP addresses that are getting bound aren't > on the loopback address or a private internet. The private internets > are defined in RFC 1918 as: > > 10.0.0.0 - 10.255.255.255 (10/8 prefix) > 172.16.0.0 - 172.31.255.255 (172.16/12 prefix) > 192.168.0.0 - 192.168.255.255 (192.168/16 prefix) >
