1. ngIRCd - Next Generation IRC Server
  3. (c)2001-2013 Alexander Barton and Contributors.
  4. ngIRCd is free software and published under the
  5. terms of the GNU General Public License.
  6. -- INSTALL --
  7. I. Upgrade Information
  8. ~~~~~~~~~~~~~~~~~~~~~~
  9. Differences to version 20.x
  10. - Starting with ngIRCd 21, the ciphers used by SSL are configurable and
  11. default to HIGH:!aNULL:@STRENGTH (OpenSSL) or SECURE128 (GnuTLS).
  12. Previous version were using the OpenSSL or GnuTLS defaults, DEFAULT
  13. and NORMAL respectively.
  14. - When adding GLINE's or KLINE's to ngIRCd 21 (or newer), all clients matching
  15. the new mask will be KILL'ed. This was not the case with earlier versions
  16. that only added the mask but didn't kill already connected users.
  17. Differences to version 19.x
  18. - Starting with ngIRCd 20, users can "cloak" their hostname only when the
  19. configuration variable "CloakHostModeX" (introduced in 19.2) is set.
  20. Otherwise, only IRC operators, other servers, and services are allowed to
  21. set mode +x. This prevents regular users from changing their hostmask to
  22. the name of the IRC server itself, which confused quite a few people ;-)
  23. Differences to version 17
  24. - Support for ZeroConf/Bonjour/Rendezvous service registration has been
  25. removed. The configuration option "NoZeroconf" is no longer available.
  26. - The structure of ngircd.conf has been cleaned up and three new configuration
  27. sections have been introduced: [Limits], [Options], and [SSL].
  28. Lots of configuration variables stored in the [Global] section are now
  29. deprecated there and should be stored in one of these new sections (but
  30. still work in [Global]):
  31. "AllowRemoteOper" -> [Options]
  32. "ChrootDir" -> [Options]
  33. "ConnectIPv4" -> [Options]
  34. "ConnectIPv6" -> [Options]
  35. "ConnectRetry" -> [Limits]
  36. "MaxConnections" -> [Limits]
  37. "MaxConnectionsIP" -> [Limits]
  38. "MaxJoins" -> [Limits]
  39. "MaxNickLength" -> [Limits]
  40. "NoDNS" -> [Options], and renamed to "DNS"
  41. "NoIdent" -> [Options], and renamed to "Ident"
  42. "NoPAM" -> [Options], and renamed to "PAM"
  43. "OperCanUseMode" -> [Options]
  44. "OperServerMode" -> [Options]
  45. "PingTimeout" -> [Limits]
  46. "PongTimeout" -> [Limits]
  47. "PredefChannelsOnly" -> [Options]
  48. "SSLCertFile" -> [SSL], and renamed to "CertFile"
  49. "SSLDHFile" -> [SSL], and renamed to "DHFile"
  50. "SSLKeyFile" -> [SSL], and renamed to "KeyFile"
  51. "SSLKeyFilePassword" -> [SSL], and renamed to "KeyFilePassword"
  52. "SSLPorts" -> [SSL], and renamed to "Ports"
  53. "SyslogFacility" -> [Options]
  54. "WebircPassword" -> [Options]
  55. You should adjust your ngircd.conf and run "ngircd --configtest" to make
  56. sure that your settings are correct and up to date!
  57. Differences to version 16
  58. - Changes to the "MotdFile" specified in ngircd.conf now require a ngircd
  59. configuration reload to take effect (HUP signal, REHASH command).
  60. Differences to version 0.9.x
  61. - The option of the configure script to enable support for Zeroconf/Bonjour/
  62. Rendezvous/WhateverItIsNamedToday has been renamed:
  63. --with-rendezvous -> --with-zeroconf
  64. Differences to version 0.8.x
  65. - The maximum length of passwords has been raised to 20 characters (instead
  66. of 8 characters). If your passwords are longer than 8 characters then they
  67. are cut at an other position now.
  68. Differences to version 0.6.x
  69. - Some options of the configure script have been renamed:
  70. --disable-syslog -> --without-syslog
  71. --disable-zlib -> --without-zlib
  72. Please call "./configure --help" to review the full list of options!
  73. Differences to version 0.5.x
  74. - Starting with version 0.6.0, other servers are identified using asynchronous
  75. passwords: therefore the variable "Password" in [Server]-sections has been
  76. replaced by "MyPassword" and "PeerPassword".
  77. - New configuration variables, section [Global]: MaxConnections, MaxJoins
  78. (see example configuration file "doc/sample-ngircd.conf"!).
  79. II. Standard Installation
  80. ~~~~~~~~~~~~~~~~~~~~~~~~~
  81. ngIRCd is developed for UNIX-based systems, which means that the installation
  82. on modern UNIX-like systems that are supported by GNU autoconf and GNU
  83. automake ("configure") should be no problem.
  84. The normal installation procedure after getting (and expanding) the source
  85. files (using a distribution archive or GIT) is as following:
  86. 0) Satisfy prerequisites
  87. 1) ./ [only necessary when using GIT]
  88. 2) ./configure
  89. 3) make
  90. 4) make install
  91. (Please see details below!)
  92. Now the newly compiled executable "ngircd" is installed in its standard
  93. location, /usr/local/sbin/.
  94. The next step is to configure and afterwards starting the daemon. Please
  95. have a look at the ngircd(8) and ngircd.conf(5) manual pages for details
  96. and all possible options -- and don't forget to run "ngircd --configtest"
  97. to validate your configuration file!
  98. If no previous version of the configuration file exists (the standard name
  99. is /usr/local/etc/ngircd.conf), a sample configuration file containing all
  100. possible options will be installed there. You'll find its template in the
  101. doc/ directory: sample-ngircd.conf.
  102. 0): Satisfy prerequisites
  103. When building from source, you'll need some other software to build ngIRCd:
  104. for example a working C compiler, make tool, GNU automake and autoconf (only
  105. when not using a distribution archive), and a few libraries depending on the
  106. features you want to compile in (like IDENT support, SSL, and PAM).
  107. If you are using one of the "big" operating systems or Linux distributions,
  108. you can use the following commands to install all the required packages to
  109. build the sources including all optional features and to run the test suite:
  110. * RedHat / Fedora based distributions:
  111. yum install \
  112. autoconf automake expect gcc glibc-devel gnutls-devel \
  113. libident-devel make pam-devel tcp_wrappers-devel telnet zlib-devel
  114. * Debian / Ubuntu based distributions:
  115. apt-get install \
  116. autoconf automake build-essential expect libgnutls-dev \
  117. libident-dev libpam-dev libwrap0-dev libz-dev telnet
  118. 1): ""
  119. The first step,, is only necessary if the configure-script isn't
  120. already generated. This never happens in official ("stable") releases in
  121. tar.gz-archives, but when using GIT.
  122. This step is therefore only interesting for developers.
  123. produces the's, which are necessary for the configure
  124. script itself, and some more files for make. To run you'll need
  125. GNU autoconf and GNU automake: at least autoconf 2.61 and automake 1.10 are
  126. requird, newer is better. But don't use automake 1.12 or newer for creating
  127. distribution archives: it will work but lack "de-ANSI-fucation" support in the
  128. generated Makefile's! Stick with automake 1.11.x for this purpose ...
  129. So automake 1.11.x and autoconf 2.67+ is recommended.
  130. Again: "end users" do not need this step and neither need GNU autoconf nor GNU
  131. automake at all!
  132. 2): "./configure"
  133. The configure-script is used to detect local system dependencies.
  134. In the perfect case, configure should recognize all needed libraries, header
  135. files and so on. If this shouldn't work, "./configure --help" shows all
  136. possible options.
  137. In addition, you can pass some command line options to "configure" to enable
  138. and/or disable some features of ngIRCd. All these options are shown using
  139. "./configure --help", too.
  140. Compiling a static binary will avoid you the hassle of feeding a chroot dir
  141. (if you want use the chroot feature). Just do something like:
  142. CFLAGS=-static ./configure [--your-options ...]
  143. Then you can use a void directory as ChrootDir (like OpenSSH's /var/empty).
  144. 3): "make"
  145. The make command uses the Makefiles produced by configure and compiles the
  146. ngIRCd daemon.
  147. 4): "make install"
  148. Use "make install" to install the server and a sample configuration file on
  149. the local system. Normally, root privileges are necessary to complete this
  150. step. If there is already an older configuration file present, it won't be
  151. overwritten.
  152. These files and folders will be installed by default:
  153. - /usr/local/sbin/ngircd: executable server
  154. - /usr/local/etc/ngircd.conf: sample configuration (if not already present)
  155. - /usr/local/share/doc/ngircd/: documentation
  156. - /usr/local/share/man/: manual pages
  157. III. Additional features
  158. ~~~~~~~~~~~~~~~~~~~~~~~~
  159. The following optional features can be compiled into the daemon by passing
  160. options to the "configure" script. Most options can handle a <path> argument
  161. which will be used to search for the required libraries and header files in
  162. the given paths ("<path>/lib/...", "<path>/include/...") in addition to the
  163. standard locations.
  164. * Syslog Logging (autodetected by default):
  165. --with-syslog[=<path>] / --without-syslog
  166. Enable (disable) support for logging to "syslog", which should be
  167. available on most modern UNIX-like operating systems by default.
  168. * ZLib Compression (autodetected by default):
  169. --with-zlib[=<path>] / --without-zlib
  170. Enable (disable) support for compressed server-server links.
  171. The Z compression library ("libz") is required for this option.
  172. * IO Backend (autodetected by default):
  173. --with-select[=<path>] / --without-select
  174. --with-poll[=<path>] / --without-poll
  175. --with-devpoll[=<path>] / --without-devpoll
  176. --with-epoll[=<path>] / --without-epoll
  177. --with-kqueue[=<path>] / --without-kqueue
  178. ngIRCd can use different IO "backends": the "old school" select() and poll()
  179. API which should be supported by most UNIX-like operating systems, or the
  180. more efficient and flexible epoll() (Linux >=2.6), kqueue() (BSD) and
  181. /dev/poll APIs.
  182. By default the IO backend is autodetected, but you can use "--without-xxx"
  183. to disable a more enhanced API.
  184. When using the epoll() API, support for select() is compiled in as well by
  185. default to enable the binary to run on older Linux kernels (<2.6), too.
  186. * IDENT-Support:
  187. --with-ident[=<path>]
  188. Include support for IDENT ("AUTH") lookups. The "ident" library is
  189. required for this option.
  190. * TCP-Wrappers:
  191. --with-tcp-wrappers[=<path>]
  192. Include support for Wietse Venemas "TCP Wrappers" to limit client access
  193. to the daemon, for example by using "/etc/hosts.{allow|deny}".
  194. The "libwrap" is required for this option.
  195. * PAM:
  196. --with-pam[=<path>]
  197. Enable support for PAM, the Pluggable Authentication Modules library.
  198. See doc/PAM.txt for details.
  199. * SSL:
  200. --with-openssl[=<path>]
  201. --with-gnutls[=<path>]
  202. Enable support for SSL/TLS using OpenSSL or gnutls libraries.
  203. See doc/SSL.txt for details.
  204. * IPv6:
  205. --enable-ipv6
  206. Adds support for version 6 of the Internet Protocol.
  207. IV. Useful make-targets
  208. ~~~~~~~~~~~~~~~~~~~~~~~
  209. The Makefile produced by the configure-script contains always these useful
  210. targets:
  211. - clean: delete every product from the compiler/linker
  212. next step: -> make
  213. - distclean: the above plus erase all generated Makefiles
  214. next step: -> ./configure
  215. - maintainer-clean: erase all automatic generated files
  216. next step: -> ./
  217. V. Sample configuration file ngircd.conf
  218. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  219. In the sample configuration file, there are comments beginning with "#" OR
  220. ";" -- this is only for the better understanding of the file.
  221. The file is separated in five blocks: [Global], [Features], [Operator],
  222. [Server], and [Channel].
  223. In the [Global] section, there is the main configuration like the server
  224. name and the ports, on which the server should be listening. Options in
  225. the [Features] section enable or disable functionality in the daemon.
  226. IRC operators of this server are defined in [Operator] blocks, remote
  227. servers are configured in [Server] sections, and [Channel] blocks are
  228. used to configure pre-defined ("persistent") IRC channels.
  229. The meaning of the variables in the configuration file is explained in the
  230. "doc/sample-ngircd.conf", which is used as sample configuration file in
  231. /usr/local/etc after running "make install" (if you don't already have one)
  232. and in the ngircd.conf(5) manual page.
  233. VI. Command line options
  234. ~~~~~~~~~~~~~~~~~~~~~~~~
  235. These parameters could be passed to the ngIRCd:
  236. -f, --config <file>
  237. The daemon uses the file <file> as configuration file rather than
  238. the standard configuration /usr/local/etc/ngircd.conf.
  239. -n, --nodaemon
  240. ngIRCd should be running as a foreground process.
  241. -p, --passive
  242. Server-links won't be automatically established.
  243. -t, --configtest
  244. Reads, validates and dumps the configuration file as interpreted
  245. by the server. Then exits.
  246. Use "--help" to see a short help text describing all available parameters
  247. the server understands, with "--version" the ngIRCd shows its version
  248. number. In both cases the server exits after the output.
  249. Please see the ngircd(8) manual page for complete details!