Welcome to WebmasterWorld Guest from 22.214.171.124
Forum Moderators: mack
I'm concerned, now, that there may some security risks for both of us. Besides turning on the firewall, what else might i need to be concerned with. This is the first live site i've done, and there's alot i don't know yet.
Am i putting her laptop, and her website at risk by running localhost and leaving it on so she can check it when i'm not there?
I do occasionally run various servers on OSX and have never had a problem, but the computers I use go through the NAT firewall on my router, as well as the built-in software firewall.
My understanding is that any computer that is web-accessible by IP address is vulnerable to some degree, and that if someone with enough expertise is determined to hack in then they will probably manage it - even if you are the Pentagon.
In your case it is probably enough to defend against casual chancers, automated or otherwise, and having a hardware firewall between your computer and the web would seem advisable if running a webserver for any length of time.
Hopefully a real security expert will comment soon.
They will probably freak us both out.
I have been using servers on pc as "localhost" for ages and have never had any issues, occasionaly if I have a client on messeger I will open port 80 and send then a link to view the site usign my computer as a server.
Localhost development machines are very handy tools, and as long as your router is doing its job, and the server is configured correctly the risk should be very small. The advantages will sure outweigh the risk.
I am ignorant about routers. Niether of us has one to my knowledge.
When I am running a webserver just for my own testing, my router firewall is blocking port 80 to outsiders. If I want to make the webserver available to the public I open port 80, and that is when security becomes an issue.
One rough and ready method of keeping the nasties out is using a different (obscure) port number.