Support » Requests and Feedback » Another compromised release?

  • Sorry for the upcoming complaint, but it did say this is where you go with “criticism”. 🙂

    First off, I love my WordPress blog. I’ve been with 2.0.10 since it came out. I tried upgrading to early 2.x versions and they were too buggy for me, so I restored and stayed with 2.0.10. This week I upgraded to 2.5, which I was relieved to find is pretty decent (a few quirks, but not bad).

    When I saw the notice for 2.5.1, I tried to download it and got a “file corrupted” error from the unzip utility. I redownloaded it and the 2nd copy unzipped (I posted on this). Fortunately, I went to the forum before prepping my upgrade and found tons of posts with very troubling results.

    How is it possible there are so many problems, several of them being the same 5 or 10 show-stopping problems in many posts, with no word on fixes? Is it possible that, like 2.2, someone bad had access to the source code and messed with the code? Whether yes or no, why is 2.5.1 still available for download? It doesn’t work. Why hasn’t someone addressed this huge problem?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Well I am fairly sure that “someone bad” has not accessed the code as that gets posted. What I am sure of is that like version 2.5 the current 2.51 did not have testing and is not ready for a release as final code. At this point the developers do not seem to care what the end users think. And to be blunt WordPress 2.5x releases are nothing but sloppy workmanship. To that end I have been testing other possible software packages and will be replacing WordPress on a personal level and professional one (testing – as in checking for issues BEFORE going live.)


    How could you possibly be “fairly sure” it hasn’t happened? It took “3-4 days” to find out the last time someone bad cracked the download version of the code (see WordPress 2.1.1 dangerous, Upgrade to 2.1.2)…

    It was determined that a cracker had gained user-level access to one of the servers that powers, and had used that access to modify the download file.

    I’d prefer to believe someone cracked the code a second time, rather than there are dozens of critical issues that were missed in testing by the hard-working developers at WordPress. 🙂

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Another compromised release?’ is closed to new replies.