Join 3,416 readers in helping fund MetaFilter (Hide)


Local Apache server + public wireless = problem?
April 5, 2009 11:41 AM   Subscribe

I have a new EeePC 1000HE with Windows XP, which I want to use for both web development and casual web browsing. Are there security issues with installing Apache and PHP on a machine that is also used to access public wireless internet? If so, what steps can I take to make my netbook more secure?
posted by oulipian to Computers & Internet (5 answers total)
 
If you're concerned about other users of the same wireless network being able to access the web server on your computer, set it up so it's only listening on the loopback interface (localhost -- 127.0.0.1) and it'll only be accessible from your own computer.
posted by FishBike at 11:56 AM on April 5, 2009


I came in here to provide the precise answer that Fishbike did. Loopback is your friend in a situation like this.
posted by deadmessenger at 11:58 AM on April 5, 2009


PHP is not known for being particularly secure, but running Apache and PHP is only adding a negligible security risk considering that the host OS is XP. No snark or MS bashing, your time worrying about security is much more fruitfully spent looking in to XP than Apache or PHP. And yeah, only allowing access from 127.0.0.1 eliminates all Apache/PHP related risk.
posted by idiopath at 12:31 PM on April 5, 2009


Thanks for the recommendations!
posted by oulipian at 8:16 PM on April 5, 2009


Most firewalls should block most/all inbound connections by default (I'm pretty sure the built-in XP one will block inbound port 80), and it's important to have that extra layer in case you screw up the Apache/MySQL/whatever settings and leave something open.
posted by malevolent at 12:08 AM on April 6, 2009


« Older Seeking a vanishingly obscure ...   |  Last year, I hired someone to ... Newer »
This thread is closed to new comments.