UnrealIRCd 4.0.10-rc2 available for testing

[Bram M. <sy...@un...>]

(You can unsubscribe here 
<https://lists.sourceforge.net/lists/listinfo/unreal-notify> at the bottom of 
the page)

Hi everyone,

UnrealIRCd 4.0.10-rc2 is now available for download. This is the second 
release candidate for 4.0.10. It fixes problems with incorrect bans being set 
when servers are linked. The plan is to get a stable 4.0.10 out by Friday 13th.

In 4.0.10 nine modules have been added to UnrealIRCd. One of them brings 
support for WebSockets so you can access IRC directly from your web browser. A 
very crude UnrealIRCd + WebSocket example is available here 
<https://www.unrealircd.org/files/dev/ws/websocket_unrealircd.html> and should 
work on most browsers, including mobile. I've also created a forum thread 
<https://forums.unrealircd.org/viewtopic.php?f=46&t=8643> to discuss the new 
WebSocket support.

*Changes between version 4.0.9 and 4.0.10-rc2
*Improvements

  * Added "websocket" module. This provides support for WebSocket (RFC6455),
    allowing JavaScript (internet browsers) to connect directly to IRC without
    the need of a 'gateway'. This module is experimental and not loaded by
    default. See https://www.unrealircd.org/docs/WebSocket_support for more
    information. This module was sponsored by Aberrant Software Inc.
  * UnrealIRCd already has the ability to configure global SSL settings via
    the set::ssl block. Now you can also override these settings for a link
    block and listen block. One possible use for this would be having a
    long-lived self-signed certificate for server linking on a serversonly
    port, and a short-lived certificate for your users on the other ports
    (such as a certificate from Let's Encrypt). Another example would be to
    force TLSv1.2 for server linking but not for users.
    Documentation: global settings are in set::ssl
    <https://www.unrealircd.org/docs/Set_block#set::ssl::certificate>,
    port-specfic settings go in listen::ssl-options
    <https://www.unrealircd.org/docs/Listen_block> and server link specific
    settings go in link::outgoing::ssl-options
    <https://www.unrealircd.org/docs/Link_block>.
  * You can now exempt IP's from (DNSBL) blacklist checking via: /except
    blacklist { mask 1.2.3.4; };/
  * All free modules from vulnscan.org are now included in UnrealIRCd itself.
    The first two modules are loaded by default (privdeaf and jumpserver). The
    other ones you have to load explicitly by adding /loadmodule
    "modulename";/ to your unrealircd.conf.
      o usermodes/privdeaf - Do not permit PM's from others (User Mode +D)
      o jumpserver - Redirect users to another server during maintenance
        (/JUMPSERVER command
        <https://www.unrealircd.org/docs/User_%26_Oper_commands#JUMPSERVER>)
      o extbans/textban <https://www.unrealircd.org/docs/Extended_Bans> -
        Channel specific word filtering (+b ~T:censor:*badword* and +b
        ~T:block:*blockthis*)
      o antirandom <https://www.unrealircd.org/docs/Set_block#set::antirandom>
        - Detect drones with random nicks / ident / etc.
      o m_ircops - Show which ircops are online (/IRCOPS command)
      o m_staff - Show custom file (/STAFF command)
      o nocodes - If this module is loaded it makes chanmode +S/+c also
        strip/block bold and underline codes
      o hideserver - Hide servers in /MAP and /LINKS (note that this does not
        truly enhance security)

Major issues fixed

  * Compile fixes for Ubuntu 16 LTS / gcc 5.4.x
  * Crash if you had an invalid crypt password in your unrealircd.conf
  * Crash if you did not load the chanmodes/nocolor module or changed the
    order in which modules were loaded
  * Incorrect bans being added during server linking

Minor issues fixed

  * Delayjoin (channel mode +D) sending QUITs for hidden users & similar bugs
  * WHO now supports multi-prefix
  * You no longer need to place all your /class/ blocks before your /allow/ blocks
  * Date in Windows log file for the first few messages was always 1970.

*For services and module coders
*

  * Services coders: "SVSMODE Nick +d" will now mark a client as deaf. Don't
    confuse this with "SVSMODE Nick +d <svid>". The parameter makes all the
    difference. Use "SVSMODE Nick +d 0" to reset/empty the stored services id.
  * Module coders: changed return value handling of HOOKTYPE_RAWPACKET_IN: -1
    now indicates don't parse and stop reading from the socket (return) and 0
    indicates don't parse but proceed to next packet (if any). If you kill a
    client in this hook then be sure to return -1.

*Other
*

  * We've always printed big warnings when running UnrealIRCd as root. In this
    version we still do, but in future versions we will simply refuse to boot.
    https://www.unrealircd.org/docs/Do_not_run_as_root

*What's new in UnrealIRCd 4
*A short overview of the most important changes:*
*

  * <https://www.unrealircd.org/docs/Modules>You decide what to load
    <https://www.unrealircd.org/docs/Modules>. We have moved as much
    functionality as possible to 150+ individually loadable modules (commands
    <https://www.unrealircd.org/docs/User_%26_Oper_commands>, user modes
    <https://www.unrealircd.org/docs/User_modes>, channel modes
    <https://www.unrealircd.org/docs/Channel_modes>, extbans
    <https://www.unrealircd.org/docs/Extended_bans>, snomasks, ..). You decide
    which features your UnrealIRCd should have.
  * Fine-grained IRCOp privileges
    <https://www.unrealircd.org/docs/Operclass_block>. The way IRCOp
    privileges are granted has been redone entirely. This allows you to
    configure oper privileges on a very detailed level. You don't want
    OperOverride? You don't want opers to see secret channels? Or you want an
    oper with a very minimal set of privileges? This is all possible.
  * Wiki <https://www.unrealircd.org/docs/UnrealIRCd_4_documentation>. All
    documentation has been moved to a wiki <https://www.unrealircd.org/docs/>.
    It's even better than before and more accessible to people who are new to
    IRCd's. The wiki also allows easy translation
    <https://www.unrealircd.org/docs/Translating_UnrealIRCd_wiki_pages> by
    community members.
  * New directory structure
    <https://www.unrealircd.org/docs/UnrealIRCd_files_and_directories>. On
    *NIX the IRCd is now always installed to a different directory than where
    you compile from (~/unrealircd by default). No more mess. On both *NIX and
    Windows configuration files go in conf/, modules go in modules/, etc..
    Configuration files can be identical on Windows and *NIX. This new
    directory structure also allows easier packaging.
  * New I/O system using kqueue & epoll. The IRCd can now handle thousands of
    users more easily.
  * Improved SSL/TLS support. SSL has always been a major feature in
    UnrealIRCd but has been enhanced. UnrealIRCd is now always built with SSL
    support (both on *NIX and Windows). SSL client certificate fingerprints
    are visible in /WHOIS, a new certfp extban
    <https://www.unrealircd.org/docs/Extended_bans>
    (~S:certificatefingerprint), better defaults including 4096 bit keys and
    Perfect forward secrecy <https://en.wikipedia.org/wiki/Forward_secrecy>, etc.
  * DNS Blacklist support <https://www.unrealircd.org/docs/Blacklist_block>
    (DNSBL/RBL). Great for combating drones and other abusers.
  * Better and more helpful error messages. Especially regarding the
    configuration file.
  * More modern server-to-server protocol.
    <https://www.unrealircd.org/docs/Server_protocol:Changes> Such as using
    UID/SID's. Resulting in less desynch. issues.
  * Lowering the bar for Spamfilter
    <https://www.unrealircd.org/docs/Spamfilter#Block_simple_spam>. You can
    now choose between 'regex' and 'simple' matching. Simple matching allows
    using the usual '?' and '*' wildcards that everyone knows about. The regex
    engine has been moved from TRE to PCRE (=about twice as fast).
  * Configuration is more logical
    <https://www.unrealircd.org/docs/Upgrading_from_3.2.x>. Around 30% of the
    configuration blocks have been restructured. Don't worry, we include an
    UnrealIRCd 3.2.x to 4.x configuration file converter.
  * Easier 3rd party module management. On *NIX you now just put your 3rd
    party modules in /src/modules/third/ and then each time you run 'make'
    they will be compiled if needed.
  * Easier upgrading. On *NIX, when upgrading to a new version, ./Config will
    ask you to import settings from a previous installation, remembering your
    installation directory and other settings. It will also copy the 3rd party
    modules from the old to the new installation and re-compile them.
  * More secure. Even better secure defaults, more warnings about insecure
    behavior, ..
  * *IPv6 now also on Windows* <https://www.unrealircd.org/docs/Ipv6>.

For developers:

  * Easier source navigation. Because we moved almost everything to modules,
    it's now much easier to see all the code for a particular feature.
  * Cleaner code. There have been a lot of source code cleanups. Code has been
    restructured or rewritten. Old irrelevant code has been deleted.
  * Development documentation can be found on the wiki
    <https://www.unrealircd.org/docs/Main_Page>. We explain how to write a
    module in C and list all the details on the various Module API's such as
    how to write commands, channel modes, plug-in by using Hooks, etc...

*Upgrading from 3.2.x**to UnrealIRCd 4*
If you are upgrading from 3.2.x to 4.x then there are three important things 
to know:
*1) New file locations*
In UnrealIRCd 4 the location of the configuration files and other files have 
been changed. On *NIX the directory where you compile the IRCd from 
(previously 'Unreal3.2.X', now 'unrealircd-4.0.0') is no longer the same as 
the directory where the IRCd will be running from.
By default the IRCd is installed to //home/yourusername/unrealircd/ on *NIX. 
On Windows UnrealIRCd will install to /C:\Program Files (x86\UnrealIRCd 4/.

The new directory structure is as follows (both on Windows and *NIX):
conf/           contains all configuration files
logs/           for log files
modules/   all modules (.so files on *NIX, .dll files on Windows)

*2) Configuration file changes
*There have also been changes in various configuration blocks and settings. 
Don't worry, UnrealIRCd can convert your existing 3.2.x configuration files to 
UnrealIRCd 4 format. There's no need to start from scratch.
Please read https://www.unrealircd.org/docs/Upgrading_from_3.2.x for more 
information on the config file conversion.

*3) Third party modules*
If you are using 3rd party modules (modules not developed by the UnrealIRCd 
team) then they will require an update before they can run on UnrealIRCd 4. 
Contact your developer for a new version or ask on our Modules forum 
<https://forums.unrealircd.org/viewforum.php?f=52> where someone may be kind 
enough to convert the module for you if you ask nicely. Due to the many core 
changes in UnrealIRCd 4 it was simply impossible to make 3.2.x modules work 
out-of-the-box on 4.x as well.

*End of the 3.2.x series*
UnrealIRCd 3.2.x is End Of Life since December 2015. All support for it will 
stop after December 31, 2016.
See https://www.unrealircd.org/docs/UnrealIRCd_3.2.x_deprecated

*Download*
As always, you can download UnrealIRCd from https://www.unrealircd.org/
All releases are signed with our PGP key (short key id 0x108FF4A9 and long id 
0xA7A21B0A108FF4A9)

Please report all bugs and feature suggestions at https://bugs.unrealircd.org/


-- 
Bram Matthys
Software developer/IT con...@vu...
Website:www.vulnscan.org
PGP key:www.vulnscan.org/pubkey.asc
PGP fp: EBCA 8977 FCA6 0AB0 6EDB  04A7 6E67 6D45 7FE1 99A6