- ngIRCd Users - lists.barton.de

ngIRCd 21~daily (38) on Linux 1.2.13 - works
by Goetz Hoffart 06 Jan '14

06 Jan '14

Cool! $ uname -a Linux susie.hoffart.de 1.2.13 #6 Sun Nov 5 02:50:37 MET 1995 i686 ngIRCd 21~38-ge2b85cc has been configured with the following options: Host: i686-pc-linux-gnu Compiler: gcc Compiler flags: -g -O2 -pipe -W -Wall -Wpointer-arith -Wstrict-prototypes -DSYSCONFDIR='"$(sysconfdir)"' -DDOCDIR='"$(docdir)"' 'ngircd' binary: /usr/local/sbin Configuration file: /usr/local/etc Manual pages: /usr/local/share/man Documentation: /usr/local/share/doc/ngircd Syslog support: yes Enable debug code: no zlib compression: no IRC sniffer: no Use TCP Wrappers: no Strict RFC mode: no IDENT support: no IRC+ protocol: yes IPv6 protocol: no I/O backend: select() PAM support: no SSL support: no libiconv support: no platformtest.sh: Running "make check" ... ** WARNING: The vsnprintf() function of this system isn't standard ** conformant and returns a WRONG result: -1 (should be 12)! The test ** result has been ignored but may lead to errors during execution! the executable works ("runs") as expected --+ tests run successfully ("make check") --+ | ngIRCd compiles ("make") --+ | | ./configure works --+ | | | | | | | Platform Compiler ngIRCd Date Tester C M T R * --------------------------- ------------ ---------- -------- -------- - - - - - i686/pc/linux-gnu 2.7.2 21~daily 14-01-06 goetz Y Y Y Y 1

2 1

ngIRCd 21~daily on SuSE 12/95, Kernel 1.2.13
by Goetz Hoffart 05 Jan '14

05 Jan '14

After I read some wondering about gcc 2.8.x and its age in the IRC channel, I thought: now for something really old (at least for Linux): Linux kernel version 1.2.13 and GCC 2.7.2. GCC 1.x was not that common on Linux system, I'll try that on a SunOS-machine later. And ngIRCd works! The only problem: the automated tests: > platformtest.sh: Running "make check" ... > Oops, test for vsnprintf return code failed!? Here are the results: susie:~/ngircd-21~34-g4d4512c $ uname -a Linux susie.hoffart.de 1.2.13 #6 Sun Nov 5 02:50:37 MET 1995 i686 susie:~/ngircd-21~34-g4d4512c $ date Sat Jan 4 19:18:54 MET 2014 ngIRCd 21~34-g4d4512c has been configured with the following options: Host: i686-pc-linux-gnu Compiler: gcc Compiler flags: -g -O2 -pipe -W -Wall -Wpointer-arith -Wstrict-prototypes -DSYSCONFDIR='"$(sysconfdir)"' -DDOCDIR='"$(docdir)"' 'ngircd' binary: /usr/local/sbin Configuration file: /usr/local/etc Manual pages: /usr/local/share/man Documentation: /usr/local/share/doc/ngircd Syslog support: yes Enable debug code: no zlib compression: no IRC sniffer: no Use TCP Wrappers: no Strict RFC mode: no IDENT support: no IRC+ protocol: yes IPv6 protocol: no I/O backend: select() PAM support: no SSL support: no libiconv support: no susie:~/ngircd-21~34-g4d4512c $ contrib/platformtest.sh platformtest.sh: Checking ngIRCd base source directory ... platformtest.sh: Checking for GIT tree ... platformtest.sh: Checking for "./configure" script ... platformtest.sh: Running "./configure" script ... platformtest.sh: Running "make" ... platformtest.sh: Running "make check" ... Oops, test for vsnprintf return code failed!? make[3]: *** [check-TESTS] Error 1 make[2]: *** [check-am] Error 2 make[1]: *** [check-recursive] Error 1 make: *** [check-recursive] Error 1 the executable works ("runs") as expected --+ tests run successfully ("make check") --+ | ngIRCd compiles ("make") --+ | | ./configure works --+ | | | | | | | Platform Compiler ngIRCd Date Tester C M T R * --------------------------- ------------ ---------- -------- -------- - - - - - i686/pc/linux-gnu 2.7.2 21~daily 14-01-04 goetz Y Y N Y 1 Regards Götz

2 3

ngIRCd 21 on PowerPC G4, OS X 10.5.8
by Götz Hoffart 04 Jan '14

04 Jan '14

$ uname -a Darwin PowerBook-G4-12.local 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:57:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_PPC Power Macintosh $ date Sa 4 Jan 2014 18:38:20 CET $ sw_vers ProductName: Mac OS X ProductVersion: 10.5.8 BuildVersion: 9L31a $ system_profiler […] hw.model: PowerBook6,8 hw.memsize: 1342177280 hw.machine: Power Macintosh hw.ncpu: 1 ngIRCd 21 has been configured with the following options: Host: powerpc-apple-darwin9.8.0 Compiler: gcc -std=gnu99 Compiler flags: -g -O2 -pipe -W -Wall -Wpointer-arith -Wstrict-prototypes -fstack-protector -DSYSCONFDIR='"$(sysconfdir)"' -DDOCDIR='"$(docdir)"' Libraries: -lz 'ngircd' binary: /usr/local/sbin Configuration file: /usr/local/etc Manual pages: /usr/local/share/man Documentation: /usr/local/share/doc/ngircd Syslog support: yes Enable debug code: no zlib compression: yes IRC sniffer: no Use TCP Wrappers: no Strict RFC mode: no IDENT support: no IRC+ protocol: yes IPv6 protocol: no I/O backend: kqueue() PAM support: no SSL support: no libiconv support: no the executable works ("runs") as expected --+ tests run successfully ("make check") --+ | ngIRCd compiles ("make") --+ | | ./configure works --+ | | | | | | | Platform Compiler ngIRCd Date Tester C M T R * --------------------------- ------------ ---------- -------- -------- - - - - - powerpc/apple/darwin9.8.0 gcc 4.0.1 21 14-01-04 goetz Y Y Y Y 3

2 1

SSL issue.
by k0nsl 14 Dez '13

14 Dez '13

Hi all, I have compiled ngircd as per the usual steps, everything does work, except the most crucial bit for me - SSL. This is what it shows during debug: [root@feisty ngircd-20.3]# /usr/local/sbin/ngircd -n [26473:5 0] ngIRCd 21~19-g444308c-IRCPLUS+SSL+SYSLOG+ZLIB-x86_64/unknown/linux-gnu started. [26473:6 0] Using configuration file "/usr/local/etc/ngircd.conf" ... [26473:6 0] OpenSSL 1.0.1e-fips 11 Feb 2013 initialized. [26473:6 0] ServerUID must not be root(0), using "nobody" instead. [26473:6 0] Running as user nobody(99), group nobody(99), with PID 26473. [26473:6 0] Not running with changed root directory. [26473:6 0] IO subsystem: epoll (hint size 100, initial maxfd 100, masterfd 3). [26473:6 0] Created pre-defined channel "#k0nsl". [26473:6 0] Now listening on [0.0.0.0]:6668 (socket 6). [26473:6 0] Now listening on [0.0.0.0]:6669 (socket 7). [26473:6 0] Now listening on [0.0.0.0]:6667 (socket 8). [26473:6 0] Now listening on [0.0.0.0]:6697 (socket 9). [26473:5 54] Client unregistered (connection 10): SSL accept error, closing socket. [26473:6 54] Connection 10 with "x.x.x.x:38879" closed (in: 0.0k, out: 0.0k). [26473:6 62] Accepted connection 10 from "x.x.x.x:39102" on socket 8. [26473:3 62] SSL protocol error: SSL_accept (error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol) [26473:6 62] Shutting down connection 10 (SSL accept error, closing socket) with "x.x.x.x:39102" ... [26473:5 62] Client unregistered (connection 10): SSL accept error, closing socket. [26473:6 62] Connection 10 with "x.x.x.x:39102" closed (in: 0.0k, out: 0.0k). [26473:6 64] Accepted connection 10 from "x.x.x.x:39148" on socket 8. [26473:3 65] SSL protocol error: SSL_accept (error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol) [26473:6 65] Shutting down connection 10 (SSL accept error, closing socket) with "x.x.x.x:39148" ... [26473:5 65] Client unregistered (connection 10): SSL accept error, closing socket. [26473:6 65] Connection 10 with "x.x.x.x:39148" closed (in: 0.0k, out: 0.0k). [26473:6 66] Accepted connection 10 from "x.x.x.x:39216" on socket 8. [26473:3 66] SSL protocol error: SSL_accept (error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol) [26473:6 66] Shutting down connection 10 (SSL accept error, closing socket) with "x.x.x.x:39216" ... [26473:5 66] Client unregistered (connection 10): SSL accept error, closing socket. [26473:6 66] Connection 10 with "x.x.x.x:39216" closed (in: 0.0k, out: 0.0k). ^C[26473:5 67] Server going down NOW! [26473:6 67] Shutting down all listening sockets (4 total) ... [26473:6 67] ngIRCd done, served 10 connections. Any ideas? Faithfully, Kuensl

2 1

ngIRCd 21 with Open Watcom 1.9: fails to complete autoconf
by Götz Hoffart 06 Dez '13

06 Dez '13

Hi, I'm having problems compiling ngIRCd 21 with Open Watcom 1.9. I’ve gotten so far that the compiler is recognized and accepted by autoconf 2.67 [1], but it fails shortly after that: <https://s1.hoffart.de/temp/ngircd-21-on-watcom.txt> I searched for the given error message, but it seems to be known since 2003 and a lot of different explanations, not necessarily Watcom-related. Should I search for Open Watcom specific problems or should I stay here with that problem? [1]: Machine: x86_64, Debian GNU/Linux 6.x, newest patchlevel Regards Götz -- ③rz :: Regionales Retro-Rechenzentrum, Freiburg :: http://www.3rz.org Für Freunde außer-gewöhnlicher elektronischer Datenverarbeitung

1 0

SSL error: Could not negotiate a supported cipher suite
by Nicolas Leclercq 03 Dez '13

03 Dez '13

Hello gentlemen, I am trying to set up a 2 node ngIRCd cluster. Clients can connect to both nodes with SSL enabled (tested with irssi or znc), but the 2 servers does not want to talk together : SSL error: Could not negotiate a supported cipher suite. [gnutls_handshake] Packages version : libgnutls26 2.12.23-1ubuntu1.1 ngircd 21-1 Here is my configurations : IRC0 : [SSL] CertFile = /etc/ngircd/irc0_crt.pem DHFile = /etc/ngircd/dh.pem KeyFile = /etc/ngircd/irc0_privatekey.pem Ports = 50799 [Server] Name = irc2.xxx.net Host = irc2.xxx.net Port = 50799 PeerPassword = toto MyPassword = tata SSLConnect = yes Group = 1 IRC2 : [SSL] CertFile = /etc/ngircd/irc2_crt.pem DHFile = /etc/ngircd/dh.pem KeyFile = /etc/ngircd/irc2_privatekey.pem Ports = 50799 [Server] Name = irc0. xxx.net Host = irc0. xxx.net Port = 50799 Passive = yes MyPassword = tata PeerPassword = toto SSLConnect = yes Group = 1 And the log messages : IRC0 : Dec 2 17:42:43 maxwell ngircd[23501]: /etc/ngircd/ngircd.conf: line 148: "Ident = yes", but ngircd was built without IDENT support! Dec 2 17:42:43 maxwell ngircd[23501]: Can't read help text file "/usr/share/doc/ngircd/Commands.txt": No such file or directory Dec 2 17:42:43 maxwell ngircd[23501]: No help text available, HELP command will be of limited use. Dec 2 17:42:43 maxwell ngircd[23501]: ngIRCd 21-IPv6+IRCPLUS+SSL+SYSLOG+ZLIB-i686/pc/linux-gnu started. Dec 2 17:42:43 maxwell ngircd[23501]: Using configuration file "/etc/ngircd/ngircd.conf" ... Dec 2 17:42:43 maxwell ngircd[23501]: GnuTLS 2.12.23 initialized. Dec 2 17:42:43 maxwell ngircd[23502]: Running as user irc(39), group irc(39), with PID 23502. Dec 2 17:42:43 maxwell ngircd[23502]: Not running with changed root directory. Dec 2 17:42:43 maxwell ngircd[23502]: IO subsystem: epoll (hint size 100, initial maxfd 100, masterfd 4). Dec 2 17:42:43 maxwell ngircd[23502]: Created pre-defined channel "#hnng". Dec 2 17:42:43 maxwell ngircd[23502]: Now listening on [0::]:50799 (socket 8). Dec 2 17:42:43 maxwell ngircd[23502]: Now listening on [0.0.0.0]:50799 (socket 9). Dec 2 17:42:44 maxwell ngircd[23502]: Preparing to establish a new server link for "irc2.xxx.net" ... Dec 2 17:42:44 maxwell ngircd[23502]: Establishing connection for "irc2.xxx.net" to "irc2.xxx.net:50799 » (—.—.—.—), socket 10 ... Dec 2 17:42:44 maxwell ngircd[23502]: SSL error: A TLS packet with unexpected length was received. [gnutls_handshake]. Dec 2 17:42:44 maxwell ngircd[23502]: SSL connection on socket 10 failed! Dec 2 17:42:44 maxwell ngircd[23502]: Shutting down connection 10 (Can't connect) with "irc2.xxx.net:50799" ... Dec 2 17:42:44 maxwell ngircd[23502]: Client unregistered (connection 10): Can't connect. Dec 2 17:42:44 maxwell ngircd[23502]: Connection 10 with "irc2.xxx.net:50799" closed (in: 0.0k, out: 0.0k). IRC2: Dec 2 17:43:01 ampere ngircd[28153]: Accepted connection 15 from "—.—.—.—:38933" on socket 9. Dec 2 17:43:01 ampere ngircd[28153]: SSL error: Could not negotiate a supported cipher suite. [gnutls_handshake]. Dec 2 17:43:01 ampere ngircd[28153]: Shutting down connection 15 (SSL accept error, closing socket) with "—.—.—.—:38933" ... Dec 2 17:43:01 ampere ngircd[28153]: Client unregistered (connection 15): SSL accept error, closing socket. Dec 2 17:43:01 ampere ngircd[28153]: Connection 15 with "—.—.—.—:38933" closed (in: 0.0k, out: 0.0k). Thanks in advance for your help. -- Nicolas

2 1

Patch submission
by Matt Pepe 03 Dez '13

03 Dez '13

Hello, A couple of months ago, I started searching for a well-maintained IRC server that I could use as a basis for internal use at my organization. We are fairly security-conscious and we needed a solid server that supported SSL and PAM authentication. So, first - thanks for the great work you all are doing. We had a couple of other requirements, especially if we were going to expose the port on an externally-accessible address. The first was to allow only authorized connections from clients who presented a valid SSL certificate. This is the first half of the patch. If linked with GNUTLS, the patch will allow the admin to limit connections to clients that present a valid cert, signed by a valid CA in the server cert's chain of trust. It also supports revocation lists. Second is the addition of a new caching process called authcache. We wire up authentication through PAM and on to an one-time password infrastructure. We chose to do this since IRC clients don't bother trying to keep that password protected... at all.. It is even written to the client's history files in many cases. To shorten the window of opportunity for exposed credentials, the user enters an OTP when authenticating. Naturally, with the manner and frequency in which IRC clients disconnect and reconnect, entering credentials repeatedly would be infuriating (and impossible with most clients.) Authcache will create a token from the hash of the original IRC name, source connection hostname/address, and if SSL is enabled, the client certificate's hash, and store it in a table for a user-configurable amount of time. This table is consulted when a new connection is made and bypasses the internal authentication step if a record is found. A user or admin directed logoff will clear the connection's entry. Known issues... 1. Requires GNUTLS 3.x. I chose to use newer methods for CRL and verification checks. I would like to figure out what version of GNUTLS is installed and call the appropriate methods, but this leads me into the next item... 2. Lack of good Autoconf checks. As noted above, it requires GNUTLS 3.x. I am sadly not familiar enough with autoconf to put together a robust means of testing for that. 3. I have not yet written an equivalent CRL and Client cert check for libssl. 4. No changes to your unit tests. I hang my head in shame... I know there are a few items in that list that are solvable after some research and fiddling (autoconf, libssl). I haven't had a chance to fix those items yet - I hope to at some point, but who knows when. As you can tell by the dates in the patchfile, I've been sitting on the changes for a bit, hoping for time to get autoconf sorted out. Its been months, so I figured I'd put the patches out there in case they are useful in this configuration. Again, thanks for an awesome server - I hope you find these patches as useful as I have. - Matt

1 0

ngIRCd 21 with nwcc
by Götz Hoffart 03 Dez '13

03 Dez '13

ngIRCd 21 builds and works fine with nwcc: ngIRCd 21 has been configured with the following options: Host: x86_64-unknown-linux-gnu Compiler: /opt/nwcc/bin/nwcc Compiler flags: -g -DSYSCONFDIR='"$(sysconfdir)"' -DDOCDIR='"$(docdir)"' Libraries: -lz 'ngircd' binary: /usr/local/sbin Configuration file: /usr/local/etc Manual pages: /usr/local/share/man Documentation: /usr/local/share/doc/ngircd Syslog support: yes Enable debug code: no zlib compression: yes IRC sniffer: no Use TCP Wrappers: no Strict RFC mode: no IDENT support: no IRC+ protocol: yes IPv6 protocol: no I/O backend: epoll(), select() PAM support: no SSL support: no libiconv support: no the executable works ("runs") as expected --+ tests run successfully ("make check") --+ | ngIRCd compiles ("make") --+ | | ./configure works --+ | | | | | | | Platform Compiler ngIRCd Date Tester C M T R * --------------------------- ------------ ---------- -------- -------- - - - - - x86_64/unknown/linux-gnu nwcc 0.8.2 21 13-12-01 goetz Y Y Y Y 1 Grüße Götz

