UnrealIRCd

We are looking for translators of unreal32docs.html in the following languages: Spanish, Greek, Dutch, and German. The first three haven't been updated since 2006/2007, so we had to remove them in 3.2.10-rc1. Users are running into problems due to ... [More] these translations being so much out of date. Most likely these will have to be done from scratch. The German translation was last updated in 2010 so could still be made up to date with considerable less work. If you want to translate the documentation, AND you have sufficient time available (important!), then contact [email protected]. People who speak your language will greatly appreciate your work, but don't underestimate the number of hours the initial translation will take! Also, be sure to also read the instructions below (copy of doc/translations.txt): Code: ---------- ==[ Translations ]============================================================ Starting with the release of Unreal 3.2 we have begun accepting translated documentation files. For now, only translations of unreal32docs.html and example.conf are accepted. Other stuff might be translated later, but this will probably be postponed to 3.3 (numerics/ircd text/help.conf/etc). There a few requirements however: - When you submit your translation it should be a translation of the very latest doc... So be sure to t ... (Read More) [Less]

I've released UnrealIRCd 3.2.10-rc1 (Release Candidate 1) for testing today. Members from the public are welcome to test if there are any major release critical bugs (such as crash bugs) present, so they can be corrected before the real 3.2.10 ... [More] release. Note that we do not recommend running this version on production servers. To grab this version, go to www.unrealircd.com -> Downloads. You can help us by testing specific items which can be found on our the Unreal3.2 testing forum. Be sure to read the first post 'READ THIS! (how to use)'. Summary of the new features and fixes: Code: ---------- ==[ NEW ]== - Improved socket engine. This brings some performance improvements and also makes it easier to configure a system to hold more than 1024 clients (no more editing of header files on Linux!). - ESVID support: services can communicate the account name of the user back to the IRCd. This only works on ESVID-capable services: - Extban ~a:<accountname>: matches users who are logged in to services with that account name. - Show account name in /WHOIS - CAP support: this enables clients to enable ce ... (Read More) [Less]

We have launched a new modules site at http://modules.unrealircd.org/ Module developers can now easily submit a module, manage updates, and more. Users can also register to comment on modules and rate them. Our previous modules site was hard to ... [More] maintain and therefore the modules listed on them were often out of date. We hope this new site will (once again) become the central location where all up-to-date UnrealIRCd modules can be found. A few weeks ago we have tried to contact all module authors of the old site regarding the transfer of their modules. If you're one of them, then please send an e-mail to [email protected]. Do you have a new module which currently is not listed? Then register your account at the site and submit the module! For security, all new and updated modules go in a queue first, which is then checked by staff, then the module is approved or rejected. We have multiple staff members checking this queue, so this shouldn't take longer than just a few days. [Less]

We've launched two website contests: The Main website contest and the Modules website contest If you are a web designer / PHP developer and would like to contribute to the UnrealIRCd project by making one of these sites, then please read the linked topics for more information.

It has been more than 2 years since last stable release (3.2.8.1) and 4 months since last release candidate. Now, finally, UnrealIRCd 3.2.9 is out! There have been 212 changes since previous release which is almost the same as previous THREE stable ... [More] releases combined. The changes consist of the usual amount of bugfixes, however also a substantial amount of new features have been added. See the Release Notes below for a summary of the changes. Special thanks go to binki, who did a considerable amount of work to make this release possible. Also thanks to everyone who contributed to UnrealIRCd, whether it is by doing support, reporting bugs, or just by using our software, helping us to maintain our position as the most widely used IRCd. Code: ---------- Unreal3.2.9 Release Notes ========================== ==[ GENERAL INFORMATION ]== * If you are upgrading on *NIX, make sure you run 'make clean' and './Config' first, before doing 'make' * The official UnrealIRCd documentation is doc/unreal32docs.html online version at: http://www.vulnscan.org/UnrealIRCd/unreal32docs.html FAQ: http://www.vulnscan. ... (Read More) [Less]

I've released the second release candidate for 3.2.9 for testing: Unreal3.2.9-rc2. There have been 32 changes between rc1 and rc2, they are not that major but do require re-testing. We hope that this will be the last Release Candidate, so we can do a ... [More] 3.2.9 release after this. Members from the public are welcome to test if there are any major release critical bugs (eg: crash bugs) present, so they can be corrected before the real 3.2.9 release. If you want to help out testing a bit, check out the downloads below. For downloads, see www.unrealircd.com -> Downloads. If you're willing to help some more, then check out the Unreal3.2 testing forum, where you can help to test specific test-items, be sure to read the first post ('READ THIS! (how to use)'). Code: ---------- Unreal3.2.9-RC2 Release Notes ============================ ==[ GENERAL INFORMATION ]== - If you are upgrading on *NIX, make sure you run 'make clean' and './Config' first, before doing 'make' - The official UnrealIRCd documentation is doc/unreal32docs.html online version at: http://www.vulnscan.org/UnrealIRCd/unreal32docs.html FAQ: http& ... (Read More) [Less]

This post is to clear up some cunfusion about Nathan (nate/NBishop/synapt) Bishop's relationship with the UnrealIRCd project. It is often brought to my attention how some things nate is telling users on other networks about the UnrealIRCd project is ... [More] tarnishing the UnrealIRCd reputation for the purpose of Nate improving his own reputation. Nate was a member of the UnrealIRCd Support Team for some time around 2007-2009, and was quite proficient in supporting users and helping them work out their problems with getting Unreal set up and in a production state. He created the new version of the UnrealIRCd website. Nate seems to take pride in assigning blame for download mirror hacking incident to myself (Stealth), however there is no root cause other than overlooked security measures as explained in our security advisory here. Nate was involved with Unreal 3.2 and 3.3 (before 3.3 was scrapped) by submitting various patches to fix bugs. As for Nate's involvement with Unreal 4, he was interested in helping write the C++ core for the project. Nate never produced any code for Unreal 4. For about 9 months Nate claimed to have a core in progress, and continually put off ... (Read More) [Less]

I've released Unreal3.2.9-rc1 (Release Candidate 1) for testing. There have been a lot of changes - twice as much as usual - since 3.2.8(.1), so this is just the first in a series of RC's for Unreal3.2.9. Members from the public are welcome to test ... [More] if there are any major release critical bugs (eg: crash bugs) present, so they can be corrected before the real 3.2.9 release. If you want to help out testing a bit, check out the downloads below. Note that 3.2.9-rc1 should NOT be used at production servers! For downloads, see www.unrealircd.com -> Downloads. If you're willing to help some more, maybe you could help out in the Unreal3.2 testing forum as well, to test specific test-items, be sure to read the first post ('READ THIS! (how to use)'). Code: ---------- Unreal3.2.9-RC1 Release Notes ============================ ==[ GENERAL INFORMATION ]== - If you are upgrading on *NIX, make sure you run 'make clean' and './Config' first, before doing 'make' - The official UnrealIRCd documentation is doc/unreal32docs.html online version at: http://www.vulnscan.org/UnrealIRCd/unreal32docs.html FAQ: http://ww ... (Read More) [Less]

We're looking for translators for the UnrealIRCd documentation in the following languages: Dutch, French, Spanish, Turkish This is mainly about the translation of unreal32docs.html, but for some languages also help.conf / example.conf. There's no ... [More] need to translate from scratch, however, the current translations are more than 2 years out of date, and need to be updated, and then maintained. If you'd like to help out, please contact [email protected]. Be sure to also read the instructions below (copy of doc/translations.txt): Code: ---------- ==[ Translations ]============================================================ Starting with the release of Unreal 3.2 we have begun accepting translated documentation files. For now, only translations of unreal32docs.html and example.conf are accepted. Other stuff might be translated later, but this will probably be postponed to 3.3 (numerics/ircd text/help.conf/etc). There a few requirements however: - When you submit your translation it should be a translation of the very latest doc... So be sure to translate the cvs version of unreal32docs.html (www.vulnscan.org/UnrealIrcd/unreal32docs.html). - Of course the t ... (Read More) [Less]

After receiving many questions of what we are doing with regards to the hack incident, here's my reply: First, we now PGP/GPG sign releases. Our GPG key is [email protected] (0x9FF03937). When downloading UnrealIRCd you will be given ... [More] instructions on how to verify the integrity of the file. Second, we're now isolating/shielding the main site from the rest, and making parts unmodifiable, to prevent catastrophes in case of a break-in. Third, we added several methods of detection when files and other data is modified. Fourth, we'll only serve the files from the main site for now. While the mirror admins did not have any blame in this, it does mean we only have to protect our own site(s). And finally we did some other things which I won't mention here. In short: we've really tightened security since the break-in to make sure this will never ever happen again. As you may understand, we really can't afford a repeat of this incident. On an unrelated side note, I find the claims in various media that this security incident indicates that Linux and Open Source cannot be trusted and that Microsoft and closed-software is better really silly. It lacks any foundation. A hacker, once in, could just as easily have inserted the backdoor in Windows software. In fact, it is *THANKS* to it being Open Source that this backdoor got noticed, though - I fully agree - much too late. [Less]