Three days ago (April 8th, 2014) word broke of a critical vulnerability (code named "Heartbleed") within the popular cryptographic software, OpenSSL, that allows an attacker to read the memory of the host system. Roughly two thirds of the internet relies on OpenSSL to keep sensitive data secret and private, leaving many sites and services (including those provided by Bukkit) potentially open to data leakage.
How did Bukkit respond?
CloudFlare, a service we depend on for Content Distribution among other things for many of our sites, patched the hole before it became public knowledge and we patched the rest of our systems shortly after (although it did take slightly longer due to complications we experienced with some of them). Despite our relatively quick response to this issue, this security hole has existed in OpenSSL since December 31, 2011 (though it was only made known recently) so the impact of this vulnerability is unknown.
At the beginning of the year Mojang started dropping hints of their plan to switch from a name based accounts system to a universally unique identifier (UUID) based accounts system, ultimately moving towards allowing people to change their Minecraft name. With much of Minecraft currently relying on a name based accounts system (bans, whitelist, ops to name a few) along with plugins using names to keep track of players (permissions, ownership, protections), this change has a high potential to break both plugins and servers if server admins and developers are not prepared for it. At the time of writing, Mojang have said they're planning to enable name changing around the time Minecraft 1.8 is released and with Minecraft 1.8 slated to release in May, the window for preparations is quickly closing.
What is a UUID?
A Universally Unique IDentifier is a fairly long series of hexadecimal numbers commonly used in software to uniquely identify something. With...
A new CraftBukkit for Minecraft 1.7.5 DEVELOPMENT build is now available! We strongly suggest that you only use this build if you would like to help us get a Beta build out sooner and are experienced with using unsupported development builds.
Despite the updates following Minecraft 1.7's release being relatively small and purely for the client, I decided it would be a good idea for us to keep pace with them in order to help with larger future updates. Unfortunately, after we had completed the update for 1.7.4, a 1.7.5 update was released which meant we had to start the update over. At the same time, we found ourselves battling against technical issues with our core infrastructure leading to a much longer update period than should have been necessary.
Will plugins break with this build?
Minecraft 1.7 is one of the most involved updates to date, with Mojang having touched a reported ~220k+ lines of code. As a result, a significant amount of the code base has shifted making...
A new CraftBukkit Beta Build (1.7.2-R0.3) that provides Minecraft 1.7.2 compatibility is now available. Please note: the stability of this build is relatively unknown due to the impact Minecraft 1.7 had on the core code.
Will plugins break with this build?
Minecraft 1.7 is one of the most involved and impactful updates to date, bringing about many changes to the core of Minecraft. As a result, there is a chance that plugins might break with this build. Even if that isn't the case, we have not completed work on API changes for 1.7 yet so future builds might still break plugins.
What is a Beta build?
A Beta Build is in between a developer build and a Recommended Build. These builds simply work and are promoted much more frequently than a Recommended Build. While we will do some testing before promoting a beta build, we will not be running it through our extensive test process. As such, there are no guarantees that they will not contain minor bugs. If we do find out...