2 1

ngIRCd on NetBSD 1.5.2: -o-
by Götz Hoffart 03 Dez '13

03 Dez '13

Works (I can connect with clients), but checks fail: ngIRCd 21 has been configured with the following options: Host: i386-unknown-netbsdelf1.5.2 Compiler: gcc Compiler flags: -g -O2 -pipe -W -Wall -Wpointer-arith -Wstrict-prototypes -DSYSCONFDIR='"$(sysconfdir)"' -DDOCDIR='"$(docdir)"' Libraries: -lz 'ngircd' binary: /usr/local/sbin Configuration file: /usr/local/etc Manual pages: /usr/local/share/man Documentation: /usr/local/share/doc/ngircd Syslog support: yes Enable debug code: no zlib compression: yes IRC sniffer: no Use TCP Wrappers: no Strict RFC mode: no IDENT support: no IRC+ protocol: yes IPv6 protocol: no I/O backend: poll() PAM support: no SSL support: no libiconv support: no the executable works ("runs") as expected --+ tests run successfully ("make check") --+ | ngIRCd compiles ("make") --+ | | ./configure works --+ | | | | | | | Platform Compiler ngIRCd Date Tester C M T R * --------------------------- ------------ ---------- -------- -------- - - - - - i386/unknown/netbsdelf1.5.2 egcs-1.1.2 21 13-11-25 goetz Y Y N Y # uname -a NetBSD 1.5.2 NetBSD 1.5.2 (GENERIC) #3: Sat Aug 18 23:37:05 CEST 2001 he@hamster.urc.uninett.no:/usr/src/sys/arch/i386/compile/GENERIC i386

2 1

ngircd build failure on raspbian
by peter green 02 Dez '13

02 Dez '13

I run a debian derivative called raspbian aimed primerally at the raspberry pi. While building ngircd on the raspbian jessie autobuilders I got a testsuite failure with an explicit request to report to this email address, so I am doing so. running misc-test ... failure! FAIL: misc-test <--snip--> running who-test ... failure! FAIL: who-test <--snip--> =========================================== 2 of 16 tests failed Please report to ngircd-ml(a)ngircd.barton.de =========================================== The full log is available at http://buildd.raspbian.org/status/fetch.php?pkg=ngircd&arch=armhf&ver=21-1&…

2 2

ngIRCd 21 with Open64 cc
by Götz Hoffart 30 Nov '13

30 Nov '13

Builds and works correctly. Several warnings are shown: opencc WARNING: unknown flag: -fstack-protector portabtest.c: In function 'main': portabtest.c:43: warning: the address of 'snprintf' will always evaluate as 'true' portabtest.c:44: warning: the address of 'vsnprintf' will always evaluate as 'true' portabtest.c:45: warning: the address of 'strlcpy' will always evaluate as 'true' portabtest.c:46: warning: the address of 'strlcat' will always evaluate as 'true' opencc WARNING: unknown flag: -fstack-protector ngIRCd 21 has been configured with the following options: Host: x86_64-unknown-linux-gnu Compiler: /opt/open64-5.0/bin/opencc -std=gnu99 Compiler flags: -g -O2 -pipe -W -Wall -Wpointer-arith -Wstrict-prototypes -fstack-protector -DSYSCONFDIR='"$(sysconfdir)"' -DDOCDIR='"$(docdir)"' Libraries: -lz 'ngircd' binary: /usr/local/sbin Configuration file: /usr/local/etc Manual pages: /usr/local/share/man Documentation: /usr/local/share/doc/ngircd Syslog support: yes Enable debug code: no zlib compression: yes IRC sniffer: no Use TCP Wrappers: no Strict RFC mode: no IDENT support: no IRC+ protocol: yes IPv6 protocol: no I/O backend: epoll(), select() PAM support: no SSL support: no libiconv support: no the executable works ("runs") as expected --+ tests run successfully ("make check") --+ | ngIRCd compiles ("make") --+ | | ./configure works --+ | | | | | | | Platform Compiler ngIRCd Date Tester C M T R * --------------------------- ------------ ---------- -------- -------- - - - - - x86_64/unknown/linux-gnu Open64 21 13-11-30 goetz Y Y Y Y 1 Grüße Götz

1 0

ngIRCd 21 with Solaris Studio 12.3 cc
by Götz Hoffart 30 Nov '13

30 Nov '13

Builds and works correctly. Three warnings are thrown: "io.c", line 789: warning: statement not reached "io.c", line 885: warning: statement not reached "io.c", line 908: warning: statement not reached $ /opt/solarisstudio12.3/bin/cc -V cc: Sun C 5.12 Linux_i386 2011/11/16 ngIRCd 21 has been configured with the following options: Host: x86_64-unknown-linux-gnu Compiler: /opt/solarisstudio12.3/bin/cc Compiler flags: -g -DSYSCONFDIR='"$(sysconfdir)"' -DDOCDIR='"$(docdir)"' Libraries: -lz 'ngircd' binary: /usr/local/sbin Configuration file: /usr/local/etc Manual pages: /usr/local/share/man Documentation: /usr/local/share/doc/ngircd Syslog support: yes Enable debug code: no zlib compression: yes IRC sniffer: no Use TCP Wrappers: no Strict RFC mode: no IDENT support: no IRC+ protocol: yes IPv6 protocol: no I/O backend: epoll(), select() PAM support: no SSL support: no libiconv support: no the executable works ("runs") as expected --+ tests run successfully ("make check") --+ | ngIRCd compiles ("make") --+ | | ./configure works --+ | | | | | | | Platform Compiler ngIRCd Date Tester C M T R * --------------------------- ------------ ---------- -------- -------- - - - - - x86_64/unknown/linux-gnu unknown 21 13-11-30 goetz Y Y Y Y 1 Grüße Götz

1 0

ngIRCd 21 with tcc
by Götz Hoffart 30 Nov '13

30 Nov '13

Builds and works correctly: ngIRCd 21 has been configured with the following options: Host: x86_64-unknown-linux-gnu Compiler: tcc Compiler flags: -g -DSYSCONFDIR='"$(sysconfdir)"' -DDOCDIR='"$(docdir)"' Libraries: -lz 'ngircd' binary: /usr/local/sbin Configuration file: /usr/local/etc Manual pages: /usr/local/share/man Documentation: /usr/local/share/doc/ngircd Syslog support: yes Enable debug code: no zlib compression: yes IRC sniffer: no Use TCP Wrappers: no Strict RFC mode: no IDENT support: no IRC+ protocol: yes IPv6 protocol: no I/O backend: epoll(), select() PAM support: no SSL support: no libiconv support: no the executable works ("runs") as expected --+ tests run successfully ("make check") --+ | ngIRCd compiles ("make") --+ | | ./configure works --+ | | | | | | | Platform Compiler ngIRCd Date Tester C M T R * --------------------------- ------------ ---------- -------- -------- - - - - - x86_64/unknown/linux-gnu tcc 0.9.25 21 13-11-30 goetz Y Y Y Y 1 Grüße Götz

1 0

ngIRCd 21 on OpenBSD 5.3 & 5.4 i386
by Goetz Hoffart 28 Nov '13

28 Nov '13

Hi, ngIRCd 21 works fine on both OpenBSD 5.3 and 5.4. Unfortunately, as a package only ngIRCd 20.2 is available. See attachments. Regards Goetz

1 0

ngIRCd 21 on MIPSel
by Goetz Hoffart 24 Nov '13

24 Nov '13

ngIRCd 21 has been configured with the following options: Host: mipsel-unknown-linux-gnu Compiler: gcc -std=gnu99 Compiler flags: -g -O2 -pipe -W -Wall -Wpointer-arith -Wstrict-prototypes -fstack-protector -DSYSCONFDIR='"$(sysconfdir)"' -DDOCDIR='"$(docdir)"' Libraries: -lz 'ngircd' binary: /usr/local/sbin Configuration file: /usr/local/etc Manual pages: /usr/local/share/man Documentation: /usr/local/share/doc/ngircd Syslog support: yes Enable debug code: no zlib compression: yes IRC sniffer: no Use TCP Wrappers: no Strict RFC mode: no IDENT support: no IRC+ protocol: yes IPv6 protocol: no I/O backend: epoll(), select() PAM support: no SSL support: no libiconv support: no [...] the executable works ("runs") as expected --+ tests run successfully ("make check") --+ | ngIRCd compiles ("make") --+ | | ./configure works --+ | | | | | | | Platform Compiler ngIRCd Date Tester C M T R * --------------------------- ------------ ---------- -------- -------- - - - - - mipsel/unknown/linux-gnu gcc 4.4.5 21 13-11-24 goetz Y Y Y Y 1 # uname -a Linux kubus 2.6.32-5-r5k-cobalt #1 Wed Jun 15 00:53:04 UTC 2011 mips #GNU/Linux $ cat /proc/cpuinfo system type : Cobalt Qube2 processor : 0 cpu model : Nevada V10.0 FPU V10.0 BogoMIPS : 248.32 wait instruction : yes microsecond timers : yes tlb_entries : 48 extra interrupt vector : yes hardware watchpoint : no ASEs implemented : shadow register sets : 1 core : 0 VCED exceptions : not available VCEI exceptions : not available

2 1

ngIRCd 21 on Minix + clang
by Götz Hoffart 22 Nov '13

22 Nov '13

Hi, I'm failing to get ngIRCd 21 running on Minix 3.2.1/x86. # ./configure […] ngIRCd 21 has been configured with the following options: Host: i686-pc-minix Compiler: cc Compiler flags: -g -O2 -pipe -W -Wall -Wpointer-arith -Wstrict-prototypes -fstack-protector -DSYSCONFDIR='"$(sysconfdir)"' -DDOCDIR='"$(docdir)"' Libraries: -lz 'ngircd' binary: /usr/local/sbin Configuration file: /usr/local/etc Manual pages: /usr/local/share/man Documentation: /usr/local/share/doc/ngircd Syslog support: yes Enable debug code: no zlib compression: yes IRC sniffer: no Use TCP Wrappers: no Strict RFC mode: no IDENT support: no IRC+ protocol: yes IPv6 protocol: no I/O backend: poll() PAM support: no SSL support: no libiconv support: no # contrib/platformtest.sh platformtest.sh: Checking ngIRCd base source directory ... platformtest.sh: Checking for GIT tree ... platformtest.sh: Checking for "./configure" script ... platformtest.sh: Running "./configure" script ... platformtest.sh: Running "make" ... clang: warning: argument unused during compilation: '-g' platformtest.sh: Running "make check" ... clang: warning: argument unused during compilation: '-g' the executable works ("runs") as expected --+ tests run successfully ("make check") --+ | ngIRCd compiles ("make") --+ | | ./configure works --+ | | | | | | | Platform Compiler ngIRCd Date Tester C M T R * --------------------------- ------------ ---------- -------- -------- - - - - - i686/pc/minix clang 3.1 21 13-11-21 root Y Y N Y # src/ngircd/ngircd -npf doc/sample-ngircd.conf [8822:3 0] Can't read MOTD file "/usr/local/etc/ngircd.motd": no such file or directory [8822:3 0] Can't read help text file "/usr/local/share/doc/ngircd/Commands.txt": no such file or directory [8822:4 0] No help text available, HELP command will be of limited use. [8822:4 0] Not specifying a full path name to "doc/sample-ngircd.conf" can cause problems when rehashing the server! [8822:4 0] No administrative information configured but required by RFC! [8822:5 0] ngIRCd 21-IRCPLUS+SYSLOG+ZLIB-i686/pc/minix started. [8822:6 0] Using configuration file "doc/sample-ngircd.conf" ... [8822:6 0] ServerUID must not be root(0), using "nobody" instead. [8822:3 0] Can't drop supplementary group IDs: bad address! [8822:1 0] Fatal: Initialization failed, exiting! anyone experienced sth like that before? I tried to set manually a suitable ServerGID but to no avail. Grüße Götz

2 1

ngIRCd 21 on Oracle Solaris Studio 12.3
by Goetz Hoffart 22 Nov '13

22 Nov '13

Works, but is not correctly identified - but it identifies itself: # cc -V cc: Sun C 5.12 Linux_i386 2011/11/16 # CC=/opt/solarisstudio12.3/bin/cc ./configure ngIRCd 21 has been configured with the following options: Host: x86_64-unknown-linux-gnu Compiler: /opt/solarisstudio12.3/bin/cc Compiler flags: -g -DSYSCONFDIR='"$(sysconfdir)"' -DDOCDIR='"$(docdir)"' Libraries: -lz 'ngircd' binary: /usr/local/sbin Configuration file: /usr/local/etc Manual pages: /usr/local/share/man Documentation: /usr/local/share/doc/ngircd Syslog support: yes Enable debug code: no zlib compression: yes IRC sniffer: no Use TCP Wrappers: no Strict RFC mode: no IDENT support: no IRC+ protocol: yes IPv6 protocol: no I/O backend: epoll(), select() PAM support: no SSL support: no libiconv support: no the executable works ("runs") as expected --+ tests run successfully ("make check") --+ | ngIRCd compiles ("make") --+ | | ./configure works --+ | | | | | | | Platform Compiler ngIRCd Date Tester C M T R * --------------------------- ------------ ---------- -------- -------- - - - - - x86_64/unknown/linux-gnu unknown 21 13-11-22 goetz Y Y Y Y 1 # uname -a Linux s1.hoffart.de 2.6.32-5-amd64 #1 SMP Fri May 10 08:43:19 UTC 2013 # x86_64 GNU/Linux Grüße Götz

1 0

ngIRCd 21
by Alexander Barton 22 Nov '13

22 Nov '13

Hello ngIRCd'ers! »We proudly present … ngIRCd 21!« After two release candidates, here it is, the shiny new release: most prominent new features are our included help system documenting all supported IRC commands (try „/QUOTE HELP <command>“ in your IRC client), far better support for „server target masks“ for a lot of commands (for example try something like „/ADMIN nickname“ or „/LUSERS *.de“), the new configuration variable „IncludeDir“ that allows to split the server configuration across multiple files, and support for SSL certificate fingerprints. But there is even more! Please see the full NEWS and ChangeLog files for all changes, you can read them here: • <http://ngircd.barton.de/doc/NEWS> • <http://ngircd.barton.de/doc/ChangeLog> And even more information can be found here: • Homepage: <http://ngircd.barton.de/> (<http://ngircd.berlios.de/>) • Bug tracker: <http://ngircd.barton.de/bugzilla/> • Downloads: - FTP: <ftp://ftp.berlios.de/pub/ngircd/> - HTTP: <http://ngircd.barton.de/pub/ngircd/> Thanks to all users, bug reporters, contributors, packagers, and supporters! Regards Alex

2 3

ngIRCd 21 auf OpenBSD 3.5/x86-32
by Goetz Hoffart 17 Nov '13

17 Nov '13

the executable works ("runs") as expected --+ tests run successfully ("make check") --+ | ngIRCd compiles ("make") --+ | | ./configure works --+ | | | | | | | Platform Compiler ngIRCd Date Tester C M T R * --------------------------- ------------ ---------- -------- -------- - - - - - i386/unknown/openbsd3.5 2.95.3 21 13-11-17 goetz Y Y Y Y 3 $ uname -a OpenBSD virtobsd3.3rz.org 3.5 GENERIC#34 i386 $ sysctl -n kern.version OpenBSD 3.5 (GENERIC) #34: Mon Mar 29 12:24:55 MST 2004 deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC Grüße Götz

1 0

ngircd on Raspberry Pi Debian Wheezy
by irosaurus 26 Okt '13

26 Okt '13

Hi everybody, have it running for a long time on my Raspberry Pi Rev2 and wanted to share this info ;) the executable works ("runs") as expected --+ tests run successfully ("make check") --+ | ngIRCd compiles ("make") --+ | | ./configure works --+ | | | | | | | Platform Compiler ngIRCd Date Tester C M T R * --------------------------- ------------ ---------- -------- -------- - - - - - armv6l/unknown/linux-gnueabihf gcc 4.6.3 48698f1 13-10-26 pi Y Y Y Y 5 Thanks for your great work Alex! Cheers iro

2 1

ngircd on OS X 10.9
by Götz Hoffart 24 Okt '13

24 Okt '13

the executable works ("runs") as expected --+ tests run successfully ("make check") --+ | ngIRCd compiles ("make") --+ | | ./configure works --+ | | | | | | | Platform Compiler ngIRCd Date Tester C M T R See --------------------------- ------------ ---------- -------- ------ - - - - --- x86_64/apple/darwin13.0.0 gcc Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn) 20.3 13-10-24 gh Y Y Y Y (3) Yay. Not that I expected another result, but keep on’ hacking :-) Grüße Götz

1 0

21~rc2 platformtest on openbsd 5.3/i386
by Darren Spruell 23 Okt '13

23 Okt '13

