- Rehash notices
- Modes in CAPAB
- GetTargetAndAction() not being static in m_callerid
- Loading custom configuration files using --config. (@SaberUK)
- ServerConfig::Read not using std::endl. (@SaberUK)
- Out of date comments in opers.conf.example, issue #624
- Fix typos, remove misleading information, rephrase a few sentences
- Add info about hmac-<hash> hash types
- Remove <performance:maxwho> (the code which used this was removed in 96e4434 - @SaberUK)
- Change inspircd.github.org to inspircd.org
Also, make all paths in the config relative to their associated
directory. This reverts a change in 2.0 which turned out to be a
terrible idea, especially for system-wide installations.
Changes to the original module:
- Parse settings using a sepstream, accept remote mode changes regardless of our config
- Refuse to link when config settings differ
- Style changes
All ideas and features are the brainchild and work of Daniel Vassdal
In the current implementation we only expire entries when someone joins, without a limit it was possible to make us practically never remove entries and consume (a tiny amount of) memory for each entry until the mode was removed/parameter was changed
The default limit of 30m is chosen to not surprise people when they upgrade. If you need to prevent rejoins for more than a minute then you should set a (timed)ban instead
Config option is available to change the limit (2.0 only)
- Example config files now end with .conf.example.
- Example text files now end with .txt.example.
- Removed 'inspircd' from the name of multiple example files.
- Added missing oper motd example file.
<ldapauth:host>, when set, will be applied to users identifying with ldapauth.
The host can also take formatters from fields set on the DN of the user.
This patchset aims to ease the packaging of InspIRCd for a system-wide installation scenario.
Changes in detail:
configure: Add the options --log-path and --data-path
m_ssl_gnutls, openssl: Change the hardcoded "conf/" to the existent CONFIG_PATH macro
m_xline_db: Make the location of xline.db configurable. It will use --data-path as default value, but this can be
changed using the configuration files.
