Clarification of "too loose server settings" statement in last post

By Chris on Dec 2, 2006 | In Meta | Send feedback »

In my last post I mentioned that one of the problems leading up to the hack attack this week was "too loose server settings". That statement in fact couldn't have been more inaccurate, and I wanted to clarify:

The server itself was so secure as to have prevented a minor blog hack from becoming an all out zombie spam server. The folks at Hit Catcher, who are long-time friends of ours and who graciously host this blog and a few other of our projects, had the foresight some time ago to lock the server down in every possible way.

The problem that I was alluding to was then not in regards to the server itself, but more to a loose setting within the PHP scripting engine that runs on the server and powers this blog software. It was as much an oversight on my part as anything, as I could have and should have taken extra steps to tighten the settings within my own hosting account. I hope this clears up an otherwise inaccurate claim.

This is a captcha-picture. It is used to prevent mass-access by robots.

Please enter the characters from the image above. (case insensitive)

Array

Leave a comment


Your email address will not be revealed on this site.

Your URL will be displayed.
:!: :?: :idea: :) :D :p B) ;) :> :roll: :oops: :| :-/ :( :'( |-| :>> ;D :P :)) 88| :. :no: XX( :lalala: :crazy: >:XX
(Line breaks become <br />)
(Name, email & website)
(Allow users to contact you through a message form (your email will not be revealed.)
This is a captcha-picture. It is used to prevent mass-access by robots.

Please enter the characters from the image above. (case insensitive)

Array
« An old friend's network TV debutBack online »