$ ./contrib/platformtest.sh platformtest.sh: Checking ngIRCd base source directory ... platformtest.sh: Checking for GIT tree ... platformtest.sh: Checking for "./configure" script ... platformtest.sh: Running "./configure" script ... platformtest.sh: Running "make" ... platformtest.sh: Running "make check" ... portabtest.c: In function 'main': portabtest.c:43: warning: the address of 'snprintf' will always evaluate as 'true' portabtest.c:44: warning: the address of 'vsnprintf' will always evaluate as 'true' portabtest.c:45: warning: the address of 'strlcpy' will always evaluate as 'true' portabtest.c:46: warning: the address of 'strlcat' will always evaluate as 'true' the executable works ("runs") as expected --+ tests run successfully ("make check") --+ | ngIRCd compiles ("make") --+ | | ./configure works --+ | | | | | | | Platform Compiler ngIRCd Date Tester C M T R See --------------------------- ------------ ---------- -------- ------ - - - - --- i386/unknown/openbsd5.3 gcc 4.2.1 21~rc2 13-10-21 dspruell Y Y Y Y (3) I did want to ask about path changes in the configuration. Under v20 the use of './configure --sysconfdir=/etc/ngircd' set the paths for many parameters in the config to /etc/ngircd. I notice the new configuration has these defaulting to /usr/local/etc/ even with --sysconfdir set to /etc/ngircd. $ egrep '\./configure' config.log $ ./configure --sysconfdir=/etc/ngircd --with-openssl --- ngircd.conf-v20 Sat Dec 29 23:49:41 2012 +++ ngircd.conf Mon Oct 21 23:41:32 2013 - ;MotdFile = /etc/ngircd/ngircd.motd + ;MotdFile = /usr/local/etc/ngircd.motd + ;IncludeDir = /usr/local/etc/conf.d - ;CertFile = /etc/ngircd/ssl/server-cert.pem + ;CertFile = /usr/local/etc/ssl/server-cert.pem - ;DHFile = /etc/ngircd/ssl/dhparams.pem + ;DHFile = /usr/local/etc/ssl/dhparams.pem - ;KeyFile = /etc/ngircd/ssl/server-key.pem + ;KeyFile = /usr/local/etc/ssl/server-key.pem - ;KeyFile = /etc/ngircd/#chan.key + ;KeyFile = /usr/local/etc/#chan.key Shouldn't the path in the config for all these be /etc/ngircd/ with --sysconfdir set as shown? The compiled in defaults appear to be correct: $ ngircd --configtest ... Reading configuration from "/etc/ngircd/ngircd.conf" ... ... MotdFile = /etc/ngircd/ngircd.motd IncludeDir = /etc/ngircd/ngircd.conf.d -- Darren Spruell phatbuckett(a)gmail.com

2 2

ngIRCd 21~rc2
by Alexander Barton 21 Okt '13

21 Okt '13

Hello! Yesterday I prepared and uploaded the second release candidate for our upcoming release, ngIRCd 21~rc2 -- but I obviously forgot to write a proper release announcement ... sorry! So here we go: There haven't been a lot of changes since the first release candidate a few weeks ago, mostly small bug fixes and documentation updates: • Report the correct configuration file name on configuration errors, support longer configuration lines, and warn when lines are truncated. • Use arc4random() function to generate "random" numbers, when available. • platformtest.sh: Detect clang compiler, and clean up GIT source tree before building (when possible). • Update (date of) manual pages. • Update "Upgrade Information" in INSTALL file, add more systems to doc/Platforms.txt, and fix spelling in NEWS and ChangeLog files =:) • Fix remaining compiler warnings on OpenBSD. Please have a look at the NEWS and ChangeLog files for the complete list of all changes and new features since ngIRCd 20: • http://ngircd.barton.de/doc/NEWS • http://ngircd.barton.de/doc/ChangeLog And please (PLEASE!) test this release candidate, I hope to be able to create the final release very soon. A good way to check it is by using the included ./contrib/platformtest.sh shell script, which will build ngIRCd, test it, and create a nice summary line suitable for inclusion into ./doc/Platforms.txt -- and contributions are highly appreciated, but you don't need to send thousands of lines for "mainstream" systems, distributions, and CPUs like Linux on i386 or amd64 ;-) • Homepage: <http://ngircd.barton.de/> (<http://ngircd.berlios.de/>) • Bug tracker: <http://ngircd.barton.de/bugzilla/> • Downloads: - FTP: <ftp://ftp.berlios.de/pub/ngircd/> - HTTP: <http://ngircd.barton.de/pub/ngircd/> Thanks to all testers and contributors! Have fun! Alex

1 0

Invitation to connect on LinkedIn
by Damon Talbot 17 Okt '13

17 Okt '13

LinkedIn ------------ I'd like to add you to my professional network on LinkedIn. - Damon Damon Talbot Telecommunications Professional Greater Grand Rapids, Michigan Area Confirm that you know Damon Talbot: https://www.linkedin.com/e/-r4hlba-hmw665jk-4w/isd/17376217269/dTxMQL_d/?hs… -- You are receiving Invitation to Connect emails. Click to unsubscribe: http://www.linkedin.com/e/-r4hlba-hmw665jk-4w/OfeCvxcCu9XOXuAOHc3quzZkzOgmm… (c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.

1 0

ngIRCd 21~rc1
by Alexander Barton 07 Okt '13

07 Okt '13

