Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss] why don't web hosts scan their sites?



Hi All,

Over the weekend I fixed a small local business web site that had been
hacked.  Same old story, they were using a popular cms, didn't update
it and and old javascript library was compromised.  It was done by
this ass anonboy:  https://www.google.com/search?q=hacked+by+anonboy
A scan with clamav could have easily alerted the host of the
situation.  Why don't these guys scan their own servers?  I bet
godaddy is hosting thousands of hacked sites serving up malware.  I
can't imagine allowing this to happen on my server.  It seems every
low level "web developer" is giving clients wordpress, drupal, and
other cms solutions without providing support after installation and
then the client gets owned.  The clients should be using plain HTML in
most cases I've seen and not a dynamic site but that's another
argument.

-- 
Eric Chadbourne
617.249.3377
http://theMnemeProject.org/
http://WebnerSolutions.com/



BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org