Log message:
unrealircd: Update to 5.0.4
UnrealIRCd 5.0.4 Release Notes
===============================
This new 5.0.4 version fixes quite a number of bugs. It contains only two small \
feature improvements.
Fixes:
* When placing a SHUN on an online user it was not always effective.
* Channeldb was not properly restoring all channel modes, such as +P.
* When upgrading UnrealIRCd it could sometimes crash the currently
running IRC server (rare), or trigger a crash report on
```./unrealircd restart``` (quite common).
* UnrealIRCd was giving up too easily on ident lookups.
* Crash when unloading a module with moddata.
* Crash if an authenticated server sends wrong information (rare).
* Removing a TEMPSHUN did not work if the user was on another server.
* SAJOIN to 0 (part all channels) resulted in a desync when used on remote users.
* Forced nick change from services was not showing up if the user
was not in any channels.
Enhancements:
* New option \
[set::hide-idle-time::policy](https://www.unrealircd.org/docs/Set_block#set%3A%3Ahide-idle-time)
by which you can change usermode +I (hide idle time in WHOIS) from
oper-only to settable by users. More options will follow in a future
release.
* In WHOIS you can now see if a user is currently (temp)shunned.
This only works for locally connected users for technical reasons,
so use ```/WHOIS Nick Nick``` to see it for remote users.
Changes:
* The oper notices and logging with regards to server linking have changed
a little. They are more consistent and log more now.
* When an IRCOp tries to oper up from an insecure connection we will now
mention the https://www.unrealircd.org/docs/FAQ#oper-requires-tls page.
This message is customizable through
\
[set::plaintext-policy::oper-message](https://www.unrealircd.org/docs/Set_block#set::plaintext-policy).
* The French HELPOP text was updated.
|
Log message:
unrealircd: Update to 5.0.3.1
UnrealIRCd 5.0.3.1
-------------------
This fixes a crash issue after REHASH in 5.0.3.
UnrealIRCd 5.0.3
-----------------
Fixes:
* Fix serious flood issue in labeled-response implementation.
* An IRCOp SQUIT'ing a far remote server may cause a broken link topology
* In channels that are +D (delayed join), PARTs were not shown correctly to
channel operators.
Enhancements:
* A new HISTORY command for history playback (```HISTORY #channel number-of-lines```)
which allows you to fetch more lines than the on-join history playback.
Of course, taking into account the set limits in the +H channel mode.
This command is one of the [two \
interfaces](https://www.unrealircd.org/docs/Channel_history#Ways_to_retrieve_history)
to [Channel history](https://www.unrealircd.org/docs/Channel_history).
* Two new [message tags](https://www.unrealircd.org/docs/Message_tags),
```unrealircd.org/userip``` and ```unrealircd.org/userhost```
which communicate the user@ip and real user@host to IRCOps.
Changes:
* Drop the draft/ prefix now that the IRCv3
[labeled-response](https://ircv3.net/specs/extensions/labeled-response.html)
specification is out of draft.
* The operclass permission ```immune:target-limit``` is now called
```immune:max-concurrent-conversations```, since it bypasses
\
[set::anti-flood::max-concurrent-conversations](https://www.unrealircd.org/docs/Set_block#set::anti-flood::max-concurrent-conversations).
For 99% of the users this change is not important, but it may be
if you use highly customized [operclass \
blocks](https://www.unrealircd.org/docs/Operclass_block)
Are you upgrading from UnrealIRCd 4.x to UnrealIRCd 5? If so,
then check out the *UnrealIRCd 5* release notes [further down](#unrealircd-5). At the
very least, check out [Upgrading from \
4.x](https://www.unrealircd.org/docs/Upgrading_from_4.x).
|
Log message:
unrealircd: Update to 5.0.2
Upgrade notes (seem like there are very few breaking changes):
https://www.unrealircd.org/docs/Upgrading_from_4.x
What's new in UnrealIRCd 5:
* Channel history. You can now see the last couple of lines that have
been said on channels when you JOIN. For this you need to set channel
mode +H, eg: eg: /MODE #chan +H 15:1440
* More IRCv3 features. Additional details are communicated to clients
which may help with displaying information. Implemented specs are:
account-tag, message-ids, time, echo-message, labeled-response and
BATCH.
* Ban exceptions (/ELINE). You can now exempt users dynamically on IRC
from *LINES, spamfilter, throttling, blacklist checking, connection
floods, bypassing antirandom, etc. Just type /ELINE on IRC to see
details.
* *LINES and Spamfilters are remembered: All of these are saved to a
file every few minutes and saved across reboots. This uses the new
tkldb module (loaded by default). No need for services for that
anymore.
* Persistent channels are remembered: For channels which have mode +P
set we now save all channel settings across reboots (topic, regular
modes and +beI lists). This via the channeldb module (loaded by
default).
* Anti connect-flood measures. In the last few 4.2.x versions we
introduced Connthrottle and reputation. In 5.x these modules are now
loaded by default for increased security.
* Easily restrict commands to fight drones. You can now disable any
command or impose restrictions, such as: command can only be executed
after being connected for XX seconds, or if you are identified to
services, etc. See the example for how to restrict LIST, INVITE and
messaging.
* Module manager for managing 3rd party modules easily. Install and
update modules with a single command.
* Condition configuration. You can have condition configuration where
you e.g. @define $IP "203.0.113.1" and can use $IP everywhere in the
configuration file. Similarly, support for @if-blocks. This is
especially useful for advanced users who like to use the same
configuration file on multiple machines, usually with the help of
remote includes.
* Improved Channel Mode +L now kicks in for any rejected join, so not
just for +l but also for +b, +i, +O, +z, +R and +k. If, for example,
the channel is +L #insecure and also +z then, when an insecure user
ties to join they will be redirected to #insecure.
* Ban forwards. New extended ban ~f to forward users to the specified
channel if the ban matches. Example: MODE #chan +b
~f:#badisp:*!*@*.isp.org
* Improved WebSocket support. We already supported websockets, but now
we support websocket type 'text', which is compatible with web IRC
clients such as Kiwi IRC.
* Code cleanups. The biggest effort of all went into cleaning up old
code and making the code much more readable. This also means that
UnrealIRCd 5 will not be able to link with really older servers or
services, like UnrealIRCd 3.2.x.
* Windows version is 64-bits. This should allow for increased address
space and security. This also means UnrealIRCd 5 will not run on
32-bits Windows (should be rare nowadays, anyway)
|