Hi All! Last weekend I created the first release candidate for our next major feature release: ngIRCd 21~rc1. There have been more than 220 individual commits since our last "feature release" ngIRCd 20 last December, and the NEWS file lists 17 new features, including new configuration options, new commands, better help, and enhanced support for SSL -- among others: • Actually KILL clients on GLINE/KLINE. (Closes bug #156) • Add support to show all user links using the "STATS L" (uppercase) command (restricted to IRC Operators). • Implement configurable SSL cipher list selection for GnuTLS and OpenSSL using the new configuration option "CipherList". In addition, this changes the defaults to more secure values: "HIGH:!aNULL:@STRENGTH" for OpenSSL, and "SECURE128" for GnuTLS. • Show connection flag "s" (SSL) in RPL_TRACE{LINK|SERVER} messages: now you can check if a server-to-server link is SSL-encrypted or not using the IRC "TRACE" command. • Implement the new configuration option "DefaultUserModes" which lists user modes that become automatically set on new local clients right after login. Please note that only modes can be set that the client could set on itself, so you can't set "a" (away) or "o" (IRC Op), for example! User modes "i" (invisible) or "x" (cloaked) etc. are "interesting", though. (Closes bug #160) • Add support for the new METADATA "account" property, which allows services to automatically identify users after netsplits and across service restarts. • Implement a new configuration option "AllowedChannelTypes" that lists all allowed channel types (channel prefixes) for newly created channels on the local server. By default, all supported channel types are allowed. If set to the empty string, local clients can't create new channels at all, which equals the old "PredefChannelsOnly = yes" setting. This change deprecates the "PredefChannelsOnly" variable, too, but it is still supported and translated to the appropriate "AllowedChannelTypes" setting. When the old "PredefChannelsOnly" variable is processed, a warning message is logged. (Closes bug #152) • Add support for "client certificate fingerprinting". When a client passes an SSL certificate to the server, the "fingerprint" will be forwarded in the network which enables IRC services to identify the user using this certificate and not using passwords. • Implement a new configuration option "IncludeDir" in the "[Options]" section that can be used to specify a directory which can contain further configuration files and configuration file snippets matching the pattern "*.conf". These files are read in after the main server configuration file ("ngircd.conf" by default) has been read in and parsed. The default is "$SYSCONFDIR/ngircd.conf.d", so that it is possible to adjust the configuration only by placing additional files into this directory. (Closes bug #157) • Add Travis-CI configuration file (".travis.yml") to project. • ngIRCd now accepts user names including "@" characters, saves the unmodified name for authentication but stores only the part in front of the "@" character as "IRC user name". And the latter is how ircd2.11, Bahamut, and irc-seven behave as well. (Closes bug #155) • Lots of IRC "information functions" like ADMIN, INFO, ... now accept server masks and names of connected users (in addition to server names) for specifying the target server of the command. (Closes bug #153) • Implement a new configuration option "IdleTimeout" in the "[Limits]" section of the configuration file which can be used to set a timeout in seconds after which the whole daemon will shutdown when no more connections are left active after handling at least one client. The default is 0, "never". This can be useful for testing or when ngIRCd is started using "socket activation" with systemd(8), for example. • Implement support for systemd(8) "socket activation". • Enable WHOIS to display information about IRC Services using the new numeric 310(RPL_WHOISSERVICE) This numeric is used for this purpose by InspIRCd, for example -- but as usual, other numerics are in use, too, like 613 in UltimateIRCd ... Please note that neither the Operator (+o) not the "bot status" (+B) of an IRC service id displayed in the output. • Update systemd(8) example configuration files in ./contrib/ directory: the "ngircd.service" file now uses the "forking" service type which enhances the log messages shown by "systemctl status ngircd.service", and the new "ngircd.socket" file configures a systemd socket that configures a socket for ngIRCd and launches the daemon on demand. • Enhance help system and the HELP command: now a "help text file" can be set using the new configuration option "HelpFile" ("global" section), which is read in and parsed on server startup and configuration reload, and then is used to output individual help texts to specific topics. Please see the file ./doc/Commands.txt for details. Please test this release candidate and report all problems, errors, and regressions you encounter! Best is to file bugs and feature requests here: ngIRCd Bug Tracker: <http://ngircd.barton.de/bugzilla/> You can find more information on our homepage at <http://ngircd.barton.de/> and its mirror <http://ngircd.berlios.de/>. The primary download locations are: • <ftp://ftp.berlios.de/pub/ngircd/> • <http://ngircd.barton.de/pub/ngircd/> Thanks to all people contributing code, ideas, and bug reports! Most probably there will be a second release candidate, and afterwards a new stable release. Have fun! Alex

1 0

TLS and authentication patches
by Matt Pepe 19 Sep '13

19 Sep '13

Hello, On a related note, I have patches for the GNUTLS side of things that allows for client certificate support (including CRLs). I also have ngircd connected to a an OTP solution, which obviously causes issues with the numerous client re-connects. I ended up implementing an authentication cache to solve that problem as well. Any interest in both/either? - Matt

2 1

Re: [ngIRCd-ML] Support fir OpenSSL CipherList
by lists＠packetmail.net 07 Sep '13

07 Sep '13

On 09/07/2013 05:00 AM, ngircd-ml-request(a)arthur.barton.de wrote: > Hi, > > I attached a fix for the last patch. > - important: verifying CipherLists are applied successfully > - if SSL initialization failes, daemon should exit and not run without SSL > > Q: Is it welcome to provide patches on the ML? I certainly appreciate you taking the time to write the patch, correct it, and share it again. This is a feature that I am very happy to see implemented and I thank you for taking the time to do this and share with the community. It seems I still have the same issue with the latest patch on ngircd-20.3 -- # patch -p0 < ../ngircd_ssl_cipherlist.patch patching file ./doc/sample-ngircd.conf.tmpl Hunk #1 succeeded at 237 (offset -23 lines). patching file ./src/ngircd/conf.c Hunk #1 succeeded at 106 (offset -11 lines). Hunk #2 succeeded at 431 (offset -15 lines). Hunk #3 succeeded at 1842 with fuzz 2 (offset -32 lines). patching file ./src/ngircd/conf.h patching file ./src/ngircd/conn-ssl.c Hunk #1 succeeded at 275 with fuzz 1 (offset -28 lines). patching file ./src/ngircd/ngircd.c Hunk #1 succeeded at 671 (offset -2 lines). # Log Sep 7 11:15:47 localhost ngircd[27467]: /usr/local/etc/ngircd.conf, line 166 (section "SSL"): Unknown variable "CipherList"! Sep 7 11:15:47 localhost ngircd[27467]: ngIRCd 20.3-IPv6+IRCPLUS+SSL+SYSLOG+ZLIB-i686/pc/linux-gnu started. Sep 7 11:15:47 localhost ngircd[27467]: Using configuration file "/usr/local/etc/ngircd.conf" ... Sep 7 11:15:47 localhost ngircd[27467]: Configuration option "DHFile" not set! Sep 7 11:15:47 localhost ngircd[27467]: SSL using default CipherList Sep 7 11:15:47 localhost ngircd[27467]: OpenSSL 1.0.1 14 Mar 2012 initialized. # grep -B 10 "CipherList" /usr/local/etc/ngircd.conf # password to decrypt SSLKeyFile (OpenSSL only) ;KeyFilePassword = secret # SSL Server Key Certificate CertFile = /etc/apache2/ssl/ssl.crt # Diffie-Hellman parameters ;DHFile = /usr/local/etc/ngircd/ssl/dhparams.pem # SSL_CipherList.patch, Sep 06 2013 CipherList = ALL:!aNULL:!ADH:!eNULL:!LOW:!EXP:RC4+RSA:+HIGH:+MEDIUM Thanks, Nathan Fowler

3 2

Re: [ngIRCd-ML] Support fir OpenSSL CipherList
by lists＠packetmail.net 06 Sep '13

06 Sep '13

On 09/06/2013 05:00 AM, ngircd-ml-request(a)arthur.barton.de wrote: > The patch attached is now in proper order. Question -- I'm very happy to see this patch but it doesn't appear to work against ngircd 20.3 -- am I doing something incorrectly? Apologies if I'm doing something stupid/obvious, I've reviewed the patch/code and it looks sound, including conf.c but based on the log message it looks like it's an issue with conf.c # gpg --verify ngircd-20.3.tar.gz.sig ngircd-20.3.tar.gz gpg: Signature made Fri 23 Aug 2013 03:25:37 PM CDT using RSA key ID EAA15A24 gpg: Good signature from "Alexander Barton <alex(a)barton.de>" gpg: aka "Alexander Barton <alex(a)barton-it.de>" gpg: aka "Alexander Barton <alex(a)arthur.ath.cx>" gpg: aka "[jpeg image of size 1488]" gpg: aka "[jpeg image of size 1718]" gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: F5B9 F52E D909 20D2 5203 76A2 C24A 0F63 7E36 4856 Subkey fingerprint: 47EC B2F6 D427 3737 30E9 0113 8A45 9AD2 EAA1 5A24 # patch -p0 < SSL_Ciphers.patch patching file ./doc/sample-ngircd.conf.tmpl Hunk #1 succeeded at 237 (offset -23 lines). patching file ./src/ngircd/conf.c Hunk #1 succeeded at 106 (offset -11 lines). Hunk #2 succeeded at 431 (offset -15 lines). Hunk #3 succeeded at 1842 with fuzz 2 (offset -32 lines). patching file ./src/ngircd/conf.h patching file ./src/ngircd/conn-ssl.c Hunk #1 succeeded at 275 with fuzz 1 (offset -28 lines). # ./configure --enable-ipv6 --with-openssl CFLAGS='-Wall -D_FORTIFY_SOURCE=2 -O2 -fPIE -pie -fstack-protector' checking build system type... i686-pc-linux-gnu .... ngIRCd 20.3 has been configured with the following options: Host: i686-pc-linux-gnu Compiler: gcc -std=gnu99 Compiler flags: -Wall -D_FORTIFY_SOURCE=2 -O2 -fPIE -pie -fstack-protector -pipe -W -Wall -Wpointer-arith -Wstrict-prototypes -fstack-protector -DSYSCONFDIR='"$(sysconfdir)"' Libraries: -lssl -lcrypto -lz 'ngircd' binary: /usr/local/sbin Configuration file: /usr/local/etc Manual pages: /usr/local/share/man Documentation: /usr/local/share/doc/ngircd Syslog support: yes Enable debug code: no zlib compression: yes IRC sniffer: no Use TCP Wrappers: no Strict RFC mode: no IDENT support: no IRC+ protocol: yes IPv6 protocol: yes I/O backend: "epoll(), select()" PAM support: no SSL support: openssl libiconv support: no # grep CipherList /etc/ngircd.conf -B 12 # SSL Server Key KeyFile = /etc/apache2/ssl/ssl.key # password to decrypt SSLKeyFile (OpenSSL only) ;KeyFilePassword = secret # SSL Server Key Certificate CertFile = /etc/apache2/ssl/ssl.crt # Diffie-Hellman parameters ;DHFile = /usr/local/etc/ngircd/ssl/dhparams.pem # SSL_CipherList.patch, Sep 06 2013 CipherList = ALL:!aNULL:!ADH:!eNULL:!LOW:!EXP:RC4+RSA:+HIGH:+MEDIUM # grep/tail log Sep 6 15:39:24 localhost ngircd[4153]: /usr/local/etc/ngircd.conf, line 166 (section "SSL"): Unknown variable "CipherList"! Sep 6 15:39:24 localhost ngircd[4153]: ngIRCd 20.3-IPv6+IRCPLUS+SSL+SYSLOG+ZLIB-i686/pc/linux-gnu started. Sep 6 15:39:24 localhost ngircd[4153]: Using configuration file "/usr/local/etc/ngircd.conf" ... Sep 6 15:39:24 localhost ngircd[4153]: Configuration option "DHFile" not set! Sep 6 15:39:24 localhost ngircd[4153]: SSL using default CipherList Sep 6 15:39:24 localhost ngircd[4153]: OpenSSL 1.0.1 14 Mar 2012 initialized. # diff -u conf.c conf.c.orig --- conf.c 2013-09-06 15:36:00.000000000 -0500 +++ conf.c.orig 2013-08-23 14:43:02.000000000 -0500 @@ -106,9 +106,6 @@ array_free_wipe(&Conf_SSLOptions.KeyFilePassword); array_free(&Conf_SSLOptions.ListenPorts); - - free(Conf_SSLOptions.CipherList); - Conf_SSLOptions.CipherList = NULL; } /** @@ -431,8 +428,6 @@ array_free_wipe(&Conf_SSLOptions.KeyFilePassword); printf(" Ports = "); ports_puts(&Conf_SSLOptions.ListenPorts); - printf(" CipherList = %s\n", Conf_SSLOptions.CipherList - ? Conf_SSLOptions.CipherList : ""); puts(""); #endif @@ -1842,11 +1837,6 @@ Config_Error_TooLong(Line, Var); return; } - if (strcasecmp(Var, "CipherList") == 0) { - assert(Conf_SSLOptions.CipherList == NULL); - Conf_SSLOptions.CipherList = strdup_warn(Arg); - return; - } Config_Error_Section(Line, Var, "Server"); } Thanks, Nathan Fowler

1 0

Support fir OpenSSL CipherList
by Bastian 06 Sep '13

06 Sep '13

Hi all, find attached a patch which enables a configuration option CipherList. This can be used to select/deselect ciphers used for tls/ssl connections. This became significant to me, because my network ops detected my ngIRCd would allow low and already known to be broken ciphers. Sorry, this is only for OpenSSL, gnutls is not included. Please also mind, that this was the first time for me looking into ngIRCd code. I hope I got all the meanings about config reading and checking properly. Hope this helps. Bastian

2 3

Re: [ngIRCd-ML] ngIRCd-ML Digest, Vol 95, Issue 1
by lists＠packetmail.net 02 Sep '13

02 Sep '13

On 09/02/2013 05:00 AM, ngircd-ml-request(a)arthur.barton.de wrote: > I am using OpenSSL (1.*) with Ngircd to enforce SSL connections. > Is there a possibility that I can enforce certain ciphers or disable > certain weak ciphers? Perhaps use the 'stunnel' method for serving ngircd over SSL and disable weak ciphers through stunnel's configuration, see http://ngircd.barton.de/doc/SSL.txt options = NO_SSLv2 ciphers = ALL:-ADH:+HIGH:+MEDIUM:-LOW:-SSLv2:-EXP If you're using RHEL-derived distribution, perhaps enable FIPS mode to disable weak ciphers system-wide see section 7.2.1 in the below URL: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux… Cheers, Nathan

2 1

question about strong ciphers
by Michiel van Es 01 Sep '13

01 Sep '13

Hello, I am using OpenSSL (1.*) with Ngircd to enforce SSL connections. Is there a possibility that I can enforce certain ciphers or disable certain weak ciphers? The default config allow 56 bits ciphers: SSLv3:RC4-MD5 - ENABLED - STRONG 128 bits SSLv3:DES-CBC3-SHA - ENABLED - STRONG 168 bits SSLv3:CAMELLIA128-SHA - ENABLED - STRONG 128 bits SSLv3:RC4-SHA - ENABLED - STRONG 128 bits SSLv3:SEED-SHA - ENABLED - STRONG 128 bits SSLv3:CAMELLIA256-SHA - ENABLED - STRONG 256 bits ** SSLv3:DES-CBC-SHA - ENABLED - WEAK 56 bits ** SSLv3:AES128-SHA - ENABLED - STRONG 128 bits SSLv3:AES256-SHA - ENABLED - STRONG 256 bits Error 20: unable to get local issuer certificate TLSv1:RC4-MD5 - ENABLED - STRONG 128 bits TLSv1:DES-CBC3-SHA - ENABLED - STRONG 168 bits TLSv1:CAMELLIA128-SHA - ENABLED - STRONG 128 bits TLSv1:RC4-SHA - ENABLED - STRONG 128 bits TLSv1:SEED-SHA - ENABLED - STRONG 128 bits TLSv1:CAMELLIA256-SHA - ENABLED - STRONG 256 bits ** TLSv1:DES-CBC-SHA - ENABLED - WEAK 56 bits ** TLSv1:AES128-SHA - ENABLED - STRONG 128 bits TLSv1:AES256-SHA - ENABLED - STRONG 256 bits Regards, Michiel

1 0

question about Ngircd and PAM setup
by Michiel van Es 26 Aug '13

26 Aug '13

Hello, I am using the latest Ngircd on an Ubuntu 64 bit vps. I am trying to setup Ngircd with PAM. I've read the documentation for PAM here: http://ngircd.barton.de/doc/PAM.txt but I am having a few questions and issues: - I've set up /etc/pam.d/ngircd as follows: #%PAM-1.0 auth required pam_userdb.so db=/etc/ngircd/ngircd-vuser.db account required pam_userdb.so db=/etc/ngircd/ngircd-vuser.db session required pam_loginuid.so Ngircd is running under the user irc but I am not sure if the user has permissions to use this pam file as specified in the PAM.txt file? - I see the following message in /var/log/syslog: ==> /var/log/auth.log <== Aug 23 10:41:12 mail ngircd[8733]: PAM _pam_init_handlers: could not open /etc/pam.conf Aug 23 10:41:12 mail ngircd[8733]: PAM pam_start: failed to initialize handlers ==> /var/log/syslog <== Aug 23 10:41:12 mail ngircd[8733]: PAM: Failed to create authenticator! (26) Why is it looking in the empty file /etc/pam.conf and not /etc/pam.d/ngircd ? My relevant config sniplet: # Use PAM if ngIRCd has been compiled with support for it. PAM = yes PAMIsOptional = no Can I force Ngircd to look for /etc/pam.d/ngricd (world readable) ? I am using this berkley vuser setup the same way with vsftpd. Regards, Michiel

2 7

ngIRCd 20.3
by Alexander Barton 24 Aug '13

24 Aug '13

Hello! A severe bug in ngIRCd 18 up to and including 20.2 has been discovered which will crash the daemon (denial of service) and can happen when the daemon fails to send the optional "notice auth" message to new clients connecting to the server (CVE-2013-5580). So here it is, our next release: ngIRCd 20.3. Please note that only setups having the configuration option "NoticeAuth" enabled are affected, which is not the default. The only change in ngIRCd 20.3 is the fix for the above bug, all installations should upgrade. But please stay tuned, ngIRCd 21 including new features like SSL fingerprints, and include directory for configuration files, better systemd(8) support etc. is the the works, too, and I hope that we can soon release a beta version for testing. I'll keep you informed! Changes in ngIRCd 20.3: • Security: Fix a denial of service bug (server crash) which could happen when the configuration option "NoticeAuth" is enabled (which is NOT the default) and ngIRCd failed to send the "notice auth" messages to new clients connecting to the server (CVE-2013-5580). More information can be found on the homepage <http://ngircd.barton.de/> and its mirror <http://ngircd.berlios.de/>. The primary download locations are: • <ftp://ftp.berlios.de/pub/ngircd/> • <http://ngircd.barton.de/pub/ngircd/> Regards Alex

1 2

Reporting 1.2K crashes
by Götz Hoffart 28 Jun '13

28 Jun '13

http://lists.debian.org/debian-devel/2013/06/msg00720.html ngircd doesn’t seem to be on the list, congrats :-) Grüße Götz

1 0

listen on port 443
by Xenophod 07 Jun '13

07 Jun '13

How can I get ngircd to listen on port 443? I don't need SSL, I just need a port that won't ever be blocked by ISPs/Wifi-hotspots/work networks I tried adding 443 to the listening ports, but I get a Permission denied message. Jun 6 11:18:08 ngircd[4605]: Can't bind socket to address 0.0.0.0:443 - Permission denied Jun 6 11:18:08 ngircd[4605]: Now listening on [0.0.0.0]:6666 (socket 8). Jun 6 11:18:08 ngircd[4605]: Now listening on [0.0.0.0]:6667 (socket 9). Jun 6 11:18:08 ngircd[4605]: Now listening on [0.0.0.0]:6668 (socket 10). Jun 6 11:18:08 ngircd[4605]: Now listening on [0.0.0.0]:6669 (socket 11). Nothing else is using port 443 on my machine either. The command below returns nothing. sudo netstat -lntup | grep 443 Can this be done with ngircd? Thanks

6 6

gource - software version control visualization - Google Project Hosting
by Götz Hoffart 27 Apr '13

27 Apr '13

http://code.google.com/p/gource/ Maybe for the ngircd-source-tree? Does anyone know some fancy CC music? Regards Götz

1 0

Set Topic
by Michiel van Es 18 Apr '13

18 Apr '13

Hello, I know how you can set the PredefChannelsOnly = yes to ensure only those channels are created and available but can I do the same with the Topic? Yes I can set the Topic option in the channel but people are still able to change the Topic to something else. I also want to disable that option so that people can only chat and not change the topic of the room. Any help is appreciated. Michiel

1 0

question about ngircd
by Michiel van Es 29 Mär '13

29 Mär '13

Hello, I am using the latest ngircd on a raspberry pi (armhf) with Debian Wheezy. I was wondering if I can restrict the creation of rooms/channels in Ngircd? I've created 2 rooms/channels which I want to be the only one available and that other people can only use those 2 rooms and can not create their own. Is that possible? Thanks for any help. Michiel

2 2

fcntl.h: present but cannot be compiled
by Aaron Walker 20 Mär '13

20 Mär '13

Hello, I'm trying to configure/build ngircd on AIX 6.1, and got the following error. Reporting it because it asked me nicely. root@r59s2h4:/twiki/ngircd/ngircd-20.2 # ./configure checking build system type... powerpc-ibm-aix6.1.0.0 checking host system type... powerpc-ibm-aix6.1.0.0 checking for a BSD-compatible install... ./install-sh -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... ./install-sh -c -d checking for gawk... no checking for mawk... no checking for nawk... nawk checking whether make sets $(MAKE)... yes checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for gcc option to accept ISO C99... -std=gnu99 checking for gcc -std=gnu99 option to accept ISO Standard C... (cached) -std=gnu99 checking for gawk... (cached) nawk checking whether ln -s works... yes checking whether make sets $(MAKE)... (cached) yes checking for ranlib... ranlib checking for an ANSI C-conforming const... yes checking for inline... inline checking for function prototypes... yes checking how to run the C preprocessor... gcc -std=gnu99 -E checking for grep that handles long lines and -e... /opt/freeware/bin/grep checking for egrep... /opt/freeware/bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... no checking for string.h... (cached) yes checking whether gcc -std=gnu99 accepts -fstack-protector... no checking for ANSI C header files... (cached) yes checking for sys/wait.h that is POSIX.1 compatible... yes checking whether time.h and sys/time.h may both be included... yes checking fcntl.h usability... no checking fcntl.h presence... yes configure: WARNING: fcntl.h: present but cannot be compiled configure: WARNING: fcntl.h: check for missing prerequisite headers? configure: WARNING: fcntl.h: see the Autoconf documentation configure: WARNING: fcntl.h: section "Present But Cannot Be Compiled" configure: WARNING: fcntl.h: proceeding with the compiler's result configure: WARNING: ## ----------------------------------------- ## configure: WARNING: ## Report this to ngircd-ml(a)ngircd.barton.de ## configure: WARNING: ## ----------------------------------------- ## checking for fcntl.h... no configure: error: required C header missing! Merci, Aaron

1 0

A little pam help?
by Doug 06 Mär '13

06 Mär '13

Hi, I was wondering if someone could shed some light on how to use PAM with ngircd? I've set PAM = yes, and PAMIsOptional = no, but I'm kind of fuzzy on how this is supposed to work. The client connects with a nick and username, (in this case my username for both, douglasl). The server rejects the connection, and logs: [18632:6 5] Accepted connection 7 from 127.0.0.1:59814 on socket 6. [18906:3 5] PAM: Error on "douglasl" (douglasl!~douglasl@localhost): Authentication failure [18632:3 5] User "douglasl!~douglasl@localhost" rejected (connection 7): Bad password! [18632:6 5] Shutting down connection 7 (Bad password) with localhost:59814 ... [18632:5 5] Client "douglasl" unregistered (connection 7): Bad password [18632:6 5] Connection 7 with localhost:59814 closed (in: 0.1k, out: 0.0k). Riiight. I'm pretty sure I've got pam working, because I can use pamtester well enough: ~/ngircd/pamtester-0.1.2/src# ./pamtester login douglasl authenticate Password: pamtester: successfully authenticated So, the question is, how the irc client supposed to be supplying the password for the user? The raw commands to the server after connect are PASS / NICK / USER, which sound like they should be all I need. :/ Any ideas? ~ Doug.

2 2

ngIRCd 20.2
by Alexander Barton 18 Feb '13

18 Feb '13

Hello ngIRCd'ers! Sebastian Köhler discovered a severe bug in ngIRCd 20 and 20.1 which can be exploited by arbitrary users to crash the daemon and to lead to denial of service. So here is the next "bug fix only" release for the ngIRCd 20 series: release 20.2. Please note that all releases before 20 are NOT affected by the bug mentioned above. But in the end, all installations should upgrade, ngIRCd 20.2 is the most complete release we have so far, and there should be no reasons to stay with old versions -- besides distributions not having newer releases ... Besides the fix for the DoS mentioned above, ngIRCd 20.2 contains other fixes. The complete ChangeLog lists the following changes: • Security: Fix a denial of service bug in the function handling KICK commands that could be used by arbitrary users to to crash the daemon. • WHO command: Use the currently "displayed hostname" (which can be cloaked!) for hostname matching, not the real one. In other words: don't display all the cloaked users on a specific real hostname! • configure: The header file "netinet/in_systm.h" already is optional in ngIRCd, so don't require it in the configure script. Now ngIRCd can be built on Minix 3 again :-) • Return better "Connection not registered as server link" errors: Now ngIRCd returns a more specific error message for numeric ERR_NOTREGISTERED(451) when a regular user tries to use a command that isn't allowed for users but for servers. • Don't report ERR_NEEDMOREPARAMS(461) when a MDOE command with more modes than nicknames is handled, as well as for channel limit and key changes without specifying the limit or key parameters. This is how a lot (all?) other IRC servers behave, including ircd2.11, InspIRCd, and ircd-seven. And because of clients (tested with Textual and mIRC) sending bogus MODE commands like "MODE -ooo nick", end-users got the expected result as well as correct but misleading error messages ... • Correctly detect when SSL subsystem must be initialized and take outgoing connections (server links!) into account, too. • autogen.sh: Enforce serial test harness on GNU automake >=1.13. The new parallel test harness which is enabled by default starting with automake 1.13 isn't compatible with our test suite. And don't use "egrep -o", insetead use "sed", because it isn't portable and not available on OpenBSD, for example. More information can be found on the homepage <http://ngircd.barton.de/> and its mirror <http://ngircd.berlios.de/>. The primary download locations are: • <ftp://ftp.berlios.de/pub/ngircd/> • <http://ngircd.barton.de/pub/ngircd/> Regards Alex

2 2

Don't disconnect on overlong lines?
by Brett Smith 15 Feb '13

15 Feb '13

Hi folks, Over the past month or so I've received complaints from multiple users, using different clients, about the fact that ngIRCd disconnects them when they send lines longer than the RFC permits. It seems like most ircds simply truncate the line, and this behavior is commonly expected. I think this is something that clients really ought to be more careful about, but unfortunately there are still too many that aren't, and it feels bad to me to punish the user with a disconnect for not manually counting their bytes. Would all consider truncating the line, or some other less disruptive way to handle this case? Maybe the disconnect behavior could stay when STRICT_RFC is defined. Thanks, -- Brett Smith

1 0

Print recent chat messages on user joining a channel
by Xiaohao.M 02 Feb '13

02 Feb '13

Hi all, Does anyone know how to let ngircd prints the latest 10 or 20 history messages on a user joining a channel? For the 'recent-offline-message-push', is that working with server side or just some bot could do? *Thank you,* *Xiaohao (Kevin)*

2 1

FYI: Status of ngircd in Debian
by Christoph Biedl 15 Jan '13

15 Jan '13

Hi, just wanted to let you know about two recent uploads: * ngirc-20.1 is now available in the "experimental" archive. Don't worry about that name, this has just a Debian-internal reason: To keep "unstable" available just in case the version 19.2-2 there might need an update for the upcoming wheezy release. Once this has happened, hopefully in the next four or six weeks, uploads will enter "unstable" as usual. * A backport of 19.2 for squeeze aka "stable", full version is '19.2-2~bpo60+1', will become available through debian-backports soon, probably during the next hours. For the (almost-)complete list of available versions of ngircd in Debian, see <http://packages.debian.org/search?keywords=ngircd>. The backport is still missing, this too should change within the next hours. Cheers, Christoph, with the ngircd Debian maintainer hat on

1 1

Colloquy 2.3 mishandles &channel messages with ngIRCd 20.1
by Brett Smith 07 Jan '13

07 Jan '13

Hi again, I know I have the SSL thread open, and I'll get to that in a bit, but this issue is even weirder (and unfortunately harder to work around). After our upgrade to ngIRCd 20.1, users using Colloquy 2.3 basically cannot use server-local &channels. The client renders any public messages sent to those channels as private messages from the sender. In other words, messages that should show up in the &channel pane end up in a private query pane instead. We haven't received any similar reports from other clients, and even Colloquy 2.4 is reported to work correctly, so this seems like a client-specific bug. But this all worked fine in ngIRCd 19.2, so I'm wondering if anyone has any ideas about what might have changed server-side that could trigger this? Thanks in advance, -- Brett Smith

2 2

ngIRCd 20.1 can't make SSL server connections with GnuTLS
by Brett Smith 07 Jan '13

07 Jan '13

Hi everyone, I deployed ngIRCd 20.1 on our server yesterday and ran into a hiccup. I built ngIRCd with these flags: ./configure --enable-ipv6 --with-gnutls --with-pam We're running two servers, and the second makes a server connection to the first with SSLConnect=yes. This all worked fine in 19.2, but in 20.1 the connection doesn't take. It looks like ngIRCd fails to initialize GnuTLS correctly in this case. Here's the logs on the second server, the one making the connection—this all happens in one second: ngircd[27581]: Preparing to establish a new server link for "hostname" ... ngircd[27581]: Establishing connection for "hostname" to "192.168.1.1:6697" (192.168.1.1), socket 14 ... ngircd[27581]: Libgcrypt warning: missing initialization - please fix the application ngircd[27581]: gnutls_handshake: Insufficient credentials for that request. ngircd[27581]: SSL connection on socket 14 failed! ngircd[27581]: Shutting down connection 14 (Can't connect!) with 192.168.1.1:6697 ... ngircd[27581]: Client unregistered (connection 14): Can't connect! ngircd[27581]: Connection 14 with 192.168.1.1:6697 closed (in: 0.0k, out: 0.0k). And in case it helps, on the server receiving the connection: ngircd[27517]: Accepted connection 27 from 192.168.1.2:54547 on socket 9. ngircd[27517]: gnutls_handshake: A TLS packet with unexpected length was received. ngircd[27517]: Shutting down connection 27 (SSL accept error, closing socket) with 192.168.1.2:54547 ... ngircd[27517]: Client unregistered (connection 27): SSL accept error, closing socket ngircd[27517]: Connection 27 with 192.168.1.2:54547 closed (in: 0.0k, out: 0.0k). Best regards, -- Brett Smith

