News for hackers. Stuff that matters.
Re:What The Rails Security Issue Means For Your Startup by WestCoastJustin on Thursday January 31, 2013 @01:44PM (#5146542)
Note: From a sysadmin standpoint http://localhost:3000 commonly refers to http://127.0.0.1:3000. When running "rails server" locally in development mode, you actually get http://0.0.0.0:3000. These are not the same! 127.0.0.1 means that "rails server" can only be accessed from your local machine, where 0.0.0.0 means, it can be accessed on any address your computer is listening on. If you are on a local intranet, say at the office, then you probably have a 127.0.0.1 and 192.168.x.x interface, then everyone can access it via 192.168.x.x, or god forbid a public IP ;)
Re:What The Rails Security Issue Means For Your Startup by patio11 on Thursday January 31, 2013 @01:58PM (#5146627)
Again, even if your development box is being physically protected by the Swiss guard with a firewall that sprung from Donald Knuths' forehead with the River Styx separating it from all inbound connection attempts, it won't even matter, because you run a browser on your development box, that browser can always connect to your development box, and that browser can be instructed to pass malicious input to your development box if you do innocuous things with it like e.g. viewing web pages on the public Internet.
Re:What The Rails Security Issue Means For Your Startup by WestCoastJustin on Thursday January 31, 2013 @02:08PM (#5146685)
Yeah, I get it. I guess I'm making an additional point, that anyone can have direct access to the development environment via any address your machine is listing on -- not just localhost.