Become a premium member to remove ads
Search the Community
Showing results for tags 'SERVER'.
Found 3 results
Man. Crazy to think we've been going nine years. Nine years is a long time. Typically, the past anniversary posts have been worded along the lines of "yea we're pretty quiet now but we'll get somewhere soon i promise!". Last year, I wanted the 8th anniversary announcement to be the final one following that format: Well, we aren't quite there yet unfortunately. That being said, we are undeniably closer to that target than we have been in a very long time - possibly closer than we ever have been. Which, hey - I'll take it. Any progress is good at this point. So, let's take a look back and reflect on the past year. Reflecting on Year 8 We started the 8th year off with, once more, a promise of hope for the future. We were hard at work on updating to 1.14 - though it still took much longer than any of us would've liked. It saw the departure of several staff members and the introduction of new ones. While year 8 wasn't as groundbreaking as we all obviously would've hoped - it was still a new beginning nonetheless. It marked the point where we fixed a number of the deeply-rooted management issues with CU. Not server issues per se, but issues with how I managed the people. I'd had a pretty serious issue with holding on to staff members for far too long. People were on the staff team for no other reason than I was used to seeing their name in Blue or Green. The vast majority of those people didn't even need to be demoted - when I laid out the new expectations going forward, they simply stepped down to avoid that uncomfortable situation. With those folk out of the team, room was available for new users to fill that role. The most notable addition is, of course, @Z0mbieslayer2013. You know him, you love him - and believe it or not, this is his first time as a Moderator. While there are certainly times where this is clear, he's done something that really doesn't happen as often as it probably should - he asks questions. Not just questions on "how do I do x", or "what do I do if Y happens?" - no, no. He stands up straight and asks questions about why things are they way they are. Questioning things that have been the case for years and pointing out things that should be obvious improvements. And while not all of his ideas and suggestions have been implemented - the fact that he still proposes changes and enhancements at all is important. When you as a leader surround yourself with people who just agree with you all the time, you're living in an echo chamber. And if nothing else, Zombie is ensuring that I'm not sitting in one. The second half of year 8 saw us hit some of the biggest population spikes we've seen in years. As unremarkable as reaching 10 or more users on the server at once seems, it's a step in the right direction - and a step we've not seen happen in years. The last time we saw numbers that high was in early 2017, roughly 3 years ago. And while those heights tend to happen at random with much of the activity still hanging much lower, activity as a whole has improved. 0 people on isn't the norm during the whole day - you'll typically only see it at a couple specific parts of the day (typically very early/late). And of course, we've been slowly working on migrating everything over to BungeeCord - in an effort to remove technical issues. And this will be our primary focus for Chaotic United's 9th year. The Plan for Year 9 Our plan for this year is similar to what we did in Year 8. Where Year 8 was the year of fixing management-related issues, Year 9 is the year of fixing all the technical problems that have been building up since 2014. Fixing long-time issues, and making future issues easier to nail down and resolve. However, due to the sheer volume of issues that are scattered about, there's no way for us to have a single, coherent memory of each and every issue. This is where you come in. If you find any bug - or anything that so much as looks like a bug - report it on our Bug Tracker. Our goal is to start the decade off with a solid technological foundation - and to enter the second decade of Chaotic United as a strong, stable, secure, and reliable server. A server that doesn't have a series of ridiculous roadblocks keeping people who would otherwise enjoy the server from having fun. And most importantly, and I cannot stress this enough - do NOT just tell me about a bug. My memory is NOT reliable and I guarantee you I'll forget about the issue entirely within 24 hours - if not sooner. This is the reason we have the bug tracker, so that issues aren't just "forgotten" and so that their status can be tracked. If you've told me about an issue before, report it. Anything that you'd consider strange or "probably not intentional" is something that should be reported. I want to know any and all issues you guys might have, severe or not. Even if it's a completely harmless bug, report it. I want to get each and every bug on that bug tracker fixed - I'm sure I speak for everyone when I say I'm sick and tired of having a buggy server - and I'm sick of making you guys constantly put up with a buggy server. Speaking of Server Stuff... Something sort of huge has been developing here lately - and you might've already heard me mention it. But if you haven't - in the coming months, we'll be doing a bit of server consolidation. Most of this is outside of Chaotic United entirely, but one change that will affect CU (slightly) is that the Elaztek Gitlab will be hosted on the same machine as the MC server. For a while (and still at the time of writing), it runs on its own machine with a couple of things that aren't CU or Elaztek related. I know what you're thinking: "I don't give a damn about server consolidation - that's not exciting". And you're absolutely right. However, the next part (at least for me) is. As part of this consolidation, I will be taking over the payment of the CU/Elaztek servers moving forward. The only things I won't be paying for are the relays - as those are so cheap that Michael will continue paying for them. That being said, a couple of the unused ones are being dropped. If you're worried - don't be. If you use a relay, the one you use will be kept online. Several that we have are just not used whatsoever - and as such, they're being dropped. For those of you who have been around for a while, you'll know that Michael has been fairly crucial to paying the bills for most of the time of the CU revival. He hosted the server out of his house from late 2014 through to mid-2015 when we merged with ND. From there, we moved to a VPS which I paid for. A while later (2017 if I'm not mistaken but don't quote me on it), Michael stepped back in to pay for the dedicated server that we've been using until today. After finally getting a stable job that shows no signs of going anywhere, I'm finally in a position where I can actually cover these bills. And with this transition, I think it's all the more important that we all thank and honor Michael for what he's done for CU since 2014. It's no exaggeration that, if he never came along, we absolutely would not be here today. I'd have likely given up on it after my old laptop died and I'd probably be on a whole different path - never getting a chance to know any of you guys. The legacy of Chaotic United would've ended in mid-2016, possibly even sooner - when ND shut down. That would've been it and the book would've closed. But thanks to Michael - we persevered. As small as we are, we've held strong and steady and managed to hold this thing together all this time. We've made sure that, if nothing else, Chaotic United's story didn't end several years ago - to ensure it lives to see a new year, a new decade, and a new generation. And while there are numerous people who have contributed to that (see the credits page (which im aware needs some updating)), Michael is easily the biggest contributor by far. So - on behalf of all of us, thank you Michael for all that you've done thus far, and will hopefully continue to do. Oh yeah - sidenote, Michael won't be leaving the community. I know the way I wrote all that makes it sound like he is, but in reality he's still gonna be a big part of the backend management of CU - it's just that he won't be putting his own money into it anymore. When we start moving things to the new server, we'll be sure to announce it both on Forums and Discord - as there will be a little bit of downtime during the migration. Wrapping Up - For Now... Well, I think that about wraps it up for now. Some of you may think that this is yet another "hope for the future" post. And I suppose in a sense, it is. But this one is a bit different. I'm not proclaiming that we're starting a new beginning today. We already did that last year. I'm saying that right now, we're a little behind schedule - but still on track. This isn't the start of a new age of CU, but rather the next building block of that new beginning. I can't say how soon it'll be, but our goal is to be running smooth and stable and with either minimal or no bugs by December. Will we achieve that goal? Only time will tell - so stay tuned.
The time has come for Modded MC to return to Chaotic United! Once again, we are utilizing the Brink of Chaos Modpack - but this time around, we have included various mods suggested by YOU - the CU Community! The Modded MC Subforum has been added (and contains topics from FTB Trident, Horizons, and old BOC) and has a couple new topics added - an up-to-date list of all the mods installed, and a topic to help those unfamiliar with the Technic Launcher to get up and running. In terms of resources, you are going to need at least 4GB of RAM on your PC and a decent CPU. RAM is the biggest thing you need. If you know how Technic works, just set your memory to 4GB (or 3.5GB if you only have 4GB in your PC, or more if you have it). If you aren't entirely sure how to do this, check out this handy topic. For a full list of mods, check this other topic. As you can also see, we have a new and improved logo design for the Modpack as well! It is made to better fit what the pack overall has - technology, creativity, and weaponry. Our server actually HAS a spawn now, which is a considerable step up from the server that we tried to do before which really never had one. This modpack has been in the works since earlier this year, you may even recall BlarFlargen mention hosting it in the past. Now, the server is hosted by AwakenedRage/Kryptoaware, who while is not present on the CU Discord, still is involved in CU from the management side of things. Our server is live at mod.chaoticunited.net - but this is technically unimportant, because the Modpack ships with the server already on your server list! We hope you guys enjoy the new and improved Modded MC experience, and stay tuned as we have another server set to launch soon as well. A server really designed for a small niche audience, but something we want to bring to CU nonetheless. So, go on! Have fun!
Hi All, A security exploit has been identified in the openjdk 1.7.0 version. The server uses OpenJDK 1.8 and has already patched the exploit. However this is also present in Java SE clients. It is highly advised that you update your java. FAQ Are there any crucial differences between Oracle and Open JDK? Nothing crucial. The openjdk project is mostly based on hotspot source code donated by Sun. Moreover, openjdk was selected to be the reference implementation for java 7, and is maintained by Oracle engineers. There's a more detailed answer to your question here, which links to this blog post: Q : What is the difference between the source code found in the OpenJDK repository, and the code you use to build the Oracle JDK? A : It is very close - our build process for Oracle JDK releases builds on OpenJDK 7 by adding just a couple of pieces, like the deployment code, which includes Oracle's implementation of the Java Plugin and Java WebStart, as well as some closed source third party components like a graphics rasterizer, some open source third party components, like Rhino, and a few bits and pieces here and there, like additional documentation or third party fonts. Moving forward, our intent is to open source all pieces of the Oracle JDK except those that we consider commercial features such as JRockit Mission Control (not yet available in Oracle JDK), and replace encumbered third party components with open source alternatives to achieve closer parity between the code bases. i dont get it. if they are similar then why two? Technical differences are a consequence of the goal of each one (OpenJDK is meant to be the reference implementation, open to the community, while Oracle is meant to be a commercial one) They both have "almost" the same code of the classes in the Java API; but the code for the virtual machine itself is actually different, and when it comes to libraries, OpenJDK tends to use open libraries while Oracle tends to use closed ones; for instance, the font library. Is the Server Affected? The Server was not affected by this exploit as the server uses OpenJDK 1.8 which had this fixed. Updated java-1.7.0-openjdk packages fix security vulnerabilities Publication date: 15 Apr 2015 Type: security Affected Mageia releases : 4 CVE: CVE-2005-1080 , CVE-2015-0460 , CVE-2015-0469 , CVE-2015-0477 , CVE-2015-0478 , CVE-2015-0480 , CVE-2015-0488 Description Updated java-1.7.0 packages fix security vulnerabilities: An off-by-one flaw, leading to a buffer overflow, was found in the font parsing code in the 2D component in OpenJDK. A specially crafted font file could possibly cause the Java Virtual Machine to execute arbitrary code, allowing an untrusted Java application or applet to bypass Java sandbox restrictions (CVE-2015-0469). A flaw was found in the way the Hotspot component in OpenJDK handled phantom references. An untrusted Java application or applet could use this flaw to corrupt the Java Virtual Machine memory and, possibly, execute arbitrary code, bypassing Java sandbox restrictions (CVE-2015-0460). A flaw was found in the way the JSSE component in OpenJDK parsed X.509 certificate options. A specially crafted certificate could cause JSSE to raise an exception, possibly causing an application using JSSE to exit unexpectedly (CVE-2015-0488). A flaw was discovered in the Beans component in OpenJDK. An untrusted Java application or applet could use this flaw to bypass certain Java sandbox restrictions (CVE-2015-0477). A directory traversal flaw was found in the way the jar tool extracted JAR archive files. A specially crafted JAR archive could cause jar to overwrite arbitrary files writable by the user running jar when the archive was extracted (CVE-2005-1080, CVE-2015-0480). It was found that the RSA implementation in the JCE component in OpenJDK did not follow recommended practices for implementing RSA signatures (CVE-2015-0478). References https://bugs.mageia.org/show_bug.cgi?id=15706 http://blog.fuseyism.com/index.php/2015/04/15/security-icedtea-2-5-5-for-openjdk-7-released/ http://www.oracle.com/technetwork/topics/security/cpuapr2015-2365600.html https://rhn.redhat.com/errata/RHSA-2015-0806.html http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2005-1080 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0460 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0469 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0477 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0478 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0480 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0488 I am glad that I used the Beta Version of Mageia that has updated dependencies and took the extra downtime. This would of been a nightmare to take care of. Looks like the downtime actually benefited us for once