3 5

ngIRCd 20.1
by Alexander Barton 02 Jan '13

02 Jan '13

Hello all, and happy new year! About two and a half week ago, ngIRCd 20 has been released. And today, I packaged the first bug fix release, ngIRCd 20.1: Release 20 included an very ugly bug which can be triggered when the configuration option "OperCanUseMode" is active and an IRC Operator tries to enforce modes on an user in a channel where the IRC Op itself isn't a member of: ngIRCd most probably will crash (and display an assertion, when compiled with debug code enabled) ... This is a severe bug, but can't be triggered by regular users. So even if you have "OperCanUseMode" enabled, but never use this functionality as IRC Operator, don't worry too much. And don't worry at all if "OperCanUseMode" is disabled in your setup, which is the default. But long story short, everybody should upgrade to ngIRCd 20.1 ;-) In addition to this bug fix, there have been a few code cleanups and fixes for the build system, for example when building on Cygwin. Full ChangeLog: • Allow ERROR command on server and service links only, ignore them and add a penalty time on all other link types. • Enforced mode setting by IRC Operators: Only check the channel user modes of the initiator if he is joined to the channel and not an IRC operator enforcing modes (which requires the configuration option "OperCanUseMode" to be enabled), because trying to check channel user modes of a non-member results in an assertion when running with debug code or could crash the daemon otherwise. This closes bug #147, thanks to James Kirwill <james.kirwill(a)bk.ru> for tracking this down! • Fix build system to cope with spaces in path names. • Code cleanups, mostly to fix build warnings on Cygwin. More information can be found on the homepage <http://ngircd.barton.de/> and its mirror <http://ngircd.berlios.de/>. The primary download locations are: • <ftp://ftp.berlios.de/pub/ngircd/> • <http://ngircd.barton.de/pub/ngircd/> And as always (hey I love cut, copy & paste!): please report any bugs, problems, and regressions to this mailing list or directly using the bug tracker. Or connect to the "official" IRC channel #ngircd on irc.barton.de: <irc://irc.barton.de/ngircd> – thanks! Regards Alex

1 0

Atheme services and XOP
by David Woodfall 30 Dez '12

30 Dez '12

I seem to be having problems with certain modules in Atheme, which are connected to XOP. Is there anything I need to set in the ngircd.conf to turn on XOP? [28/12/2012 17:58:48] atheme 7.0.5 is starting up... [28/12/2012 17:58:48] Module chanserv/owner requires owner support, refusing to load. [28/12/2012 17:58:48] module_load(): module /usr/modules/chanserv/owner init failed [28/12/2012 17:58:48] Module chanserv/protect requires protect support, refusing to load. [28/12/2012 17:58:48] module_load(): module /usr/modules/chanserv/protect init failed [28/12/2012 17:58:48] Module chanserv/quiet requires a ban-like mode +q, refusing to load. [28/12/2012 17:58:48] module_load(): module /usr/modules/chanserv/quiet init failed [28/12/2012 17:58:48] module_load(): module /usr/modules/groupserv/main is already loaded [at 0x15dd3e0] [28/12/2012 17:58:48] opensex: data format version is 11. [28/12/2012 17:58:48] groupserv: opensex data schema version is 4. [28/12/2012 17:58:48] pid 10970 [28/12/2012 17:58:48] running in background mode from /usr As you can see from the output, it Atheme thinks that ngircd doesn't support owner, protect or quiet, which according to the changelog was added to ngircd around 20rc1 -- Studioware http://www.studioware.org

2 1

ngircd 20 auf Pogoplug Pro: works
by Götz Hoffart 26 Dez '12

26 Dez '12

Hi, ngircd 20 builds fine on a Pogoplug Pro (ARM-based mini computer) with ArchLinuxARM (rolling release of today). the executable works ("runs") as expected --+ tests run successfully ("make check") --+ | ngIRCd compiles ("make") --+ | | ./configure works --+ | | | | | | | Platform HW OS Compiler ngIRCd Date C M T R See --------------------------- --- ------ ---------- ------ -------- - - - - --- armv6l/unkn./linux-gnueabi PPP ArchLA gcc4.7.2 20 12-12-25 Y Y Y Y (5) armv6l/unkn./linux-gnueabi RBP DSquee gcc4.4.5 19.1 12-06-04 Y Y Y Y (5) armv7l/unkn./linux-gnueabi CBX Ubuntu gcc4.4.3 19.1 12-04-29 Y Y Y Y (5) hppa2.0w-hp-hpux11.11 J67 HPUX11 gcc4.2.3 14.1 09-07-22 Y Y Y Y i386/pc/solaris2.11 VMF Nexent gcc4.2.3 19.1 12-05-29 Y Y Y Y (4) i386/unknown/netbsdelf1.6.2 386 NetBSD gcc2.95.3 18 11-07-10 Y Y Y Y i386/unknown/freebsd4.1.1 VMF FrBSD4 gcc2.95.2 0.8.3 12-07-07 Y Y Y Y i386/unknown/freebsd4.1.1 VMF FrBSD4 gcc2.95.2 19.2 12-07-07 Y N N N (3) i386/unknown/freebsd4.1.1 VMF FrBSD4 gcc2.95.2 19.2 12-09-04 Y Y Y Y (4) i686/pc/linux-gnu VMF Lin1.2 gcc2.7.2 19.1 12-05-30 Y Y Y Y (1) m68k/hp/hp-ux9.10 400 HPUX9 Orig.HPUX 0.7.x 03-04-30 Y Y Y Y mipsel/unknown/linux-gnu CQu DEtch gcc4.1.2 18 11-07-05 Y Y N Y (1) mipsel/unknown/linux-gnu CQu DLenny gcc4.4.5 18 11-07-30 Y Y Y Y (1) powerpc/apple/darwin7.9.0 iB3 MacOSX gcc3.3 19.1 12-05-22 Y Y Y Y (3) powerpc/apple/darwin8.11.0 PM5 MacOSX gcc4.0.1 18 11-07-02 Y Y Y Y (3) x86_64/apple/darwin12.0.0 MBA OSX108 gcc4.2.1 19.2 12-07-26 Y Y Y Y (3) x86_64/unknown/linux-gnu VMF OrcLin gcc4.4.6 20~rc2 12-12-08 Y Y Y Y (1) HW Computer Type CPU/MHz RAM ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ PPP = Pogoplug Pro ARM v6l, Dual-Core 128 RBP = Raspberry Pi ARM1176JZF-S/700 224 CBX = Solid-Run CuBox Marv. Armada 510/800 768 J67 = HP 9000 J6750 PA-RISC 8700+/2x875 16384 VMF = vmWare Fusion - 64 386 = Intel i80386 Intel i80386/25 32 400 = HP 400t (A1630A) Motorola 68030/50 40 CQu = Cobalt Qube2 RM5231 256 iB3 = Apple iBook G3 IBM PowerPC 750fx/800 640 PM5 = Apple PowerMac G5 IBM PowerPC 970FX/1800 4096 MBA = MacBook Air 11" 2011 Intel Core i7-2677M/1800 4096 OS ~~~ DEtch = Debian Etch 4.0 DLenny = Debian Lenny 5.0 DSquee = Debian Squeeze 6.0 Lin1.2 = Linux Kernel 1.2.13 FrBSD4 = FreeBSD 4.1.1 i386 OrcLin = Oracle Enterprise Linux, 64 Bit, Kernel 2.6.39-200.24.1.el6uek.x86_64 <https://s1.hoffart.de/ngircd-platforms.txt> Regards Götz

1 0

ngircd-19.2 to ngircd-20 upgrade produces "Bad server password" for all connecting clients
by lists＠packetmail.net 19 Dez '12

19 Dez '12

Hello, After updating to ngircd-20 from ngircd-19.2 with the same build options, all connecting clients are rejected with "Bad server password". The configuration file remained unchanged between the ngircd-20 upgrade. Am I missing something obvious? The server password is made of [0-9A-Za-z\x5e]{22} ngircd-20 was compiled with the same flags as ngircd-19.2: ./configure --enable-ipv6 --with-openssl CFLAGS="-Wall -D_FORTIFY_SOURCE=2 -O2 -fPIE -pie -fstack-protector" Syslog support: yes Enable debug code: no zlib compression: yes IRC sniffer: no Use TCP Wrappers: no Strict RFC mode: no IDENT support: no IRC+ protocol: yes IPv6 protocol: yes I/O backend: "epoll(), select()" PAM support: no SSL support: openssl libiconv support: no No errors or oddities are reported in /var/log/syslog and the start-up looks to be normal. Revering to 19.2 restores connectivity despite the "password too long" warning. Dec 19 09:00:20 localhost ngircd[1906]: /usr/local/etc/ngircd.conf, line 33: Value of "Password" too long! Dec 19 09:00:20 localhost ngircd[1906]: ngIRCd 20-IPv6+IRCPLUS+SSL+SYSLOG+ZLIB-i686/pc/linux-gnu started. Dec 19 09:00:20 localhost ngircd[1906]: Using configuration file "/usr/local/etc/ngircd.conf" ... Dec 19 09:00:20 localhost ngircd[1906]: Configuration option "DHFile" not set! Dec 19 09:00:20 localhost ngircd[1906]: OpenSSL 1.0.1 14 Mar 2012 initialized. Dec 19 09:00:20 localhost ngircd[1906]: Changed root and working directory to "/var/chroot". Dec 19 09:00:20 localhost ngircd[1907]: Running as user unknown(65534), group unknown(65534), with PID 1907. Dec 19 09:00:20 localhost ngircd[1907]: Running with root directory "/var/chroot". Dec 19 09:00:20 localhost ngircd[1907]: IO subsystem: epoll (hint size 100, initial maxfd 100, masterfd 4). Dec 19 09:00:20 localhost ngircd[1907]: Created pre-defined channel "#channel" Dec 19 09:00:20 localhost ngircd[1907]: Now listening on [0::]:1643 (socket 7). Dec 19 09:00:20 localhost ngircd[1907]: Now listening on [192.168.1.1]:1643 (socket 8). Dec 19 09:04:51 localhost ngircd[3177]: /usr/local/etc/ngircd.conf, line 33: Value of "Password" too long! Dec 19 09:04:51 localhost ngircd[3177]: ngircd 19.2-SYSLOG+ZLIB+SSL+IRCPLUS+IPv6-i686/pc/linux-gnu started. Dec 19 09:04:51 localhost ngircd[3177]: Using configuration file "/usr/local/etc/ngircd.conf" ... Dec 19 09:04:51 localhost ngircd[3177]: Configuration option "SSLDHFile" not set! Dec 19 09:04:51 localhost ngircd[3177]: OpenSSL 1.0.1 14 Mar 2012 initialized. Dec 19 09:04:51 localhost ngircd[3177]: Changed root and working directory to "/var/chroot". Dec 19 09:04:51 localhost ngircd[3178]: Running as user unknown(65534), group unknown(65534), with PID 3178. Dec 19 09:04:51 localhost ngircd[3178]: Running with root directory "/var/chroot". Dec 19 09:04:51 localhost ngircd[3178]: IO subsystem: epoll (hint size 100, initial maxfd 100, masterfd 4). Dec 19 09:04:51 localhost ngircd[3178]: Created pre-defined channel "#channel" Dec 19 09:04:51 localhost ngircd[3178]: Now listening on [0::]:1643 (socket 7). Dec 19 09:04:51 localhost ngircd[3178]: Now listening on [192.168.1.1]:1643 (socket 8). Any insight or help is appreciated. Thank you for your time and efforts around ngircd. Respectfully, Nathan

2 12

ngIRCd 20
by Alexander Barton 18 Dez '12

18 Dez '12

Hi All! Finally, after two release candidates, the final version of ngIRCd 20 has been published! Yiiiha! Thanks a lot to all contributors, testers, and otherwiese involved people! Since the last release candidate only a single change has been made: now ngIRCd supports user names ("IDENT names") up to 19 characters length: this can be useful if you want to authenticate your users to some "external" data sources that are already using longer user names than the formerly supported 9 characters. You can read the full ChangeLog and NEWS files online, and it is included in out source distribution archives, of course: • <http://ngircd.barton.de/doc/NEWS> • <http://ngircd.barton.de/doc/ChangeLog> More information can be found on the homepage <http://ngircd.barton.de/> and its mirror <http://ngircd.berlios.de/>. The primary download locations are: • <ftp://ftp.berlios.de/pub/ngircd/> • <http://ngircd.barton.de/pub/ngircd/> And as always: please report any bugs, problems, and regressions to this mailing list or directly using the bug tracker. Or connect to the "official" IRC channel #ngircd on irc.barton.de: <irc://irc.barton.de/ngircd> – thanks! Regards Alex

1 0

ngIRCd 20~rc2
by Alexander Barton 10 Dez '12

10 Dez '12

Hi All! After ngIRCd 20~rc1 a few weeks ago, I just released the second release candidate, ngIRCd 20~rc2. There have been a few fixes and one "feature enhancement" since the first release candidate, see the ChangeLog: • Rework cloaked hostname handling and implement the "METADATA cloakhost" subcommand: Now ngIRCd uses two fields internally, one to store the "real" hostname and one to save the "cloaked" hostname. This allows "foreign servers" (aka "IRC services") to alter the real and cloaked hostnames of clients without problems, even when the user itself issues additional "MODE +x" and "MODE -x" commands. • RPL_UMODEIS: send correct target name, even on server links. • Update platformtest.sh to follow autoconf changes and only generate the "configure" script when it is missing. • Fix the test suite to correctly execute test scripts even when stdout is redirected. • Fix some compiler warnings on NetBSD and OpenBSD. You can find more information on our homepage at <http://ngircd.barton.de/> and its mirror <http://ngircd.berlios.de/>. The primary download locations are: • <ftp://ftp.berlios.de/pub/ngircd/> • <http://ngircd.barton.de/pub/ngircd/> Please test this release candidate and report any problems and bugs you encounter, either to this list, the #ngircd channel on irc.barton.de (<irc://irc.barton.de/#ngircd>), or our bug tracker: • <http://ngircd.barton.de/bugzilla/> Thanks! Alex

2 2

Link for openSUSE rpm's returns empty page
by Thomas Spahni 19 Nov '12

19 Nov '12

