Scott Alfter wrote:
In article <fe6e05da-cf23-4e80-a9a9-ab040217fa60@w5g2000prd.googlegroups.com>, Warren Ernst <wernst@gmail.com> wrote:On Apr 20, 9:04 pm, sc...@alfter.DIESPAMMERSDIE.us (Scott Alfter) wrote:In article <MOWdnZihDsqe3JfVnZ2dnUVZ_h-vn...@comcast.com>, Michael J. Mahon <mjma...@aol.com> wrote:A friend of mine used to keep a small website up on a Linux machine in his network's "DMZ".He had a chron script that ran every night to copy the website backup to the website files, just to cope with this problem. He said that he was logging dozens of probes per day.I suppose that'd work, but the better approach would be to keep your system updated. I have a script that runs weekly to check my installed apps against what Gentoo says has vulnerabilities; if any are found, it fires off some email to me listing what needs to be upgraded.Of course, the *best* approach is to do both. That's what I do. ;-)A cron job on my Mac mini keeps a local copy of my websites (and the databases they use) updated nightly. If something happens to a website, I can send it back up in not much time. (I should probably have it make some tarballs every once in a while, so I don't just end up with a local copy of a defaced website if I don't catch it in time.)
That's always a problem with automated backup--it backs up errors, too! And it's why my friend kept a private master copy that was auto-copied to the vulnerable "slave" copy on the server. All updates were done to the master copy, not the on-line copy. If a change were urgent enough, a copy to the slave could be "pushed". Of course, this was in the days before everybody could add to your website... ;-) -michael NadaPong: Network game demo for Apple II computers! Home page: http://members.aol.com/MJMahon/ "The wastebasket is our most important design tool--and it's seriously underused."