ngIRCd Users

ngircd@lists.barton.de

424 Diskussionen

ngIRCd 17
by Alexander Barton 07 Nov '10

07 Nov '10

Hello World! We proudly present … ngIRCd 17! :-) After three release candidates, here it is, the new release. The most prominent new features are that user mode „c“ (show connect/disconnect NOTICEs, required for e.g. BOPM) and „x“ (hostname cloaking) have been implemented, and support for user authentication using PAM has been added. New configuration options „NoPAM“, „NoZeroConf“, and „SyslogFacility“ were supplemented and allow even better customization of ngIRCd. In addition, the debug mode has been enhanced, the daemon can dump its internal state now, which eases bug fixing. And the power of IRC operators has been raised: now they can use MODE on any channel and always change channel modes. The NEWS file lists the following new features since our last release (r16): * doc: change path names in sample-ngircd.conf depending on sysconfdir * Generate ngIRCd version number from GIT tag. * Make sourcecode compatible with ansi2knr again. This allows to compile ngIRCd using a pre-ANSI K&R C compiler again. * New configuration option "NoZeroConf" to disable service registration at runtime even if ngIRCd is compiled with support for ZeroConf (e.g. using Howl, Avahi or on Mac OS X). * New configuration option "SyslogFacility" to define the syslog "facility" (the "target"), to which ngIRCd should send its log messages. Possible values are system dependant, but most probably "auth", "daemon", "user" and "local1" through "local7" are possible values; see syslog(3). Default is "local5" for historical reasons. * Dump the "internal server state" (configured servers, established connections and known clients) to the console or syslog when receiving the SIGUSR2 signal and debug mode is enabled. * Enable the daemon to disable and enable "debug mode" on runtime using signal SIGUSR1, when debug code is compiled in, not only on startup using the command line parameters. * Implement user mode "x": hostname cloaking (closes: #102). * Change MOTD file handling: ngIRCd now caches the contens of the MOTD file, so the daemon now requires a HUP signal or REHASH command to re-read the MOTD file when its content changed. * Allow IRC ops to change channel modes even without OperServerMode set. * Allow IRC operators to use MODE command on any channel (closes: #100). * New configuration option "NoPAM" to disable PAM. * Implement asynchronous user authentication using PAM, please see the file doc/PAM.txt for details. * Add some documentation for using BOPM with ngIRCd, see doc/Bopm.txt. * Implement user mode "c": receive connect/disconnect NOTICEs. Note that this new mode requires the user to be an IRC operator. * Show SSL status in WHOIS output, numeric 275. Please see the ChangeLog for a list of all changes — it is available in the archive and online: <http://ngircd.berlios.de/doc/ChangeLog>. The new release can be downloaded here: * <ftp://ftp.berlios.de/pub/ngircd/ngircd-17.tar.gz> * <ftp://ngircd.barton.de/pub/ngircd/ngircd-17.tar.gz> GnuPG signatures for release 17, a Mac OS X package, patches from release 16 and 17~rc3 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. Thanks for your support! Regards Alex P.S.: I updated my unofficial Debian packages already: <http://debian.barton.de>

1 0

ngIRCd 17~rc2
by Alexander Barton 25 Okt '10

25 Okt '10

Hi All! Not quite a week later, there is the 2nd release candidate for the upcoming ngIRCd release 17 available for downloading and testing. The changes since -rc1 are: * doc/Makefile.am: don¹t set docdir, automake handles it already * Only use "__attribute__ ((unused))" if GCC >=2.8 is used * Only try to set FD_CLOEXEC if this flag is defined * Added m68k/apple/aux3.0.1 (gcc 2.7.2) to doc/Platforms.txt * Don't use PARAMS() macro for function implementations * ./configure: check support for C prototypes again * ./configure: check if C compiler can compile ISO Standard C * Make sourcecode compatible with ansi2knr again * Generate ngIRCd version number from GIT tag * ZeroConf: include header files missing since commit a988bbc86a * New doc/HowToRelease.txt file describing the release process * Updated contrib/platformtest.sh (new version scheme) So the biggest change is that really old compilers (pre-ANSI) are supported again; this has been tested on ancient Apple UNIX (A/UX) 3.0. If you want to test ngIRCd yourself, you can use the sequenze tar xzf ngircd-17~rc2.tar.gz cd ngircd-17~rc2 contrib/platformtest.sh which will (hopefully) result in a nice summary after compiling the daemon and running the test suite. The release candidate is available for downloading and testing at the usual locations: <ftp://ftp.berlios.de/pub/ngircd/ngircd-17~rc2.tar.gz> <ftp://ngircd.barton.de/pub/ngircd/ngircd-17~rc2.tar.gz> The GnuPG signatures for 17~rc2 and patches from release 17~rc1 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> Please test this release candidate thoroughly and report all bugs and problems you encounter using the bug tracker (<http://ngircd.barton.de/bugzilla/index.cgi>) and/or this mailing list. I think I'll update my Debian packages with this release candidate as well as build a new Mac OS X package, so that this code gets even more testing. What do you think? Regards Alex

1 0

ngIRCd 17~rc1
by Alexander Barton 20 Okt '10

20 Okt '10

(My last mail didn’t reach its recipients; /me should use the correct mailing list address in the future – so here my next try…) Hello World! After about 6 months of development, we are in preparation for the next ngIRCd release which will be release 17. I uploaded the first release candidate for the upcoming release, please test! The following new features and changes have been coded, most notably ngIRCd now supports user authentication using PAM, supports hostname cloaking (user mode „x“), and supports BOPM, the open proxy monitor. The full NEWS file lists: * New configuration option "NoZeroConf" to disable service registration at runtime even if ngIRCd is compiled with support for ZeroConf (e.g. using Howl, Avahi or on Mac OS X). * New configuration option "SyslogFacility" to define the syslog "facility" (the "target"), to which ngIRCd should send its log messages. Possible values are system dependant, but most probably "auth", "daemon", "user" and "local1" through "local7" are possible values; see syslog(3). Default is "local5" for historical reasons. * Dump the "internal server state" (configured servers, established connections and known clients) to the console or syslog when receiving the SIGUSR2 signal and debug mode is enabled. * Enable the daemon to disable and enable "debug mode" on runtime using signal SIGUSR1, when debug code is compiled in, not only on startup using the command line parameters. * Implement user mode "x": hostname cloaking (closes: #102). * Change MOTD file handling: ngIRCd now caches the contens of the MOTD file, so the daemon now requires a HUP signal or REHASH command to re-read the MOTD file when its content changed. * Allow IRC ops to change channel modes even without OperServerMode set. * Allow IRC operators to use MODE command on any channel (closes: #100). * New configuration option "NoPAM" to disable PAM. * Implement asynchronous user authentication using PAM, please see the file doc/PAM.txt for details. * Implement user mode "c": receive connect/disconnect NOTICEs. Note that this new mode requires the user to be an IRC operator. * Show SSL status in WHOIS output, numeric 275. The release candidate is available for downloading and testing at the usual locations: <ftp://ftp.berlios.de/pub/ngircd/ngircd-17~rc1.tar.gz> <ftp://ngircd.barton.de/pub/ngircd/ngircd-17~rc1.tar.gz> The GnuPG signatures for 17~rc1 and patches from release 16 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> Please test this release candidate thoroughly and report all bugs and problems you encounter using the bug tracker (<http://ngircd.barton.de/bugzilla/index.cgi>) and/or this mailing list. Are features missing, for release 17 or later? Please file „enhancement“ bugs as well! And patches are welcome, too ;-) Thanks a lot for your support! Regards Alex

1 0

nevermind....
by Rich Griese 15 Aug '10

15 Aug '10

Mivermind folks. I realized that my client was using a different /open name password than I had adjusted in the .conf what a moron I am. On the good news front. I have my server limited to my one channel, and don't have to worry about idiots using it. oh... now that I say that.... from a utilization of resources standpoint. How to you prevent people from joining the SERVER and not a channel. I mean, and this is a bit ridiculas, but two people could join the server, and not the one allowed channel, but could use the / msg command to talk to each other. I run this server on a mac mini, and am looking for every way to eliminate any user other than the ones that are using the server/channel for it's purpose. Any thoughts. Cheers! RichGriese(a)gmail.com

2 1

upgraded to release 16 and can limit to predefined, but....
by Rich Griese 15 Aug '10

15 Aug '10

I made progress. I upgraded to release 16 and now can limit channels to the one I want. problem though.... I am not longer getting ops. Can you tell me what commands need to go in the .conf file, AND what commands I execute to identify as a operator, and then op myself in my channel. Cheers! RichGriese(a)gmail.com

1 0

question about limiting channels
by Rich Griese 13 Aug '10

13 Aug '10

I have been running the ngircd for a while, now and it works fine. I have been using it as a user support system, and they way I have it confirmed is that I set up a server password, and was using cgi:irc. I could with that web client prevent the /join command from working. So in effect I did not have to worry about any connecting and using any channel than the one I had set up and monitored. The server required a password, the only one that knew the password was the cgi:irc client, and only using that client was forced to my one channel, and could not issue a /join command. I am not having troulbe with cgi:irc on a new server. My question. Can I set ngircd up so that users CANNOT create channels? I want to set up a mibbit widget that wil allow people to join the server, and my one user help channel, but I want to prevent anyone from doing a /join #yaya and creating another channel. I can't find anything in the docs for the .conf file, but found this mailing list and thought I would ask. I had been limiting channel access before by the one web client i allowed to access the system. Now I want to know if I can set the ngircd server itself to limit channels. Cheers! RichGriese(a)gmail.com

3 2

Patch to show SSL status in WHOIS
by Neale Pickett 23 Jun '10

23 Jun '10

I've been wanting this for years and finally took the 5 minutes to patch it in. I took the response code (275) from whatever's running OFTC's IRC network. diff -ur ngircd-16.orig/src/ngircd/irc-info.c ngircd-16/src/ngircd/irc-info.c --- ngircd-16.orig/src/ngircd/irc-info.c 2010-04-25 06:06:29.000000000 -0500 +++ ngircd-16/src/ngircd/irc-info.c 2010-06-11 17:23:18.000000000 -0500 @@ -993,6 +993,13 @@ if( ! IRC_WriteStrClient( from, RPL_WHOISOPERATOR_MSG, Client_ID( from ), Client_ID( c ))) return DISCONNECTED; } + + /* Connected using SSL? */ + if( Conn_UsesSSL(Client_Conn(c))) + { + if( ! IRC_WriteStrClient( from, RPL_WHOISSSL_MSG, Client_ID( from ), Client_ID( c ))) return DISCONNECTED; + } + /* Idle and signon time (local clients only!) */ if (Client_Conn(c) > NONE ) { if (! IRC_WriteStrClient(from, RPL_WHOISIDLE_MSG, diff -ur ngircd-16.orig/src/ngircd/messages.h ngircd-16/src/ngircd/messages.h --- ngircd-16.orig/src/ngircd/messages.h 2010-04-25 06:06:29.000000000 -0500 +++ ngircd-16/src/ngircd/messages.h 2010-06-11 17:20:34.000000000 -0500 @@ -47,6 +47,7 @@ #define RPL_LOCALUSERS_MSG "265 %s %lu %lu :Current local users: %lu, Max: %lu" #define RPL_NETUSERS_MSG "266 %s %lu %lu :Current global users: %lu, Max: %lu" #define RPL_STATSCONN_MSG "250 %s :Highest connection count: %lu (%lu connections received)" +#define RPL_WHOISSSL_MSG "275 %s %s :is connected via SSL (secure link)" #define RPL_AWAY_MSG "301 %s %s :%s" #define RPL_USERHOST_MSG "302 %s :"

2 2

ngIRCd Release 16
by Alexander Barton 04 Mai '10

04 Mai '10

Hi All! ngIRCd 16 has been released and is available from the usual locations, see below. Since our last stable release, release 15, the most notably changes are: - Enhace connection statistics counters: display total number of served connections on daemon shutdown and when a new client connects using the new numeric RPL_STATSCONN (250). - Various fixes to the build system and code cleanups. - Added missing modes to USERMODES #define - Show our name (IRCD=ngIRCd) in ISUPPORT (005) numeric - Quote received messages of ERROR commands in log output. - ngircd.conf manual page: document missing "Password" variable. - Implement WEBIRC command used by some Web-IRC frontends. The password required to secure this command must be configured using the new "WebircPassword" variable in the ngircd.conf file. - Remove limit on max number of configured irc operators. - Only link "nsl" library when really needed. - A new channel mode "secure connections only" (+z) has been implemented: Only clients using a SSL encrypted connection to the server are allowed to join such a channel. But please note three things: a) already joined clients are not checked when setting this mode, b) IRC operators are always allowed to join every channel, and c) remote clients using a server not supporting this mode are not checked either and therefore always allowed to join. Please see the ChangeLog file (or even better: the GIT history) for the complete list of all the changes committed. As usua, you can download ngIRCd release 15 from these locations: <ftp://ftp.berlios.de/pub/ngircd/ngircd-16.tar.gz> <ftp://ngircd.barton.de/pub/ngircd/ngircd-16.tar.gz> GnuPG signatures for release 16, a Mac OS X installer package, and patches from release 15 are available, too, and can be downloaded from here: <ftp://ngircd.barton.de/pub/ngircd/> <ftp://ftp.berlios.de/pub/ngircd/> The relevant MD5 sums are: ngircd-15.tar.gz: c183a85eba6fe51255983848f099c8ae ngircd-14.1-15.patch.gz: 8a114618bfc23d3301762e0dbee704ac 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> Please let us know if you encounter any bugs or need more or better documentation (best is to file bugs using the bug tracker or to mail to this list). Thanks a lot for your support! Regards Alex

1 1

ngIRCd-Foo when leaving a channel?
by Götz Hoffart 29 Apr '10

29 Apr '10

Hi, since a few days I noticed a strange behaviour. See this log from irssi: […] 19:03:11 * po||ux macht dann mal Feierabend. 19:03:13 <@po||ux> bye! 19:06:25 < tooltime> cu 19:06:33 < SirLani> tschö 19:10:12 -!- po||ux [~alex@…] has left #… [Heim. Biergarten. Juhu!] 19:10:17 < po||ux> 7aw 19:10:32 < SirLani> eh 19:10:34 < SirLani> hä!? 19:10:58 < SirLani> po||ux hat den Chatraum verlassen und sagt danach noch was? 19:17:42 -!- sepia [~lucia@…] has joined #… 19:17:53 < sepia> Abend! 19:18:07 < tooltime> re 19:32:08 -!- You're now known as allerbest 19:32:20 < allerbest> re 19:32:32 < allerbest> SirLani: das hat mich neulich schon gewundert […] We had this a few days earlier, too—with exactly the same behaviour: po||ux leaves (timestamp 19:10:12) and a few seconds after that “he” writes “7aw” (timestamp 19:10:17) to the channel. Last time I thought of a random hiccup or cosmic ray or dying bits in non-ECC memory. But this time two people mentioned the behaviour _and_ it was the exact same string “po||ux” sent after leaving. I'm using: # ngircd --version ngircd 15-SYSLOG+ZLIB+SSL+TCPWRAP+IDENT+IRCPLUS+IPv6-i486/pc/linux-gnu Regards Götz

2 1

Web: Suggestion: clarify mailing list status
by usenet＠hoffart.de 25 Apr '10

25 Apr '10

Hi, I think it should be noted in the »Support« section of the website, that any feedback is appreciated even without subscribing to the mailing list. The text now doesn't state clearly that it is not necessary to subscribe to the mailing list. This can be hurdle for some users. Regards Götz -- http://www.knubbelmac.de/

2 1

Springe zur Seite:

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