I would say a good chunk of the popular servers are already running recent enough code to prevent the exploit. It was fixed in the server code as of late March. There was a security flaw found that allows player impersonation to occur. Someone reported it didn’t work on Tiger.įirst off, I’d like to say that ALL server owners should upgrade to 2.0.16 as soon as possible. UPDATE: Removed “Tiger” from the note for mrapple’s OSX build. If you want to help contribute any fixes, that is welcome as well. Here are some places to look:Īnd feel free to mention/discuss the bugs (known or otherwise) on our #bzflag IRC channel. If you encounter bugs or problems, please check if they have already been reported. OSX build by mrapple (NOTE: Intel Only, should work on Leopard, and Snow Leopard)Īs I don’t have an Intel Mac (much less a Mac that boots) I can’t verify the OSX builds will work as noted, soooo….OSX build by Constitution (NOTE: Probably Intel only, Snow Leopard only, 64-bit only.).There’s a forum thread over at the BZFlag forum about this as well. Linux users (and OSX users that can’t run the builds below) can build a client with the source from SVN. I have made a Windows installer of the latest development code, and a couple other people made various versions of an OSX build. During that time, there might be some temporary outages.īZFlag 3.0.0 is in the “alpha” stage right now. ![]() So, I’ll be working on the migration over the weekend here. It’s not that we’ve outgrown the server, but there is just a couple resource hungry processes (cough irssicough) on the old server that chew up lots of RAM (hundreds of MB) and make everything else very slow. The existing server has been less than ideal for a long time and has hit various resource limitations. We’re also going to work on migrating all of the web services (forum, list, wiki, main site, etc) to a different server that will be a bit more … responsive. Here’s a wiki page that we’re working on that covers the plan: It won’t be BZFlag 3.0, but it will be a new version that has features worth upgrading for. Less new features = less chance of breaking stuff. This will mean there is less time for feature creep to take over again, which in turn will reduce how much testing we have to do. The idea is to push for getting a release out in a month or so. Then we’ll start to bring back specific low-risk features from 2.99.x and put them into 2.3.x, which we’ll release as 2.4.0.0 (or whatever we decide on). Now the plan is to move trunk (2.99.x/3.x.x) out of the way, copy v2_0branch (2.0.x) into trunk, and then relabel the new trunk as 2.3.0.0. Feature creep from the last five or six years caused us to end up with something we couldn’t easily fix. We got lost in all of the bugs and features and couldn’t get a release out. Essentially it’s been decided that version 3.0 was too big of a jump with far too many big changes. Some serious thought is being put into getting a new release of BZFlag out.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |