News Overview
Currently showing all news items posted in 2015. News items are available for these years:
Anope 2.0.2 Release
Anope 2.0.2 has been released, with many bug fixes and features.
The list of notable changes include:
Fix keepmodes preventing the first user of a channel from being deopped
Fix SQlines that don’t begin with # from matching channels
Made cs_clone behave like the help describes, copying many settings and lists by default
Allow cs_clone to clone levels, too
Update Hybrid protocol module for 8.2
Fix not unescaping all characters sent over XMLRPC
Fix crash when os_mode is used to destroy channels, like when unsetting permanent channel mode from an empty channel
Allow users with topic change privilege to change the topic instead of requiring them to use ChanServ’s topic command
Fix negatively locking param modes in default mlock
Change entrymsg to check for the SET privilege, not real founder
Allow configuring characters allowed in nicknames
Fix crash when non users register channels externally (like XMLRPC)
Remove operserv/exception MOVE, it did not function correctly. Instead reorder the list by deleting/adding entries.
Allow flood ttb to be 0.
Enforce mlock when disabling defcon modes
Fix cs_mode not being able to apply mlock on register
Add log message when users send memos
Fix old collide timers from staying around after successful identify. Fixes being able to identify and logout and still being hit by the old timers.
Fix undefined behavior in cs_mode which usually crashes when clearing large list modes
Show all opertypes in operserv/info, even if no opers use them
All users are recommended to upgrade.
The news post for the 2.0 branch is reproduced below for those not yet on 2.0. There is no new information here for users already on 2.0.
MD5 Sum: 67dec82058cd4e19ea25a19ead86d17c anope-2.0.2-source.tar.gz
MD5 Sum: c34afd0a39ed1bddf8e3baa4c051b418 anope-2.0.2.exe
We are proud to announce that after five years of development our latest stable release, Anope 2.0, is now available for download.
With this release we are deprecating the 1.8 branch and no longer recommend users use it.
Overview of changes from 1.8 to 2.0:
Use an account style system instead of the old NSNickTracking option, which allows you to stay logged in no matter what nick you are on.
Fantasy support for all commands.
Can assign core pseudo clients (such as ChanServ) to channels.
A built in web panel.
Persistent channels, which allows services bots to stay in empty channels.
Channel passwords replaced with founder level access (QOP, or the FOUNDER access level).
OWNER access levels added, defaults to access level 9999.
The option to use a flags based channel access system.
Ability to authenticate via SSL certificates
Autojoin channels on authentication (ns_ajoin)
Significantly more advanced logging system, choose what is logged and where it is logged.
Support for other optional database backends, such as SQL and Redis.
Granular command configuration. Configure which command is on what service, what it’s called, and who can use it.
Configurable opertypes, which allows defining new services operator levels (Root, Admin, Oper, etc.) and what permissions each has.
Ability to authenticate users against external databases, such as by SQL or LDAP.
Capability to switch between different encryption methods.
DNSBL support.
Installation instructions for Linux/UNIX:
Anope 2 requires CMake to be built. On most systems you can simply install the package from your package manager, eg. sudo apt-get install cmake or sudo yum install cmake.
First, enable any extra modules you want by executing the ‘extras’ script. Extra modules generally depend on other libraries, such as MySQL, and are not enabled by default due to their dependencies. Then run:
./Config
cd build
make
make install
Upgrading instructions:
1) Install Anope 2 to a separate directory from your old install (such as ~/services2)
2) Copy 1.8’s databases to the ‘data’ directory of your new install.
3) Configure services, the configuration files are located in the ‘conf’ directory.
Anope 2 uses a different configuration file format from 1.8, you will have to reconfigure them completely.
Use your old configuration as a reference.
4) While configuring, be sure to load db_old, which loads the old 1.8.x databases, and db_flatfile, which writes out the new Anope 2 database.
Ensure that the hash method in db_old’s configuration block is the same encryption method that you are currently using on 1.8.
Load the correct encryption module, which is the same one configured in db_old.
5) Start services. Once you confirm your database has been successfully imported, comment or remove db_old from the configuration file, so that the next time services restart, they will load the newer database.
Third party modules, such as most of the ones found on on the Modsite, that are written for 1.7.x or 1.8.x
will not work with Anope 2. However, many of the features of the most popular 1.8 modules have been included in the Anope 2 release, so you may find you no longer need your extra modules. If it is unclear to you whether or not a given feature is in Anope 2, come ask us.
Join our IRC channel at irc://irc.anope.org/anope for questions or comments.