Hello all, This is my first post on this ml. I noted that the Download page of the ngircd website (http://ngircd.barton.de/download.php.de) contains this link for openSUSE rpm's: http://software.opensuse.org/download/server:/irc/ A click on the link returns an empty white page. The correct link would be: http://download.opensuse.org/repositories/server:/irc/ Can you please verify and fix this? Thank you very much. Regards, Thomas Spahni

2 1

ngIRCd 20~rc1
by Alexander Barton 19 Nov '12

19 Nov '12

Hello! Last weekend, I prepared the first release candidate for our next major release: ngIRCd 20~rc1. There have been more than 170 commits since our last release (19.2), and quite a few bug reporters and coders have contributed their ideas, written patches, or discussed new features -- thanks a lot! Please (please!) test this release candidate and report all problems, errors, and regressions you encounter! Best is to file bugs and feature requests here: ngIRCd Bug Tracker: <http://ngircd.barton.de/bugzilla/> The NEWS file lists quite a few new features: • Update doc/Services.txt: describe the upcoming version of Anope 1.9.8, then including a protocol module for ngIRCd. And remove our own patches in ./contrib/Anope because they aren't supported any more ... • Implement new "METADATA" command which can be used by remote servers and IRC services to update client metadata like the client info text ("real name"), user name, and hostname, and use this command to configure an cloaked hostname (user mode "+x") on remote servers: This prevents "double cloaking" of hostnames and even cloaked hostnames are in sync on all servers supporting "METADATA" now. • Implement new IRC "SVSNICK" command to allow remote servers (and IRC services) to change nicknames of already registered users. The SVSNICK command itself doesn't change the nickname, but it becomes forwarded to the server to which the user is connected to. And then this server initiates the real nickname changing using regular NICK commands. This allows to run mixed networks with old servers not supporting the SVSNICK command, because SVSNICK commands for nicknames on such servers are silently ignored and don't cause a desynchronization of the network. • New configuration option "MaxListSize" to configure the maximum number of channels returned by a LIST command. The default is 100, as before. • Implement user mode "b", "block messages": when a user has set mode "b", all private messages and notices to this user are blocked if they don't originate from a registered user, an IRC Op, server or service. The originator gets an error numeric sent back in this case, ERR_NONONREG_MSG (486), which is used by UnrealIRCd, too. (Closes #144) • Implement channel mode "V" (invite disallow): If the new channel mode "V" is set, the INVITE command becomes invalid and all clients get the new ERR_NOINVITE_MSG (518) reply. (Closes #143) • Implement channel mode "Q" and user mode "q": Both modes protect users from channel kicks: only IRC operators and servers can kick users having mode "q" or in channels with mode "Q". (Closes #141) • Allow users to "cloak" their hostname only when the configuration variable "CloakHostModeX" (introduced in 19.2) is set. Otherwise, only IRC operators, other servers, and services are allowed to set the user mode "+x": this prevents regular users from changing their hostmask to the name of the IRC server itself, which confused quite a few people ;-) (Closes #133) • New configuration option "OperChanPAutoOp": If disabled, IRC operators don't become channel operators in persistent channels when joining. Enabled by default, which has been the behavior of ngIRCd up to this patch. (Closes #135) • Allow IRC operators to see secret (+s) channels in LIST command as long as the "MorePrivacy" configuration option isn't enabled in the configuration file. (Closes #136) • Implement new (optional) IRC+ "CHARCONV" command to set a client character set that the server translates all messages to/from UTF-8. This feature requires the "libiconv" library and must be enabled using the new "--with-iconv" option of the ./configure script. See doc/Protocol.txt for details. (Closes #109) • Implement user mode "B" ("Bot flag"): it is settable and unsettable by every (non-restricted) client. This is how Unreal and InspIRCd do behave, and so do we :-) • Implement channel mode "M": Only the server, identified users and IRC operators are able to talk in such a channel. • Block nicknames that are reserved for services and are defined using the configuration variable "ServiceMask" in "Server" blocks; And this variable now can handle more than one mask separated by commas. • Implemented XOP channel user modes: "Half Op" ("+h", prefix "%") can set the channel modes +imntvIbek and kick all +v and normal users; "Admin" ("+a", prefix "&") can set channel modes +imntvIbekoRsz and kick all +o, +h, +v and normal users; and "Owner" ("+q", prefix "~") can set channel modes +imntvIbekoRsz and kick all +a, +o, +h, +v and normal users. • Implement hashed cloaked hostnames for both the "CloakHost" and "CloakHostModeX" configuration options: now the admin can use the new '%x' placeholder to insert a hashed version of the clients hostname, and the new configuration option "CloakHostSalt" defines the salt for the hash function. When "CloakHostSalt" is not set (the default), a random salt will be generated after each server restart. You can find more information on our homepage at <http://ngircd.barton.de/> and its mirror <http://ngircd.berlios.de/>. The primary download locations are: • <ftp://ftp.berlios.de/pub/ngircd/> • <http://ngircd.barton.de/pub/ngircd/> Have fun! Alex

2 4

Constants to make configurable?
by Brett Smith 28 Okt '12

28 Okt '12

Hi everyone, After a lot of wait and hurry up, W3C flipped the switch last week and put our ngIRCd server into production. It's been running smoothly ever since and many of our users are quite happy with it. In the run-up to production, we had to adjust a few constants in src/ngircd/defines.h to better suit our needs: * CLIENT_ID_LEN: While I respect the RFC, we had to increase this in order to authenticate users with longer usernames in our existing account system. * MAX_RPL_LIST: We generally have around 200 channels, so the default limit of 100 seemed a little sharp to us. * MAX_RPL_WHO: Users who joined channels with more than 25 people in them were getting notices in their clients about reaching this limit, and they were happy to voice their complaints about it to me. :) Apparently we're not the only ones who have dealt with this: see also <http://colloquy.info/project/ticket/3251>. Would you be willing to consider patches that made all of these values configurable in ngircd.conf's [Limits] section? A patch could also enforce the value of CLIENT_ID_LEN with --strict-rfc. I'd be happy to write something up if we can get it upstream. Thanks again, -- Brett Smith

2 6

Allow more characters in usernames
by Brett Smith 15 Sep '12

15 Sep '12

Hello again, On our site, we have a few users with hyphens in their usernames. They haven't been able to log in to ngIRCd because of the validity tests in <http://arthur.barton.de/cgi-bin/gitweb.cgi?p=ngircd.git;a=commitdiff;h=6680…>. I understand that other ircds use similar checks, but this somewhat limits the value of PAM integration. I've prepared <https://gitorious.org/~bretts/ngircd-irc-daemon/bretts-ngircd/commits/more-…>, which still has some limits that I think are obviously justified (some by the RFC :) ) but is otherwise more permissive. I'd be interested to hear what you think of it. Thanks, -- Brett Smith

2 4

PAM module
by Anthony Caiafa 10 Sep '12

10 Sep '12

Has anyone successfully got the PAM module to work? I can't seem to get it working with LDAP or localauth. Anyone interested in providing their auth file for ngircd?

2 2

Password limitations in ngIRCd
by Brett Smith 26 Aug '12

26 Aug '12

Hello folks, I'm a sysadmin at W3C, and we're looking at using ngIRCd to serve our private staff IRC channel, requiring users to authenticate through PAM. Our initial tests with this have been encouraging, and I really like how clean ngIRCd is, but we have hit a couple of corner cases with authentication I wanted to ask about. First, users who have passwords with spaces in them can't connect. If I've done my homework right, this seems to be a limitation of the IRC protocol itself: when clients connect, they provide all their important information (nick, username, password, etc.) on a space-separated line, so the server has no choice but to parse a password with spaces as multiple fields. Do I have that right? I'd be happy to be told I'm wrong about this if it means I can accommodate these users better. Second, ngIRCd allocates 21 bytes for the password buffer, which is too short for some of our users' passwords. As far as I can tell, a maximum password length isn't defined in the RFC or similar, so I'm guessing this limitation is largely historical. I've patched ngIRCd locally to #define CLIENT_PASS_LEN to 64, which seems to be working with no ill effects. Would you be willing to consider a patch like this upstream? We'd love to be running stock ngIRCd without any patches, even one as trivial as this. Thank you, -- Brett Smith

2 4

systemd service
by keenerd 18 Aug '12

18 Aug '12

Hello all. Linked is a service file for ngircd. Please add this to your source tree so other people don't have to learn to write service files ;-) https://projects.archlinux.org/svntogit/community.git/plain/trunk/ngircd.se… -Kyle Keen Arch Linux TU http://kmkeen.com

2 1

ngIRCd 19.2
by Alexander Barton 19 Jun '12

19 Jun '12

Hi all! About a week after the release candidate, here it is: ngIRCd 19.2. There have been no functional changes since 19.2~rc1, only a documentation fix in ./doc/Capabilities.txt: now the only supported capability "multi-prefix" is described there ;-) Changes and new features since 19.1: - New configuration option "CloakHostModeX" to configure the hostname that gets used for IRC clients which have user mode "+x" enabled. Up to now, the name of the IRC server itself has been used for this, which still is the default when "CloakHostModeX" isn't set. - Correctly handle asynchronously re-established server links: a race condition could let the daemon loose track of an already re-established incoming server link while preparing its own outgoing connection. Peers that both try to connect each other could have been affected. - Log a debug message when SIGUSR2 is handled in debug mode. - Only allow alphanumeric characters in user-supplied user names of USER command and IDENT replies. - Change wording of "TLS initialized" message to make it more consistent. - Don't leak file descriptors on error path when creating "PID files". - Add missing mode "r" to CHANMODES in 005 "ISUPPORT" numeric. - Update doc/Modes.txt and doc/Platforms.txt documents. - contrib/platformtest.sh: correctly detect Open64 C compiler and handle "CC=xxx MAKE=yyy ./platformtest.sh" calling convention. - Add instructions for setting up Atheme IRC services. - Implement support for IRC capability handling, the new "CAP" command, and capablity "multi-prefix" which allows both the NAME and WHO command handlers to return more than one "class prefix" to the client. - Update Xcode project files: reference missing documentation files. - Fix: Don't ignore "permission denied" errors when enabling chroot. - FAQ: enhance description of chroot setup. You can find more information on our homepage at <http://ngircd.barton.de/> and its mirror <http://ngircd.berlios.de/>. The primary download locations are: - <ftp://ftp.berlios.de/pub/ngircd/> - <http://ngircd.barton.de/pub/ngircd/> Please report any bugs and regressions to this mailing list or directly using the bug tracker – thanks! Regards Alex

1 0

ngIRCd 19.2~rc1
by Alexander Barton 13 Jun '12

13 Jun '12

Hello World! The next release of ngIRCd, release 19.2, is on the horizon – and in preparation to this maintenance release, here is the first release candidate. Changes and new features: - New configuration option "CloakHostModeX" to configure the hostname that gets used for IRC clients which have user mode "+x" enabled. Up to now, the name of the IRC server itself has been used for this, which still is the default when "CloakHostModeX" isn't set. - Correctly handle asynchronously re-established server links: a race condition could let the daemon loose track of an already re-established incoming server link while preparing its own outgoing connection. Peers that both try to connect each other could have been affected. - Log a debug message when SIGUSR2 is handled in debug mode. - Only allow alphanumeric characters in user-supplied user names of USER command and IDENT replies. - Change wording of "TLS initialized" message to make it more consistent. - Don't leak file descriptors on error path when creating "PID files". - Add missing mode "r" to CHANMODES in 005 "ISUPPORT" numeric. - Update doc/Modes.txt and doc/Platforms.txt documents. - contrib/platformtest.sh: correctly detect Open64 C compiler and handle "CC=xxx MAKE=yyy ./platformtest.sh" calling convention. - Add instructions for setting up Atheme IRC services. - Implement support for IRC capability handling, the new "CAP" command, and capablity "multi-prefix" which allows both the NAME and WHO command handlers to return more than one "class prefix" to the client. - Update Xcode project files: reference missing documentation files. - Fix: Don't ignore "permission denied" errors when enabling chroot. - FAQ: enhance description of chroot setup. You can find more information on our homepage at <http://ngircd.barton.de/> and its mirror <http://ngircd.berlios.de/>. The primary download locations are: - <ftp://ftp.berlios.de/pub/ngircd/> - <http://ngircd.barton.de/pub/ngircd/> Please report any bugs and regressions to this mailing list or directly using the bug tracker – thanks! Regards Alex

1 0

IRC OP
by "André Z." 25 Mai '12

25 Mai '12

Hallo, ich habe das Problem das ich keine OP (Admin) Rechte mir geben kann, bzw. bekomme. In der Config habe ich auch dafür ein User eingetragen, aber es geht nicht. Bitte um Hilfe. Gruß, André

1 0

Channel Management
by Alessandro Alessio 08 Mai '12

08 Mai '12

Arthur, i solved my login problems. It was an SDL socket problem. So, i created a brand new socket management on my own and now everything works fine. I am actually enjoying checking the various client commands and relative server responds, and i have two questions for you, i believe you can help. On Channel_Create you actually create one channel (&Server) in your server. Then you have another method Channel_InitPredefined(), which created a list of 'predefined' channels contained into a GLOBAL array Conf_Channels. I actually don't understand where (and if) this array is populated. Second question regards messages in chan. Actually the IRC protocol talks about PRVMSG but not about messages that client sends to chan. Is there a prefix or is a server feature, which broadcasts the message to all the clients belonging to the same chan? Tnx again for your help, and congrats for the IRC Server developed. Cheers alex

2 6

User Registration
by Alessandro Alessio 26 Apr '12

26 Apr '12

Hi all, I am a new user of the ngircd. I created an IRC client in C++ and i am now interested in testing it with your ngircd server. i am having some troubles during the registration phase and i don't understand where i am wrong. I wonder if any of you can help. The IRC protocol states that client has to register the user following these steps: 1. Pass message 2. Nick message 2. Service message 3. User message Actually, i create first a socket to the ngicrd (run win -n) which responds "Accepted connection from <IP> on socket <id>" then i send the following messages: PASS NOPASS\n\r NICK giggio\n\r USER guest 0 * :Ronald Reagan\n\r And after a while i get the following answers: Shutting down connection <id> (Timeout) with <IP:port> Client unregistered (<id>) : Timeout I tried to use /PASS or to erase \n\r but i always get a Timeout error. I don't get what i'm doing wrong since i am respecting the IRC Protocol cheers, alex

2 6

Re: [ngIRCd-ML] NGIRCD installation
by Alessandro Alessio 24 Apr '12

24 Apr '12

Well, that is the problem :) No ngircd installed in the directories. And if i run ./ngircd -n i get: Can't read configuration "/usr/local/etc/ngircd.conf": No such file or directory. So, i miss the conf file and i believe that something went wrong in the make install phase, since i got no problems during the ./configure and make phases Tnx Am 24.04.2012 um 14:58 schrieb Alessandro Alessio: > after running 'make install' i do not get any error, but actually i am not sure the install went fine. If you don’t get error messages most probably there haven’t been any errors. So what’s your problem? After running „make install“ you’ll find ngIRCd installed in the default location (usr/local/sbin, /usr/local/etc/ngircd, …) or in the location(s) you passed to the ./configure script. Regards Alex

2 1

Multiple LAN Servers.....
by Damon Talbot 20 Apr '12

20 Apr '12

Hello, I am trying to configure several servers that all connect over a LAN/MESH (AD-HOC) network. I thought I had edited the ngircd.conf right but cannot get it to work. How can I go about doing this? all of the servers would share the same IP since they are on a AD-HOC MESH system KC7NEC Damon

3 2

ngIRCd 19.1
by Alexander Barton 19 Mär '12

19 Mär '12

Hello! I just released the first „bug fix release“ for ngIRCd 19, named „19.1“. You can grab it on the usual locations, see below. All changes are cosmetic (fixed typos in comments and log messages) or fix our build system, there have been no functional changes – so if you built and installed ngIRCd 19 successfully, there is no big reason to update. But feel free to do so anyway :-) Please see the NEWS and ChangeLog files for all the glory details: - <http://ngircd.barton.de/doc/NEWS> - <http://ngircd.barton.de/doc/ChangeLog> You can find more information on our homepage at <http://ngircd.barton.de/> and its mirror <http://ngircd.berlios.de/>. The primary download locations are: - <ftp://ftp.berlios.de/pub/ngircd/> - <http://ngircd.barton.de/pub/ngircd/> Regards Alex

1 0

ngIRCd 19
by Alexander Barton 05 Mär '12

05 Mär '12

Hi List Readers! „We proudly present ngIRCd 19!“ – so here it is, the next stable release of ngIRCd! There have been a few last fixes since the release candidate, for example the „SyslogFacility“ configuration variable should really work now and you can use GCC 2.7.2 again to build it [yeah, I know, who cares – but indeed a few do, including me ;-)]. Besides these fixes, ngIRCd 19 is the most usable release in combination with Anope IRC services ever: lots of enhancements and fixes went in, in addition to an updated Anope protocol module that works with Anope 1.9.6 released in early February (see included ./doc/Services.txt and ./contrib/Anope/README files for details). The flood protection and „abuse prevention behavior“ has been greatly enhanced, for example by introducing new limits for channel ban and invite lists (MODE +b/+I) and other list replies (LIST, WHO, WHOIS, WHOWAS). And there are new commands (like GLINE and KLINE), new user modes (R, C) and channel modes (r, R), and channel exception lists (e) have been implemented as well. Lots of commands have been enhanced to better follow the RFC-specified and/or well known syntax and behavior (MODE, LINKS, WHO, LUSERS, …). Please read the NEWS and ChangeLog files for the whole story: - <http://ngircd.barton.de/doc/NEWS> - <http://ngircd.barton.de/doc/ChangeLog> You can find more information on our homepage at <http://ngircd.barton.de/> and its mirror <http://ngircd.berlios.de/>. The primary download locations are: - <ftp://ftp.berlios.de/pub/ngircd/> - <http://ngircd.barton.de/pub/ngircd/> And as usual: send questions to this list, file bug reports (for bugs and enhancements), send patches, join <irc://irc.barton.de/ngircd>, and have fun! ;-) Regards Alex

1 1

[PATCH] Fix testcase error for Debian using sbuild
by Christoph Biedl 03 Mär '12

03 Mär '12

Hello, for reasons beyond my understanding, when * building the ngircd Debian package (on Linux at least) and * using the sbuild build system, the command "ps -af" does not include the commands running inside the sbuild system. Therefore, start-server.sh will report a fail as getpid.sh cannot not find the ./T-ngircd1 just started although it's actually running. This results in a funny build log ... starting server 1 ... failure! FAIL: start-server1 running connect-test ... ok. PASS: connect-test The self-test of getpid.sh however will likely succeed as it's happy if it sees any process with "sh" somewhere in the name. Things go downhill from there. The confusing things are: * The alternative cowbuilder/pbuilder does not have this problem. * The alternative usage "ps ax" does fine. This took a few days to track down. So, as a quick hack, the patch attached adds another switch to getpid.sh. It's already included in the Debian package ngircd-19-1 uploaded a few hours ago. As briefly discussed in IRC, the whole start-server/getpid thingie is very fragile and needs a cleanup. Unfortunately, any solution has to keep in mind ngircd aims to be portable so we cannot use advanced solutions for the problem of sane daemon starting/stopping like start-stop-daemon. Cheers, Christoph diff --git a/src/testsuite/getpid.sh b/src/testsuite/getpid.sh index fd3b342..19ced76 100755 --- a/src/testsuite/getpid.sh +++ b/src/testsuite/getpid.sh @@ -13,6 +13,8 @@ elif [ $UNAME = "A/UX" ]; then PS_FLAGS="-ae"; PS_PIDCOL="1"; HEAD_FLAGS="-1" elif [ $UNAME = "GNU" ]; then PS_FLAGS="-ax"; PS_PIDCOL="2"; HEAD_FLAGS="-n 1" +elif [ $UNAME = "Linux" ]; then + PS_FLAGS="ax"; PS_PIDCOL="1"; HEAD_FLAGS="-n 1" elif [ $UNAME = "SunOS" ]; then PS_FLAGS="-af"; PS_PIDCOL=2; HEAD_FLAGS="-n 1" else

1 0

ngIRCd 19~rc1
by Alexander Barton 13 Feb '12

13 Feb '12

Hello! Today I prepared the first release candidate for the next release of ngIRCd: version 19~rc1. Since the last release back in July, there have been lots of enhancements, new features, and bug fixes. Thanks to all testers, bug reporters and contributors! There is support for more user modes (like „C“), channel modes (like „R“), IRC commands (like GLINE and KLINE), much better flood and overload protection, and an updated protocol module for Anope IRC services 1.9.6. Please have a look at the GIT history or the NEWS and ChangeLog files: * <http://ngircd.barton.de/doc/NEWS> * <http://ngircd.barton.de/doc/ChangeLog> * <http://ngircd.barton.de/cgi-bin/gitweb.cgi?p=ngircd.git> This is our first release candidate; not the final release. So keep in mind that there can be bugs: please report all problems you encounter, to the mailing list or our bug tracker — thanks! You can find this on the download page and the usual mirrors: * <http://ngircd.barton.de/download> * <http://ngircd.barton.de/pub/ngircd/> * <ftp://ftp.berlios.de/pub/ngircd/> There are source packages, GnuPG signatures, and a binary package for Mac OS X. And I updated my unofficial Debian packages as well. Regards Alex

