Tweet Archive for October 2010 « page 2

@MarkAssani Look here for some good advice It’s not a WP-specific issue, if you’ve other PHP apps check them too.

in reply to MarkAssani — 5:31pm Oct 6 2010 —

@kendawes @zookx The problem is *not* known to be a WordPress one. Many non-wp php files have also been attacked

in reply to thewebmechanic — 5:29pm Oct 6 2010 —


in reply to AlistairReid — 3:56pm Oct 6 2010 —

Re: @123reg, more examples of this *not* being a WordPress issue coming in

2:37pm Oct 6 2010 —

@gvogvo1 I couldn’t possibly use a company that plays loud music at me and hosts such a dubious looking hard sell page #2thumbsdown

in reply to gvogvo1 — 12:42pm Oct 6 2010 —

@benhuson I know, but they mention a security breach that targets WP i.e. after they got in they infect WP files. Not they got in thru WP.

in reply to benhuson — 9:57am Oct 6 2010 —

@benhuson This mentions all php files & 123-reg’s ‘solution’ is fix for hosting security vuln that hit all php files

in reply to benhuson — 9:40am Oct 6 2010 —

Ref for my last tweet again, not WordPress specfic

9:33am Oct 6 2010 —

This 123-reg hack seems to be related to poor hosting security again, and not WordPress specific

9:27am Oct 6 2010 —

@Azizur thanks for the recommendation.

in reply to Azizur — 10:58pm Oct 1 2010 —