Anope 2.0.3 Release
Anope 2.0.3 has been released, which contains bug fixes, and several new features, such as Unreal 4 support.
The notable changes includes:
Add support for UnrealIRCd 4
Fix cs_access to respect chanserv/access/list privilege
Fix cs_access to match level -1 as every user, not any level <0
Fix problems related to object destruction order when using db_sql_live
Show memo notify settings in ms_info
Fix some actions bumping channels last used time that shouldn’t have
Add maxlogins configuration directive to limit the number of concurrent logins to one account
Fix race with auto svsnick on ghost sometimes causing nick collisions instead
Fix saset langauge reply
Show akill/sxlines ids in VIEW
Fix crash when an oper is configured in both the configuration and via os_oper
Fix m_ldap reconnect logic not properly setting protocol and network timeout settings
Fix crash from unloading regex modules when regex xlines exist
Fix irc2sql to store away messages
Add notice method to m_xmlrpc_main
Fix numerics on InspIRCd from being sent to user UID
Fix +I on InspIRCd to be considered oper only
Fix crash in webcpanel when deleting your own access on a channel
Fix webcpanel allowing suspended users to login
Fix hs_off on InspIRCd to not desync active user host
Fix bs_bot to not allow colliding bots into users
Don’t allow hostserv modules to load if there is no hostserv
Fix ns_register allowing bot nicks to be registered through webcpanel
Don’t update chanserv keepmodes during inhabit
Fix build on cmake 2.4
Allow searching emails by wildcard in ns_getemail
All users are recommended to upgrade.
MD5 Sum: 61813c38533dc1340a5693f649deaee3 anope-2.0.3.exe
MD5 Sum: cdf1592facf63eaafcbd4844aee9a23b anope-2.0.3-source.tar.gz
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.
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.