1 0

qwebirc connection limit
by Rodrigo Valiña Gutiérrez 22 Jan '12

22 Jan '12

hi, I have reached the ip connection limit. is it possible to raise it for webchat (localhost) and not for every ip address?

1 0

"MODE #CHANNEL +b !" can crash the ircd ...
by Cahata 03 Jan '12

03 Jan '12

"MODE #CHANNEL +b !" can crash the ircd ...

4 4

ngIRCd bans doesnt work properly...
by Cahata 24 Dez '11

24 Dez '11

in ngircd bans can be set in freeform dont acording that nick cant exceed "NICKLEN" ident cant be longer that 9 characters and domain name cant exceed 63 characters or longer if subdomain is used ....

1 0

Frage: KLINE
by Michaela Merz 18 Dez '11

18 Dez '11

Hi: Kann man im ngircd /mode +k setzen, um User notfalls komplett aus dem Server zu entfernen? Danke. mm.

5 7

Spam protection
by Sebastian Köhler 16 Dez '11

16 Dez '11

Hi, at the moment I have a problem with someone who is using proxies and/or bots to connect to the server, then he sends a spam message, reconnects with another IP/Nick and sends a slightly modified message again and so on. At the moment I helped myself by setting the channel modes to +m. But I dont really like this. Is there a way to block proxies/bots before they actually connect? I know that other IRC servers can use DNSBLs for that but afaik ngircd doesn't have that option. Sebastian

2 1

Modifications to prevent abuse
by Wyke Yeahman 15 Dez '11

15 Dez '11

Hello, I've modified a bit the source code of ngircd to let the IRC operators to bypass the +x and +i mode, so the commands who, whois, whowas, userhost and list will show the invisible and host masked users and invisible channels. I made it in my network to prevent abuse. However, before releasing the modification, I would like to ask: is that forbidden by the ngircd philosophy? If not, can someone please tell me how to release a patch, so everyone could also use this features? Thanks : )

2 1

ngircd 18 on Nexenta: works
by Götz Hoffart 19 Aug '11

19 Aug '11

ngIRCd 18 has been configured with the following options: Target: i386-pc-solaris2.11 Compiler: gcc -std=gnu99 Compiler flags: -g -O2 -pipe -W -Wall -Wpointer-arith -Wstrict-prototypes -DSYSCONFDIR='"$(sysconfdir)"' Libraries: -lz -lsocket -lnsl 'ngircd' binary: /usr/local/sbin Configuration file: /usr/local/etc Manual pages: /usr/local/share/man Documentation: /usr/local/share/doc/ngircd Syslog support: yes Enable debug code: no zlib compression: yes IRC sniffer: no Use TCP Wrappers: no Strict RFC mode: no IDENT support: no IRC+ protocol: yes IPv6 protocol: no I/O backend: "/dev/poll" PAM support: no SSL support: no the executable works ("runs") as expected --+ tests run successfully ("make check") --+ | ngIRCd compiles ("make") --+ | | ./configure works --+ | | | | | | | Platform Compiler ngIRCd Date Tester C M T R See --------------------------- ------------ ---------- -------- ------ - - - - --- i386/pc/solaris2.11 gcc 4.2.3 18 11-08-17 goetz Y Y Y Y (4) # file src/ngircd/ngircd src/ngircd/ngircd: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), not stripped # uname -a SunOS nexentia 5.11 NexentaOS_134f i86pc i386 i86pc Solaris (Nexenta is in 64 bit mode here) Regards Götz

2 1

ngIRCd 18
by Alexander Barton 10 Jul '11

10 Jul '11

Hi All! Finally, here it is: ngIRCd 18 has been released today! Since our 2nd release candidate, a preliminary protocol module for the upcoming Anope 1.9 services package has been added to our contrib/ directory, our documentation has been slightly updated, and no WHOWAS information will be leaked when disabling „MorePrivacy“ mode during runtime. Please see doc/Services.txt and contrib/Anope/README if you are interested in using ngIRCd 18 with the development branch 1.9.x of Anope IRC services! Latest tested release of Anope is 1.9.4, there is no guarantee that it will work with newer versions, because the 1.9 branch of Anope is under heavy development … Since release 17.1, there is quite a bit of new functionality with new configuration options like „MorePrivacy“, „ScrubCTCP“, „RequireAuthPing“, „ NoticeAuth“, „CloakHost“ and „CloakUserToNick“; a new channel mode „O“ („IRC Ops only“); support for ZeroConf service registration has been removed; and, quite prominent, the restructuring of the ngircd.conf configuration file. Please have a look at our GIT history or the NEWS and ChangeLog files for the whole story: - <http://ngircd.barton.de/doc/NEWS> - <http://ngircd.barton.de/doc/ChangeLog> And please DON’T FORGET TO READ the INSTALL text, it contains valuable upgrading information regarding the new structure of ngircd.conf: - <http://ngircd.barton.de/doc/INSTALL> You can find more information on our homepage at <http://ngircd.barton.de/> and its mirror <http://ngircd.berlios.de/>. Our primary download locations are: - <ftp://ftp.berlios.de/pub/ngircd/> - <http://ngircd.barton.de/pub/ngircd/> I hope you enjoy this new release – have fun! Regards Alex

1 0

ScrubCTCP and MorePrivacy patches
by Alexander Barton 10 Jul '11

10 Jul '11

Hi all! It's me again ;-) I looked into the "ScrubCTCP" and "MorePrivacy" patches of xor (thanks BTW!), and applied them (only slightly modified and adopted to my "newconfig" work) into two branches in my own ngIRCd development repository: ScrubCTCP is here: <https://arthur.barton.de/cgi-bin/gitweb.cgi?p=ngircd-alex.git;a=shortlog;h=…> And MorePrivacy here: <https://arthur.barton.de/cgi-bin/gitweb.cgi?p=ngircd-alex.git;a=shortlog;h=…> What do you think? xor, do you agree with my changes? I would include both branches in our next release -- no? Regards Alex

2 2

sudo nick command for IRC operators
by Rich Griese 10 Jul '11

10 Jul '11

This might exist, but perhaps someone can send me the exact command. I am looking for a command that IRC operators can use that would change another users nickname. Something like; /sudo nick Guest849 peter If this exists could someone send me the syntax? I am running a small IRC network that I use on my website as a simple way for people to contact me real time. The initial page uses a mibbit web interface that asks people to start by entering their nickname, but you would be amazed at how many people just click through with the Guest??? nick. And then... the first thing they will say is "Rich, it's peter". At that point I it would be great for me for me to be able to change their nickname for them instead of telling them how to change their nick themselves. Cheers! RichGriese(a)gmail.com

2 1

ngIRCd 18~rc2 on NetBSD 1.6.2 i386
by Götz Hoffart 10 Jul '11

10 Jul '11

Works fine: ngIRCd 18~rc2 has been configured with the following options: Target: i386-unknown-netbsdelf1.6.2 Compiler: gcc Compiler flags: -g -O2 -pipe -W -Wall -Wpointer-arith -Wstrict-prototypes -DSYSCONFDIR='"$(sysconfdir)"' Libraries: -lz 'ngircd' binary: /usr/local/sbin Configuration file: /usr/local/etc Manual pages: /usr/local/share/man Documentation: /usr/local/share/doc/ngircd Syslog support: yes Enable debug code: no zlib compression: yes IRC sniffer: no Use TCP Wrappers: no Strict RFC mode: no IDENT support: no IRC+ protocol: yes IPv6 protocol: no I/O backend: "poll()" PAM support: no SSL support: no platformtest.sh: Checking ngIRCd base source directory ... platformtest.sh: Checking for "./autogen.sh" script ... platformtest.sh: Running "./configure" script ... platformtest.sh: Running "make" ... platformtest.sh: Running "make check" ... the executable works ("runs") as expected --+ tests run successfully ("make check") --+ | ngIRCd compiles ("make") --+ | | ./configure works --+ | | | | | | | Platform Compiler ngIRCd Date Tester C M T R See --------------------------- ------------ ---------- -------- ------ - - - - --- i386/unknown/netbsdelf1.6.2 gcc 2.95.3 18~rc2 11-07-10 root Y Y Y Y Grüße Götz

2 1

ngircd: Checks on Debian @ MIPS
by Götz Hoffart 10 Jul '11

10 Jul '11

Hi, there are some errors for platformtest.sh on my Cobalt Qube 1, 150 MHz MIPS CPU, 60 MB RAM, Debian 4.0. # cat /etc/debian_version 4.0 # cat /proc/cpuinfo system type : Cobalt Qube processor : 0 cpu model : Nevada V1.0 FPU V1.0 BogoMIPS : 148.99 wait instruction : yes microsecond timers : yes tlb_entries : 48 extra interrupt vector : yes hardware watchpoint : no ASEs implemented : shadow register sets : 1 VCED exceptions : not available VCEI exceptions : not available # time ./configure ngIRCd 18~rc2 has been configured with the following options: Target: mipsel-unknown-linux-gnu Compiler: gcc -std=gnu99 Compiler flags: -g -O2 -pipe -W -Wall -Wpointer-arith -Wstrict-prototypes -DSYSCONFDIR='"$(sysconfdir)"' Libraries: -lz 'ngircd' binary: /usr/local/sbin Configuration file: /usr/local/etc Manual pages: /usr/local/share/man Documentation: /usr/local/share/doc/ngircd Syslog support: yes Enable debug code: no zlib compression: yes IRC sniffer: no Use TCP Wrappers: no Strict RFC mode: no IDENT support: no IRC+ protocol: yes IPv6 protocol: no I/O backend: "epoll(), select()" PAM support: no SSL support: no real 6m3.430s user 3m43.846s sys 2m6.552s # time make real 10m12.506s user 9m21.779s sys 0m35.626s root@qube:~/ngircd-18~rc2/contrib # ./platformtest.sh platformtest.sh: Checking ngIRCd base source directory ... platformtest.sh: Checking for "./autogen.sh" script ... platformtest.sh: Running "./configure" script ... platformtest.sh: Running "make" ... platformtest.sh: Running "make check" ... portabtest.c: In function 'main': portabtest.c:43: warning: the address of 'snprintf', will always evaluate as 'true' portabtest.c:44: warning: the address of 'vsnprintf', will always evaluate as 'true' portabtest.c:45: warning: the address of 'strlcpy', will always evaluate as 'true' portabtest.c:46: warning: the address of 'strlcat', will always evaluate as 'true' ./getpid.sh: line 22: 7161 Speicherzugriffsfehler ps $PS_FLAGS >/dev/null 2>&1 ./getpid.sh: line 31: 7162 Speicherzugriffsfehler ps $PS_FLAGS >procs.tmp ./getpid.sh: line 22: 7185 Speicherzugriffsfehler ps $PS_FLAGS >/dev/null 2>&1 ./getpid.sh: line 31: 7186 Speicherzugriffsfehler ps $PS_FLAGS >procs.tmp make[3]: *** [check-TESTS] Fehler 1 make[2]: *** [check-am] Fehler 2 make[1]: *** [check-recursive] Fehler 1 make: *** [check-recursive] Fehler 1 the executable works ("runs") as expected --+ tests run successfully ("make check") --+ | ngIRCd compiles ("make") --+ | | ./configure works --+ | | | | | | | Platform Compiler ngIRCd Date Tester C M T R See --------------------------- ------------ ---------- -------- ------ - - - - --- mipsel/unknown/linux-gnu gcc 4.1.2 18~rc2 11-07-05 root Y Y N Y (1) Grüße Götz

2 1

ngIRCd 18~rc2
by Alexander Barton 29 Jun '11

29 Jun '11

Moin, moin! This morning I released the 2nd release candidate for the ngIRCd 18 release: ngIRCd 18~rc2. Some documentation and our manual pages have been updated and a SSL-related regression has been fixed, that prevented the current ngIRCd to link with elder releases using SSL. Please have a look at our GIT history or the NEWS and ChangeLog files for the whole story: - <http://ngircd.barton.de/doc/NEWS> - <http://ngircd.barton.de/doc/ChangeLog> And as already stated for the 1st release candidate, please DON’T FORGET TO READ the INSTALL text, it contains valuable upgrading information regarding the new structure of ngircd.conf: - <http://ngircd.barton.de/doc/INSTALL> You can find this prerelease here: - <ftp://ftp.berlios.de/pub/ngircd/> - <ftp://ngircd.barton.de/pub/ngircd/> There are source packages, GnuPG signatures, and a binary package for Mac OS X. Regards Alex

1 0

ngIRCd 18~rc1
by Alexander Barton 28 Jun '11

28 Jun '11

Hi All! Here it is, the first release candidate for ngIRCd release 18! Our last release dates back to 2010, so it’s long overdue … and in the meantime, lots of patches and enhancements have accumulated. All in all, 116 files changed and there were 3590 insertions and 2306 deletions to our codebase since release 17.1 — quite a lot. There is new functionality with new configuration options like „MorePrivacy“, „ScrubCTCP“, „RequireAuthPing“, „ NoticeAuth“, „CloakHost“ and „CloakUserToNick“; a new channel mode „O“ („IRC Ops only“); support for ZeroConf service registration has been removed; and, quite prominent, the restructuring of the ngircd.conf configuration file. Please have a look at our GIT history or the NEWS and ChangeLog files for the whole story: - <http://ngircd.barton.de/doc/NEWS> - <http://ngircd.barton.de/doc/ChangeLog> And please DON’T FORGET TO READ the INSTALL text, it contains valuable upgrading information regarding the new structure of ngircd.conf: - <http://ngircd.barton.de/doc/INSTALL> This is our first release candidate; not the final release. So keep in mind that there can be bugs: please report all problems you encounter, to the mailing list or our bug tracker — thanks! You can find this prerelease here: - <ftp://ftp.berlios.de/pub/ngircd/> - <ftp://ngircd.barton.de/pub/ngircd/> There are source packages, GnuPG signatures, and a binary package for Mac OS X. Regards Alex PS.: I will update my unofficial debian repository as soon as I find time …

1 0

New configuration file layout
by Alexander Barton 25 Jun '11

25 Jun '11

Hi ngIRC'ers! we discussed the layout of ngircd.conf and the massive growth of variables in the [Global] section a few weeks (months!?) ago in irc://irc.barton.de/#ngircd -- today I published a patch restructuring ngircd.conf, please review it and let me know what you think: <https://arthur.barton.de/cgi-bin/gitweb.cgi?p=ngircd-alex.git;a=shortlog;h=…> The new layout splits the variables from [Global] into the sections [Global], [Limits], and [Options]. Left in [Global] are only configuration options that most probably every ngIRCd administrator has to adjust; all the limits (MaxConnections, …) and timeouts (PING, PONG) are stored below [Limits]; and all (optional) features are move into the [Options] section. All moved or renamed variables ("NoPAM = yes" -> "PAM = no") are still recognized in their old location in [Global], but marked as "deprecated" and will emit a warning message when starting ngIRCd or running "ngircd --configtest". So you should be able to use your old configuration file without loss of functionality. There have been no changes to the handling of [Operator], [Server], or [Channel] blocks. What do you think? Regards Alex PS.: this would be the new layout: [GLOBAL] Name AdminInfo1 AdminInfo2 AdminEMail Info Listen MotdFile MotdPhrase Password PidFile Ports ServerGID ServerUID [LIMITS] ConnectRetry MaxConnections MaxConnectionsIP MaxJoins MaxNickLength PingTimeout PongTimeout [OPTIONS] AllowRemoteOper ChrootDir CloakHost CloakUserToNick ConnectIPv4 ConnectIPv6 DNS Ident NoticeAuth OperCanUseMode OperServerMode PAM PredefChannelsOnly RequireAuthPing SSLCertFile SSLDHFile SSLKeyFile SSLKeyFilePassword SSLPorts SyslogFacility WebircPassword [Operator] … [Server] … [Channel] …

2 2

A couple of questions setting up a new server
by Jonathan Coveney 25 Jun '11

25 Jun '11

Hello, and thanks in advance for any help. I want to set up a lightweight IRC server, and ngircd seems perfect. I can't find some documentation on certain things, however... for example, in the README it says "Implemented IRC-commands are: ADMIN, AWAY, CHANINFO, CONNECT, DIE, DISCONNECT, ERROR, HELP, INVITE, ISON, JOIN, KICK, KILL, LINKS, LIST, LUSERS, MODE, MOTD, NAMES, NICK, NJOIN, NOTICE, OPER, PART, PASS, PING, PONG, PRIVMSG, QUIT, REHASH, RESTART, SERVER, SQUIT, STATS, TIME, TOPIC, TRACE, USER, USERHOST, VERSION, WALLOPS, WHO, WHOIS, WHOWAS." However, I can't seem to find the syntax for any of these! I tried using help, but that just brings up MIRC's help. There are a couple of things I'd like to do at the moment, but am unsure of how, for example: I made a persistent room, and want to make myself the operator of it. I used /oper to make myself an irc admin, but /mode #channel +o myname gives me a 'you are not channel operator name.' I can't see in the server logs where to set this, and it seems odd that despite being an irc operator, I can't just force the mode command. If there is a place where things like this are documented more thoroughly I'd lvoe that. Otherwise, I'd deeply appreciate any help you Jon

3 4

A couple of questions setting up a new server
by Jonathan Coveney 21 Jun '11

21 Jun '11

