On Sunday 08 June 2003 02:15, Tom Nielsen wrote:
On Sat, 2003-06-07 at 22:29, Derek Fountain wrote:
The downside is security. Once you have an entry point into your box from the outside world, especially with a static IP address, you need to understand exactly what that entry point allows and what abuse it might get put to. In other words, you need to read up on Apache and ensure the config is set as you need it. Don't just assume SuSE have set up a secure config which meets your needs.
If you just want to serve static pages and photos, make sure you don't allow PHP, mod_perl or any other of the other abusable things to be accessed from the outside world.
I really, really, really hate reading manuals!! I could stress that more, but I don't have enought time. Most have too much information that would apply on an enterprise level rather than a home user/newbie. Is there a "crib notes" version that I can look at some where? I've always had a static IP, but no reason for anyone to look at it.
As soon as you put up a webserver, you may find Adelphia looking at it. Most ISP's frown on their customers running services without paying extra bucks. (and they scan ports to find such services)
Thanks for the info!
Tom
- - - - - - - - - - - - - - - - - -
Tom Nielsen Neuro Logic Systems, Inc. 805.389.5435 x18 www.neuro-logic.com