ngIRCd Users

ngircd@lists.barton.de

424 Diskussionen

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

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