Hello, and thanks in advance for any help (I'm not sure if this is going to double post, forgive me if it does, my mail client bugged). I want to set up a lightweight IRC server, and ngircd seems perfect. I can't find some documentation on certain things, however... for example, in the README it says "Implemented IRC-commands are: ADMIN, AWAY, CHANINFO, CONNECT, DIE, DISCONNECT, ERROR, HELP, INVITE, ISON, JOIN, KICK, KILL, LINKS, LIST, LUSERS, MODE, MOTD, NAMES, NICK, NJOIN, NOTICE, OPER, PART, PASS, PING, PONG, PRIVMSG, QUIT, REHASH, RESTART, SERVER, SQUIT, STATS, TIME, TOPIC, TRACE, USER, USERHOST, VERSION, WALLOPS, WHO, WHOIS, WHOWAS." However, I can't seem to find the syntax for any of these! I tried using help, but that just brings up MIRC's help. There are a couple of things I'd like to do at the moment, but am unsure of how, for example: I made a persistent room, and want to make myself the operator of it. I used /oper to make myself an irc admin, but /mode #channel +o myname gives me a 'you are not channel operator name.' I can't see in the server logs where to set this, and it seems odd that despite being an irc operator, I can't just force the mode command. If there is a place where things like this are documented more thoroughly I'd lvoe that. Otherwise, I'd deeply appreciate any help you Jon

1 0

MorePrivacy patch
by xor 19 Jun '11

19 Jun '11

this patch contains: * Fix for Conf_CloakUserToNick to make it conceal user details (extended user string). * Adds MorePrivacy-feature MorePrivacy censors some user information from being reported by the server. Signon time and idle time is censored. Part and quit messages are made to look the same. WHOWAS requests are silently dropped. All of this is useful if one wish to conceal users that access the ngircd servers from TOR or I2P. View attached file for more info :)

1 0

ScrubCTCP patch
by xor 13 Jun '11

13 Jun '11

This patch makes it possible to scrub incomming CTCP commands from other servers and clients alike. The ngircd oper can enable it from the config file, by adding "ScrubCTCP = yes" under [FEATURES]. It is default off. CTCP can be used to profile IRC users (get user clients name and version, and also their IP addresses). This is not something we like to happen when user pseudonymity/secrecy is important. The server silently drops incomming CTCP requests from both other servers and from users. The server that scrubs CTCP will not forward the CTCP requests to other servers in the network either, which can spell trouble if not every oper knows about the CTCP-scrubbing. Scrubbing CTCP commands also means that it is not possible to send files between users. There is one exception to the CTCP scrubbing performed: ACTION ("/me commands") requests are not scrubbed. ACTION is not dangerous to users (unless they use OTR, which does not encrypt CTCP requests) and most users would be confused if they were just dropped. A CTCP request looks like this: ctcp_char, COMMAND, arg0, arg1, arg2, .. argN, ctcp_char ctcp_char is 0x01. (just like bold is 0x02 and color is 0x03.) They are sent as part of a message and can be delivered to channels and users alike. If there is any error in what I just said, please tell me :D Attached is the patch for ScrubCTCP. I am not that good at writing patches. This is actually my very first one for a real project. So please be patient with me :)

2 1

Re: [ngIRCd-ML] IRC Services (rfc1459) broken on latest git?
by Alexander Barton 12 Mai '11

12 Mai '11

Hello! Am 29.04.2011 um 16:25 schrieb shinji(a)elite-systems.org: > Since you had to relax for rfc1459 and the logs are indicating "rfc1459 compatibility mode" does this mean you are working to support more services protocols? Current development version of ngIRCd has support for the current development branch (1.9) of Anope. However ngIRCd is a „second class citizen“ in Anope world: the protocol module most probably will be moved out of the regular source tree into an „extra“ branch or something like that, because of too little „relevance“. But as of today, the protocol module still lives in modules/protocol/ngircd.cpp (Anope 1.9, current GIT). If you are interested in Anope supporting ngircd, please test current ngIRCd and current Anope versions, and report back to Anope, for example in #anope-devel on irc.teranova.net :-) Regards Alex PS.: please try to „replay to all“ and keep the list in CC:!

2 1

IRC Services (rfc1459) broken on latest git?
by Robert Pendell 29 Apr '11

29 Apr '11

IRC Services support seems to be broken on the latest git. I guess it doesn't help that I'm using a discontinued IRC services application but since it does provide what is needed I've gotten used to using it anyways. On the most recent git (compiled into deb packages) rfc1459 support seems to break. I get the following in my syslog with ircservices attempts to connect. Apr 29 02:48:03 icarus ngircd[1801]: Accepted connection 12 from 127.0.0.1:42754 on socket 9. Apr 29 02:48:03 icarus ngircd[1801]: IDENT lookup for connection 12: no result. Apr 29 02:48:03 icarus ngircd[1801]: Switching connection 12 (" services.example.com") to RFC 1459 compatibility mode. Apr 29 02:48:03 icarus ngircd[1801]: Attention: this server uses a non-standard nick length, but the peer doesn't support the IRC+ extended server handshake! Apr 29 02:48:03 icarus ngircd[1801]: Server "services.example.com" registered (connection 12, 1 hop - direct link). Apr 29 02:48:03 icarus ngircd[1801]: Received command without prefix (connection 12, command "NICK")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "OperServ", client not known (connection 12, command "USER")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "OperServ", client not known (connection 12, command "MODE")!? Apr 29 02:48:03 icarus ngircd[1801]: Received command without prefix (connection 12, command "NICK")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "Global", client not known (connection 12, command "USER")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "Global", client not known (connection 12, command "MODE")!? Apr 29 02:48:03 icarus ngircd[1801]: Received command without prefix (connection 12, command "NICK")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "NickServ", client not known (connection 12, command "USER")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "NickServ", client not known (connection 12, command "MODE")!? Apr 29 02:48:03 icarus ngircd[1801]: Received command without prefix (connection 12, command "NICK")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "ChanServ", client not known (connection 12, command "USER")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "ChanServ", client not known (connection 12, command "MODE")!? Apr 29 02:48:03 icarus ngircd[1801]: Received command without prefix (connection 12, command "NICK")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "MemoServ", client not known (connection 12, command "USER")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "MemoServ", client not known (connection 12, command "MODE")!? Apr 29 02:48:03 icarus ngircd[1801]: Received command without prefix (connection 12, command "NICK")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "StatServ", client not known (connection 12, command "USER")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "StatServ", client not known (connection 12, command "MODE")!? Apr 29 02:48:03 icarus ngircd[1801]: Received command without prefix (connection 12, command "NICK")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "HelpServ", client not known (connection 12, command "USER")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "HelpServ", client not known (connection 12, command "MODE")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "OperServ", client not known (connection 12, command "WALLOPS")!? Just a thought but the buffering may be a bit off on this. It seems the commands from ircservices are not being properly interpreted somewhere. The last built I had that did work correctly. That one had a version string of ngircd-17.1~55-g5417a72 being it was from the git rep when I did it. The one I did just now was done today and I got all those errors above. The debug build doesn't provide any additional information otherwise I would provide that as well. If there is anything you can advise then I'm open for it. Robert Pendell shinji(a)elite-systems.org CAcert Assurer "A perfect world is one of chaos."

3 4

Buffer overflow on user connection
by Terry Baume 28 Apr '11

28 Apr '11

Hello, I am having some trouble with some users connecting to my ngIRCd server - this only seems to affect some users. Here's an extract from my log: > Apr 28 10:46:39 jupiter ngircd[1600]: Accepted connection 13 from > 58.160.178.xxx:54009 on socket 10. > Apr 28 10:46:39 jupiter ngircd[14258]: Can't resolve > "CPE-58-160-178-xxx.hbqy1.fli.bigpond.net.au": Name or service not known > Apr 28 10:46:39 jupiter ngircd[14258]: Possible forgery: > 58.160.178.xxxresolved to CPE-58-160-178-xxx.hbqy1.fli.bigpond.net.au > (which has no ip address) > Apr 28 10:46:39 jupiter ngircd[1600]: New TLSv1 connection using > cipher AES128-SHA on socket 13. > Apr 28 10:46:39 jupiter ngircd[1600]: User "Skiitz!~.(a)58.160.178.xxx" > registered (connection 13). > Apr 28 10:46:39 jupiter ngircd[1600]: Write buffer overflow > (connection 13, size 4036 byte)! > Apr 28 10:46:39 jupiter ngircd[1600]: Shutting down connection 13 > (Write buffer overflow!) with 58.160.178.xxx:54009 ... > Apr 28 10:46:39 jupiter ngircd[1600]: SSL connection 13 shutting down ... > Apr 28 10:46:39 jupiter ngircd[1600]: User "Skiitz!~.(a)58.160.178.xxx" > unregistered (connection 13): Write buffer overflow! > Apr 28 10:46:39 jupiter ngircd[1600]: Connection 13 with > 58.160.178.xxx:54009 closed (in: 0.0k, out: 11.9k). My interpretation of the log is that the client is exceeding ngIRCd's buffer size - can this parameter be tuned, or is this a misbehaving (outside of RFC) client? Terry.

2 3

re; PredefChannelsOnly = yes
by Rich Griese 16 Mär '11

16 Mär '11

Hey there, Thanks for the; PredefChannelsOnly = yes advice. I tried putting it in the global and then the channel section, and it is not doing the job I put it in my /usr/local/etc/ngircd.conf and then stopped and started the ngirdc is there a trick I am missing? Cheers! RichGriese(a)gmail.com

4 8

replay recent messages on joining persistent chatroom
by Brendan Miller 16 Mär '11

16 Mär '11

For some jabber based chatrooms, there seems to be a way to make the server play back recent messages on joining, so that you can see what the conversation was about before you joined. Is there a setting to make ngircd do this?

2 1

can't connect from other than localhost
by Brendan Miller 02 Mär '11

02 Mär '11

I just installed ngirc for the first time. Currently, I can connect to ngirc from localhost; however, from other machines I cannot connect. It tried troubleshooting with netcat and wireshark a bit. When I connect with netcat to port 6667 from another machine, my connection ins't refused, but I don't seem to be getting any kind of response back from the server either. Not even an ACK. Any suggestions? I'm wondering if there's some switch I have to flip to get it to talk to something other than localhost. Thanks

2 1

Forcing SSL only listeners
by Darren Spruell 28 Feb '11

28 Feb '11

I have a use case for an ircd that provides SSL/TLS only service. ngIRCd looks like it will support both SSL and non-SSL encrypted services through the use of 'Ports' and 'SSLPorts' configuration options. I can use iptables to block connections to the vanilla IRC service port but it seems an option to force SSL/TLS only (or disable non-SSL service) would be more elegant. Has this scenario been discussed before? Shall I add a bugtraq entry for a feature request to support this capability? Thx, -- Darren Spruell phatbuckett(a)gmail.com

1 1

Default Client/Channel Modes
by Jerome Rose 25 Feb '11

25 Feb '11

Is there an way to set the default mode for new clients and/or channels? Thanks, Jerome

4 4

gnutls_handshake: Could not negotiate a supported cipher suite.
by Georges POLITIS 06 Jan '11

06 Jan '11

Hi, I am tried to setup an SSL protected irc server using ngIRCd and I epicly failed. Here's my ngircd.conf: [Global] SSLPorts = 17667 SSLKeyFile = /etc/ngircd/ngircd-key.pem SSLCertFile = /etc/ngircd/ngircd-cert.pem SSLDHFile = /etc/ngircd/ngircd-params.pem Name = irc.debian.org Info = Yet another IRC Server running on Debian GNU/Linux AdminInfo1 = Debian User AdminInfo2 = Debian City AdminEMail = root@localhost MotdFile = /etc/ngircd/ngircd.motd PidFile = /var/run/ngircd/ngircd.pid PingTimeout = 120 PongTimeout = 20 ConnectRetry = 60 OperCanUseMode = yes MaxConnections = 500 MaxConnectionsIP = 10 MaxJoins = 10 The problem is that SSL initialisation fails. Here's the relevant /var/log/syslog output: Jan 5 21:31:12 chronos ngircd[12609]: ngircd 15-SYSLOG+ZLIB+SSL+IRCPLUS+IPv6-i486/pc/linux-gnu started. Jan 5 21:31:12 chronos ngircd[12609]: Reading configuration from "/etc/ngircd/ngircd.conf" ... Jan 5 21:31:12 chronos ngircd[12609]: gnutls_certificate_set_x509_key_file (cert /etc/ngircd/ngircd-cert.pem, key /etc/ngircd/ngircd-key.pem): Base64 decoding error. Jan 5 21:31:12 chronos ngircd[12609]: Warning: Error during SSL initialization, continuing ... Jan 5 21:31:12 chronos ngircd[12609]: ServerUID must not be 0, using "nobody" instead. Jan 5 21:31:12 chronos ngircd[12609]: Can't change group ID to 65534: Operation not permitted Jan 5 21:31:12 chronos ngircd[12609]: Can't change user ID to 65534: Operation not permitted Jan 5 21:31:12 chronos ngircd[12610]: Running as user irc(39), group irc(39), with PID 12610. Jan 5 21:31:12 chronos ngircd[12610]: Not running with changed root directory. Jan 5 21:31:12 chronos ngircd[12610]: Notice: Can't change working directory to "/var/run/ircd": No such file or directory Jan 5 21:31:12 chronos ngircd[12610]: IO subsystem: poll (initial maxfd 100). Jan 5 21:31:12 chronos ngircd[12610]: Now listening on [0::]:17667 (socket 5). Jan 5 21:31:12 chronos ngircd[12610]: Now listening on [0.0.0.0]:17667 (socket 6). I doubt it is a permissions problem. Here's the /etc/ngircd directory listing: gp@chronos:/etc/ssl$ sudo ls -l /etc/ngircd/ total 20 -rwxrwxrwx 1 irc irc 0 2011-01-05 21:21 ngircd-cert.pem -rw-r--r-- 1 irc irc 4839 2011-01-05 21:29 ngircd.conf -rwxrwxrwx 1 irc irc 1238 2011-01-05 21:25 ngircd-dhparams.pem -rwxrwxrwx 1 irc irc 1675 2011-01-05 21:21 ngircd-key.pem -rw-r--r-- 1 irc irc 255 2010-05-11 19:16 ngircd.motd gp@chronos:/etc/ssl$ I've read the SSL guide (found here http://ngircd.barton.de/doc/SSL.txt) and it lists 2 methods for creating the SSL certificate/private key. I've used both without success. Does anyone have any ideas? Thank you in advance. Georges

3 2

ngIRCd 17.1
by Alexander Barton 19 Dez '10

19 Dez '10

Hi All! Not that long ago, ngIRCd 17 has been released. Sadly a few bugs have slipped in, which have been fixed in this new release: 17.1. – in addition a few minor new features have been implemented which are also part of this release. The changes since release 17 are: * --configtest: remember if MOTD is configured by file or phrase * Enhance log messages when establishing server links a little bit * Reset ID of outgoing server link on DNS error correctly * Don't log critical (or worse) messages to stderr * Manual page ngircd(8): add SIGNALS section * Manual pages: update and simplyfy AUTHORS section * Remove "error file" when compiled with debug code enabled * README: Updated list of implemented commands * add doc/README-Interix.txt and doc/Bopm.txt to distribution tarball * add doc/PAM.txt to distribution tarball * New numeric 329: get channel creation time on "MODE #chan" commands * Save channel creation time; new function Channel_CreationTime() The most important fix is "Reset ID of outgoing server link on DNS error correctly“: this could result in ngircd never trying to re-connect to a particular server when a DNS error occurred and to a permanently split network :-/ The new release can be downloaded here: * <ftp://ftp.berlios.de/pub/ngircd/ngircd-17.1.tar.gz> * <ftp://ngircd.barton.de/pub/ngircd/ngircd-17.1.tar.gz> GnuPG signatures for release 17.1, a Mac OS X package, patches from release 17 as well as further archive formats are available as well and can be downloaded from here: * <ftp://ngircd.barton.de/pub/ngircd/> * <ftp://ftp.berlios.de/pub/ngircd/> You can have a look at the complete history and every single patch using the GIT web-frontend located at: * <http://ngircd.barton.de/cgi-bin/gitweb.cgi?p=ngircd.git> I hope that there are now showstoppers … please report all bugs using our bug tracker (<http://ngircd.barton.de/bugzilla/index.cgi>) and/or this mailing list. Have fun! Regards Alex

1 0

Support for qwebirc?
by Travis King 28 Nov '10

28 Nov '10

I'm planning on using ngircd(I've used it back on a VPS with release 13 or so before), as an ICB[1] wannabe with a web interface, as a simple synchronous text chat system for a small group of people who are either slackers(I am one too!) or not nerdic-inclined. For this I would probably be using some OpenBSD(It just works, pretty simple all around) box on my local network, with ngircd compiled as: --disable-ircplus --with-openssl --without-zeroconf --without-ident --without-pam --without-zlib --disable-ipv6 I would then set up 'proper' https on something like thttpd[2](is this a good idea? I'd rather not deal with Apache) to host qwebirc[3]. It would be https web only access to limit user confusion. If someone can suggest a better web interface to IRC I would be open - but I'm looking at qwebirc because Freenode uses it. Has anyone done anything similar? The only negative thing I can think of(right now) would be no DCC SEND support for file transfers due to the web interface, but considering everyone is behind broken networks anyway(NAT), we'll probably use some private FTP. Thank you. PS: I wonder if --enable-strict-rfc would cause problems with qwebirc or others, as I don't plan on having traditional IRC clients(except a convenient bot) connect and I know it breaks mIRC. Then again, it shouldn't matter, but it helped a friend when he only had telnet and a copy of the RFCs - it also feels good in an OCD sort of way. [1] http://www.icb.net/ [2] http://www.qwebirc.org/ [3] http://www.acme.com/software/thttpd/ -- end

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

ngIRCd Users