Comments on: Hacked http://chrisgonyea.com/archives/2005/08/17/hacked/ Just another WordPress weblog Tue, 09 Mar 2010 14:59:25 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Chris http://chrisgonyea.com/archives/2005/08/17/hacked/comment-page-1/#comment-220 Chris Fri, 19 Aug 2005 18:33:27 +0000 http://chrisgonyea.com/archives/2005/08/17/hacked/#comment-220 It is possible. I did see that post about the different versions of 1.5.2 right after I got the e-mail from Dreamhost. I don't know which copy of 1.5.2 I originally had. That is one reason why I did a reinstall of 1.5.2 from a freshly downloaded copy of it...so there was no chance of a problem. However Dreamhost could not tell me exactly when the hack occured (it could have been a week ago or the day of 1.5.2) without having me go deep into the logs. Not worth the time or effort really. So I still don't know when the hack exactly occured. Either way, things appear to be ok and back to normal. It is possible. I did see that post about the different versions of 1.5.2 right after I got the e-mail from Dreamhost. I don’t know which copy of 1.5.2 I originally had. That is one reason why I did a reinstall of 1.5.2 from a freshly downloaded copy of it…so there was no chance of a problem.

However Dreamhost could not tell me exactly when the hack occured (it could have been a week ago or the day of 1.5.2) without having me go deep into the logs. Not worth the time or effort really. So I still don’t know when the hack exactly occured.

Either way, things appear to be ok and back to normal.

]]> By: Martey http://chrisgonyea.com/archives/2005/08/17/hacked/comment-page-1/#comment-219 Martey Fri, 19 Aug 2005 18:28:06 +0000 http://chrisgonyea.com/archives/2005/08/17/hacked/#comment-219 Is it possible that the fact that you upgraded to WordPress 1.5.2 so early could have something to do with it? The files in the 1.5.2 release were silently changed after the release was announced - see <a href="http://blog.php-security.org/archives/8-WordPress-irresponsible-silent-tarball-update.html" rel="nofollow">this post</a>. Is it possible that the fact that you upgraded to WordPress 1.5.2 so early could have something to do with it? The files in the 1.5.2 release were silently changed after the release was announced – see this post.

]]>