ngIRCd Users

ngircd@lists.barton.de

1 Teilnehmer
425 Diskussionen

ngIRCd 0.10.0-pre1
by Alexander Barton 30 Aug '06

30 Aug '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi All! After a quite long time, the next release of ngIRCd, version 0.10.0, is pending. Before releasing this new version, we will publish at least one pre-release which this mail is now announcing: ngIRCd 0.10.0-pre1! ngIRCd 0.10.0 can be downloaded from the following locations: <ftp://ftp.berlios.de/pub/ngircd/ngircd-0.10.0-pre1.tar.gz> <ftp://ngircd.barton.de/pub/ngircd/ngircd-0.10.0-pre1.tar.gz> The GnuPG signature and a patch from 0.9.2 is available and can be downloaded from here: <ftp://ngircd.barton.de/pub/ngircd/> This pre-release is tagged as "rel-0-10-0-pre1" in CVS; the branch for the 0.10.x releases is named "branch-0-10-x". Changes since ngIRCd 0.9.2 are: - Validate "ServerName" (see RFC 2812, section 2.3.1). - Enhanced DIE to accept a single parameter ("comment text") which is sent to all locally connected clients before the server goes down. - The ngIRCd handles time shifts backwards more gracefully now (the timeout handling doesn't disconnect clients by mistake any more). - Internal: Restructured connection handling (the connection ID is equal to the file descriptor of the connection). - Internal: Simplified resolver code. - JOIN now supports more than one channel key at a time. - Implemented numeric "333": Time and user name who set a channel topic. - Enhanced the handler for PING and PONG commands: fix forwarding and enable back-passing of a client supplied additional argument of PING. - Changed handling of timeouts for unregistered connections: don't reset the counter if data is received and disconnect clients earlier. - Removed unnecessary #define of "LOCAL", now use plain C "static" instead. - Channel topics are no longer limited to 127 characters: now the only limit is the maximum length of an IRC command, i. e. 512 bytes (in practice, this limits the topic to about 490 characters due to protocol overhead). - Reverse DNS lookup code now checks the result by doing an additional lookup to prevent spoofing. - Added new IO layer which (optionally) supports epoll() and kqueue () in addition to the select() interface. Please test this release and let us know which problems you encounter and which changes should be made for the final 0.10.0 release. Thanks! Regards Alex -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) iD8DBQFE01CLwkoPY342SFYRAgkRAJ9nUDzKIe580W5CUnUFXQCUKlZv8wCgqlP8 eY+Y5NaVQnbjFOJNEVvrKEs= =d8Zm -----END PGP SIGNATURE-----

3 3

Newbie Questions about ngIRCd
by Stephan Fabel 02 Mär '06

02 Mär '06

Hi list, I'm new to the topic of IRC (as an admin), and am in the following situation: I would like to set up an IRC server, with the following features: - four permanent groups, two of those should be password protected - assign a password for connection to the server - use SSL as a connection possibility - user administration: make certain users (identified by a password) channel operators on "their" channels I know about stunnel, but would prefer a "native" solution. If this is not possible at the moment, stunnel would work. I already assigned a password to the server for connection, and so far this works as well. What doesn't seem to work (or I am too blind to find it in the docs) is how to make a permanent channel password protected and how to "administer" the operators insofar as when they log in, they automatically get +o set on their channel. If a user doesn't provide a password (to become operator), he should not be denied access, but simply not be able to get op status or open new channels. If possible, I would like to avoid a channel bot. Is there a way for ngIRCd to have these features? Thanks, Stephan

1 0

Channel Operators
by Michael Belanger 01 Feb '06

01 Feb '06

Greetings, I have been running ngIRC for a few days and am impressed with how quickly it compiled and just worked nearly out of the box! I have currently two static channels defined in the config file for ngirc. However, I seem to be missing a critical piece of information to setup channel operators. It appears that the operator is normally the channel creator -- when the channel is created on the fly.. For these static channels, I would think that it is predefined in the configuration somewhere. The example conf does not show such an option. Can anyone guide me to the solution? Much thanks! -M -- Michael Belanger CICLOPS, Space Science Institute Join us on IRC: irc.ciclops.org channel #ciclops

2 2

Compile without NickServ support?
by AA 29 Jan '06

29 Jan '06

Hello, I would like to not have to mess with NickServer. I will be running this IRC server on a private LAN with no outside access and do not want to have to mess with registration. Would I just be able to add --disable-nickserv when running the ./configure script? Thanks much, Aaron

2 1

How to register nicks and channels?
by Martin Wegner 16 Jan '06

16 Jan '06

