ngIRCd - Next Generation IRC Server
http://ngircd.barton.de/
- (c)2001-2014 Alexander Barton and Contributors.
+ (c)2001-2019 Alexander Barton and Contributors.
ngIRCd is free software and published under the
terms of the GNU General Public License.
Differences to version 22.x
+- The "NoticeAuth" ngircd.conf configuration variable has been renamed to
+ "NoticeBeforeRegistration". The old "NoticeAuth" variable still works but
+ is deprecated now.
+
- The default value of the SSL "CipherList" variable has been changed to
"HIGH:!aNULL:@STRENGTH:!SSLv3" (OpenSSL) and "SECURE128:-VERS-SSL3.0"
(GnuTLS) to disable the old SSLv3 protocol by default.
the new mask will be KILL'ed. This was not the case with earlier versions
that only added the mask but didn't kill already connected users.
+- The "PredefChannelsOnly" configuration variable has been superseded by the
+ new "AllowedChannelTypes" variable. It is still supported and translated to
+ the appropriate "AllowedChannelTypes" setting but is deprecated now.
+
Differences to version 19.x
- Starting with ngIRCd 20, users can "cloak" their hostname only when the
set mode +x. This prevents regular users from changing their hostmask to
the name of the IRC server itself, which confused quite a few people ;-)
-Differences to version 17
+Differences to version 17.x
- Support for ZeroConf/Bonjour/Rendezvous service registration has been
removed. The configuration option "NoZeroconf" is no longer available.
You should adjust your ngircd.conf and run "ngircd --configtest" to make
sure that your settings are correct and up to date!
-Differences to version 16
+Differences to version 16.x
- Changes to the "MotdFile" specified in ngircd.conf now require a ngircd
configuration reload to take effect (HUP signal, REHASH command).
automake ("configure") should be no problem.
The normal installation procedure after getting (and expanding) the source
-files (using a distribution archive or GIT) is as following:
+files (using a distribution archive or Git) is as following:
0) Satisfy prerequisites
- 1) ./autogen.sh [only necessary when using GIT]
+ 1) ./autogen.sh [only necessary when using Git]
2) ./configure
3) make
4) make install
0): Satisfy prerequisites
When building from source, you'll need some other software to build ngIRCd:
-for example a working C compiler, make tool, GNU automake and autoconf (only
-when not using a distribution archive), and a few libraries depending on the
-features you want to compile in (like IDENT support, SSL, and PAM).
+for example a working C compiler, make tool, and a few libraries depending on
+the feature set you want to enable at compile time (like IDENT, SSL, and PAM).
+
+And if you aren't using a distribution archive ("tar.gz" file), but cloned the
+plain source archive, you need a few additional tools to generate the build
+system itself: GNU automake and autoconf, as well as pkg-config.
If you are using one of the "big" operating systems or Linux distributions,
you can use the following commands to install all the required packages to
build the sources including all optional features and to run the test suite:
-* RedHat / Fedora based distributions:
+* Red Hat / Fedora based distributions:
yum install \
autoconf automake expect gcc glibc-devel gnutls-devel \
- libident-devel make pam-devel tcp_wrappers-devel telnet zlib-devel
+ libident-devel make pam-devel pkg-config tcp_wrappers-devel telnet zlib-devel
* Debian / Ubuntu based distributions:
apt-get install \
- autoconf automake build-essential expect libgnutls-dev \
- libident-dev libpam-dev libwrap0-dev libz-dev telnet
+ autoconf automake build-essential expect libgnutls28-dev \
+ libident-dev libpam-dev pkg-config libwrap0-dev libz-dev telnet
1): "autogen.sh"
-The first step, autogen.sh, is only necessary if the configure-script isn't
-already generated. This never happens in official ("stable") releases in
-tar.gz-archives, but when using GIT.
+The first step, autogen.sh, is ONLY necessary if the "configure" script itself
+isn't already generated. This never happens in official ("stable") releases in
+"tar.gz" archives, but when cloning the source code repository using Git.
This step is therefore only interesting for developers.
autogen.sh produces the Makefile.in's, which are necessary for the configure
script itself, and some more files for make. To run autogen.sh you'll need
-GNU autoconf and GNU automake: at least autoconf 2.61 and automake 1.10 are
-requird, newer is better. But don't use automake 1.12 or newer for creating
-distribution archives: it will work but lack "de-ANSI-fication" support in the
-generated Makefile's! Stick with automake 1.11.x for this purpose ...
+GNU autoconf, GNU automake and pkg-config: at least autoconf 2.61 and automake
+1.10 are required, newer is better. But don't use automake 1.12 or newer for
+creating distribution archives: it will work but lack "de-ANSI-fication" support
+in the generated Makefile's! Stick with automake 1.11.x for this purpose ...
So automake 1.11.x and autoconf 2.67+ is recommended.
Again: "end users" do not need this step and neither need GNU autoconf nor GNU
projects / ngircd-alex.git / blobdiff