News Overview
Currently showing all news items posted in 2017. News items are available for these years:
Anope 2.0.6 Release
Anope 2.0.6 has been released, which contains bug fixes, and several new features.
The notable changes includes:
Log client IP for web clients running commands via webcpanel
Fix log file path for the config file could not be opened log message
Allow nickserv/group to be used via XMLRPC
Fix logsearch without wildcards
Support cidr exempts in m_dnsbl
Add support for IPv6 dnsbls
Add +u and +L channel modes for ircd-hybrid
Set +x after hostserv/off on InspIRCd and UnrealIRCd
Fix chanserv/mode not being able to set extbans
Send CHGIDENT/CHGHOST on SVSLOGIN on InspIRCd
Fix escaping replies from commands in webcpanel
Enable require_oper for all opers added via operserv/oper
Advertise SASL mechanisms to UnrealIRCd servers
All users are recommended to upgrade.
SHA256 Sum: e2a216ab92ceb75b9c8e089d74c4e4e4868b794dd15250d6f8fba3c608f90ccb anope-2.0.6.exe
SHA256 Sum: 546377755af33f5497a1f5811dfab7d289eaf07b644e4babd1de8d95b9936816 anope-2.0.6-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.
Posted on 11 Dec 2017 by Adam (Read More...)
Anope 2.0.5 Release
Anope 2.0.5 has been released, which contains bug fixes, and several new features.
The notable changes includes:
Fix negative levels to not match users with negative access
Fix memo sender to always be the account name of the sender
Allow unregistered users to use the ChanServ seen command
Fix secureops to not be enforced on operators with the chanserv/administration privilege
Fix command name in HELP syntax messages to always be upper case
Show unconfirmed nickname messages on registration in webcpanel
Fix NickServ SET EMAIL to be executable via XMLRPC
Fix OperServ USERLIST/CHANLIST to accept regexes
Allow OperServ USERLIST to also match realname syntax (n!u@h#r)
Fix db_old importing languages to use the UTF-8 version
Fix m_dns to return REFUSED if no answers could be found
Fix ns_maxemail to be case insensitive
Add MemoServ READ ALL command
Add support for NickServ GROUP to be executed via XMLRPC
Add support for logging hostname/ip of SASL authentication attempts, if supported by IRCd
All users are recommended to upgrade.
MD5 Sum: ff54bfd4d93c10723a237dc07073abac anope-2.0.5.exe
MD5 Sum: e0972e936e3f2ffd6bd65664e6af58a4 anope-2.0.5-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.