Hello. Is it possible for users to register nicknames or channels in ngircd? If yes, how? NickServ and ChanServ I know from other IRC servers do not exist, right? I have created an oper in ngircd.conf: [Operator] Name = martin Password = xxxxxxxxxx I have my username set to "martin". How can I identify myself with a password to be the operator? How can I define OPs for a persistent channel? Thanks in advance, martin -- Get my public GPG key from pgp.mit.edu or wwwkeys.pgp.net Key ID: 0x44085D12 -- Homepage: http://mroot.net/ Powered by Gentoo Linux (http://gentoo.org/)

3 2

ngIRCd in Debian!
by Alexander Barton 06 Dez '05

06 Dez '05

Hi all! I just want to let you know that ngIRCd has been added to the "unstable" and "testing" distribution of Debian Linux: <http://packages.debian.org/testing/net/ngircd> Thanks to Mario Iseli! Regards Alex PS.: Now I have to test this package myself :-)

1 0

ngIRCd 0.9.2
by Alexander Barton 15 Okt '05

15 Okt '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi All! There have been a few fixes for the 0.9.x branch of ngIRCd, so here comes the next release: ngIRCd 0.9.2! ngIRCd 0.9.2 can be downloaded from the following places: <ftp://ftp.berlios.de/pub/ngircd/ngircd-0.9.2.tar.gz> <ftp://ngircd.barton.de/pub/ngircd/ngircd-0.9.2.tar.gz> And soon it should be available via HTTP from this site: <http://download.berlios.de/ngircd/ngircd-0.9.2.tar.gz> The GnuPG signature and a patch from 0.9.0 is available and can be downloaded from here: <ftp://ngircd.barton.de/pub/ngircd/> This release is tagged as "rel-0-9-2" in CVS. Changes since ngIRCd 0.9.1 are: - Fixed a bug that could cause the damon to crash when outgoing server connections can't be established. - Fixed a bug that caused the daemon to leak file descriptors when no resolver subprocesses could be created. - Fixed server NOTICEs to users with "s" mode ("server messages"). - Fixed a format string bug in "connection statistics" messages to clients. Regards Alex - -- Alexander Barton, Freiburg, Germany alex(a)barton.de, http://www.barton.de/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDUQXXwkoPY342SFYRAqo/AKDWRzZ9H9XmP7OwSU5RwLw2uVN8dwCfVYBT pVSa282J2+iDRvpvg1gZrLI= =y66f -----END PGP SIGNATURE-----

1 0

Kicking idle people who are not on a channel
by Jens Kleine 13 Aug '05

13 Aug '05

Hi, another quite unusual hack but maybe usefull for some of you: Adding these two lines to conn.c after line 1313: if(Channel_FirstChannelOf(c) == NULL && Conn_GetIdle(Client_Conn(c)) > 60) Conn_Close( i, NULL, "Not on a channel timeout", true ); will auto-close connections to people who hang around on your server but don't chat on any of the channels. (I just can't stand them) It gives them 60 seconds to join a channel or switch between them. Yours, Jens. -- Many an ancient lord's last words had been, 'You can't kill me because I've got magic aaargh.' (Terry Pratchett - Interesting Times)

2 3

rc.d start-up
by Adam McGreggor 13 Aug '05

13 Aug '05

Helo, I've recently installed ngirc on a FreeBSD install, using the ports collection. There's one thing that appears to be missing, and that's a shell script to start the daemon when the server's rebooted. I see in http://arthur.barton.de/pipermail/ngircd-ml/2005-January/000218.html that a ngircd.sh has been written, but can't see this - should it be there? I can't find much usefulness with a web-search, nor from /docs TIA, Adam

3 3

ngIRCd 0.9.1
by Alexander Barton 04 Aug '05

04 Aug '05

Hello All! Due to a severe bug in the handler for the IRC KILL command in ngIRCd 0.9.0, we are releasing version 0.9.1. ngIRCd 0.9.1 can be downloaded from the following places: <ftp://ftp.berlios.de/pub/ngircd/ngircd-0.9.1.tar.gz> <ftp://ngircd.barton.de/pub/ngircd/ngircd-0.9.1.tar.gz> And soon it should be available via HTTP from this site: <http://download.berlios.de/ngircd/ngircd-0.9.1.tar.gz> The GnuPG signature and a patch from 0.9.0 is available and can be downloaded from here: <ftp://ngircd.barton.de/pub/ngircd/> This release is tagged as "rel-0-9-1" in CVS. Changes since ngIRCd 0.9.0 are: - The KILL command killed much more than desired (including server links!) when the target user is connected to a remote server. Bug introduced in ngIRCd 0.9.0 ... Reported by <qssl(a)fastmail.fm>, Thanks! - Changed some constants to be "signed" (instead of unsigned) to solve problems with old (pre-ANSI) compilers. Regards Alex -- Alexander Barton, Freiburg, Germany http://www.barton.de/, alex(a)barton.de

1 0

Springe zur Seite:

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