ngIRCd Users

ngircd@lists.barton.de

425 Diskussionen

ngIRCd Release 23
by Alexander Barton 16 Nov '15

16 Nov '15

Hi ngIRCd'ers! Our last "feature release" is over one year old, so the next release is quite overdue. But you can relax, here it is: ngIRCd Release 23! This release isn't the one with the most changes or the greatest new features in ngIRCd's history, but makes ngIRCd more compatible, more consistent, and adds some nice new functionality. Please see the ChangeLog for the whole story (online at <http://ngircd.barton.de/doc/ChangeLog> and included in the source distribution). The NEWS file lists the following new features since ngIRCd 22.1: • Use "NOTICE *" before registration instead of "NOTICE AUTH". "AUTH" is a valid nickname so sending notices to it is probably not a good idea. Use "*" as the target instead as done with numerics when the nick is not available. This mimics the behavior in Charybdis, IRCD-Hybrid, InspIRCd 2.2, Plexus 4, etc. Closes #217. The "NoticeAuth" configuration variable (ngircd.conf) has been renamed to "NoticeBeforeRegistration" accordingly, but the old name is still supported for compatibility reasons. • Implement new channel mode "N" (regular users can't change their nick name while on this channel). Closes #214. • Keep track of who placed bans, invites, and excepts. Idee and implementation by LucentW, Thanks! Closes #203. • Implement numeric RPL_LISTSTART(321). lightIRC and other clients expecting RPL_LISTSTART should now behave correctly. Idee and implementation by LucentW, Thanks! Closes #207. • Streamline the effect of "MorePrivacy" option: Update documentation in ngircd.conf(5); don't hide channels for IRC Ops on LIST and don't hide IP addresses/host names on WHOIS when "MorePrivacy" is in effect. This closes #198. • IRC operators now can kick anyone when "OperCanMode" is set. Idee and implementation by LucentW, Thanks! Closes #202. • Implement user mode "I": Hide channels on WHOIS: this mode prevents ngIRCd from showing channels on WHOIS (IRC Operators can always see the channel list). Idee and implementation by LucentW, Thanks! Closes #197. • INVITE command: Implement ERR_USERNOTONSERV(504) numeric and make sure that the target user is on the same server when inviting other users to local ("&") channels. Idea by Cahata, thanks! Closes #183. • MODE command: Always report channel creation time. Up to now when receiving a MODE command, ngIRCd only reported the channel creation time to clients that were members of the channel. This patch reports the channel creation time to all clients, regardless if they are joined to that channel or not. At least ircd-seven behaves like this. This closes #188. Reported by Cahata, thanks! You can find more information on our homepage at <http://ngircd.barton.de/> and its mirror <http://ngircd.mirror.3rz.org/>. The primary download locations are: • <http://ngircd.barton.de/pub/ngircd/> • <http://ngircd.mirror.3rz.org/pub/ngircd/> THANK YOU to all users, bug reporters, contributors, packagers, testers, and supporters: this release wouldn't have been possible without your work! Have fun! Alex

1 0

ask about ngircd
by Agung Kurniawan 02 Nov '15

02 Nov '15

hello i'm ubuntu newbie from indonesia, and i want ask how to configure transfer file / sending file on ngircd, im use ubuntu 12.04 for server and pidgin for client chat thankyou best regrads, agung Kurniawan

2 1

ngIRCd Release 23~rc1
by Alexander Barton 06 Sep '15

06 Sep '15

Hello all! Please give a warm welcome to ngIRCd Release 23~rc1, our just published first release candidate for the next "feature release" of ngIRCd, the lightweight and portable Internet Relay Chat server for small and private networks. There have been 56 commits since our last stable release, ngIRCd 22.1. The NEWS file lists these new features: • Use "NOTICE *" before registration instead of "NOTICE AUTH". "AUTH" is a valid nickname so sending notices to it is probably not a good idea. Use "*" as the target instead as done with numerics when the nick is not available. This mimics the behavior in Charybdis, IRCD-Hybrid, InspIRCd 2.2, Plexus 4, etc. Closes #217. The "NoticeAuth" configuration variable (ngircd.conf) has been renamed to "NoticeBeforeRegistration" accordingly, but the old name is still supported for compatibility reasons. • Implement new channel mode "N" (regular users can't change their nick name while on this channel). Closes #214. • Keep track of who placed bans, invites, and excepts. Idee and implementation by LucentW, Thanks! Closes #203. • Implement numeric RPL_LISTSTART(321). lightIRC and other clients expecting RPL_LISTSTART should now behave correctly. Idee and implementation by LucentW, Thanks! Closes #207. • Streamline the effect of "MorePrivacy" option: Update documentation in ngircd.conf(5); don't hide channels for IRC Ops on LIST and don't hide IP addresses/host names on WHOIS when "MorePrivacy" is in effect. This closes #198. • IRC operators now can kick anyone when "OperCanMode" is set. Idee and implementation by LucentW, Thanks! Closes #202. • Implement user mode "I": Hide channels on WHOIS: this mode prevents ngIRCd from showing channels on WHOIS (IRC Operators can always see the channel list). Idee and implementation by LucentW, Thanks! Closes #197. • INVITE command: Implement ERR_USERNOTONSERV(504) numeric and make sure that the target user is on the same server when inviting other users to local ("&") channels. Idea by Cahata, thanks! Closes #183. • MODE command: Always report channel creation time. Up to now when receiving a MODE command, ngIRCd only reported the channel creation time to clients that were members of the channel. This patch reports the channel creation time to all clients, regardless if they are joined to that channel or not. At least ircd-seven behaves like this. This closes #188. Reported by Cahata, thanks! Please test this release candidate thoroughly and report all glitches, 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.mirror.3rz.org/>. The primary download locations are: • <http://ngircd.barton.de/pub/ngircd/> • <http://ngircd.mirror.3rz.org/pub/ngircd/> And as usual: a big THANKS to all users, bug reporters, contributors, packagers, testers, and supporters: Your work is highly appreciated! Have fun! Alex

1 0

Reproducible builds
by Christoph Biedl 26 Aug '15

26 Aug '15

Hello, at the moment ngircd fails the tests for reproducible builds in Debian since it uses the __DATE__ and __TIME__ macros for the INFO command. Instead of patching this out I decided to implement an optional constant BIRTHTIME that allows you to set a time stamp for the "Birth Date" information, in seconds since the epoch, like in export CFLAGS += -DBIRTHTIME=$(shell date +%s --date="2015/08/15 23:42:22") In the future, Debian will provide a SOURCE_DATE_EPOCH environment variable, dealing with the situation until then will be my job. The time format was taken from the NGIRCd_StartStr formatting in ngircd.c so the "Birth Date" and "On-line since" lines in the INFO output look similar: :irc.example.net 371 nick :ngIRCd 22.1-IDENT+IPv6+IRCPLUS+PAM+SSL+SYSLOG+ZLIB-x86_64/pc/linux-gnu :irc.example.net 371 nick :Birth Date: Tue Aug 25 2015 at 18:11:11 (CEST) :irc.example.net 371 nick :On-line since Tue Aug 25 2015 at 18:11:33 (CEST) :irc.example.net 374 nick :End of INFO list The format of the time stamped is changed, but as far as I can tell, there's no rule that is violated by that. Bonus level: Reformat the messages so the time stamps are aligned. Christoph --- a/src/ngircd/irc-info.c +++ b/src/ngircd/irc-info.c @@ -556,7 +556,15 @@ NGIRCd_Version)) return DISCONNECTED; -#if defined(__DATE__) && defined(__TIME__) +#if defined(BIRTHDATE) + char t_str[60]; + time_t t = BIRTHDATE; + (void)strftime(t_str, sizeof(t_str), "%a %b %d %Y at %H:%M:%S (%Z)", + localtime(&t)); + snprintf(msg, sizeof(msg), "Birth Date: %s", t_str); + if (!IRC_WriteStrClient(Client, RPL_INFO_MSG, Client_ID(prefix), msg)) + return DISCONNECTED; +#elif defined(__DATE__) && defined(__TIME__) snprintf(msg, sizeof(msg), "Birth Date: %s at %s", __DATE__, __TIME__); if (!IRC_WriteStrClient(Client, RPL_INFO_MSG, Client_ID(prefix), msg)) return DISCONNECTED;

2 1

Re: [ngIRCd-ML] questions about the chat log history
by Arno Duwel 29 Apr '15

29 Apr '15

> Hello.I'm choi. > I have a some question. > I want to save client's chat log history together in one of the server. > Is it possible. Hello choi! I am new to this mailing list (hello all, hello Arthur Barton … thank you for your wonderful server! :) ) – but I would like to reply to your message: As far as I understand it: IRC servers are not really meant to log messages that users are sending. You could probably find similar questions already if you google them. It's probably not uncommon to ask this. While I think that it is great that IRC servers respect the privacy of their users – it is likely that there are personal or special conditions where it is wanted to log conversations of course! The best way to do this is to log in as a user. Most clients save the logfiles. And you just need to log into your ngircd-server as a user and join the channel you would like to log. If you do not want to start a full desktop-irc-client you could be interested in using a bot for something like this. There are hundreds of little helper-programs out there - and I have currently only used supybot so far (more current: limnoria) which runs well with ngircd. The bot logs in as a user – and you can configure such a bot to log everything that is said - or just special times for example. And a bot may help you in lots of other cases as well. I believe that there will be dozens of different solutions for your problem – but the server itself will not log everything. You will want some kind of logged-in user/bot for this. I hope this helps. Good luck to you!

1 0

questions about the chat log history
by yoonsung choi 29 Apr '15

29 Apr '15

Hello.I'm choi. I have a some question. I want to save client's chat log history together in one of the server. Is it possible. I will wait for the reply . Thank you .

1 0

questions about the ngIRC
by yoonsung choi 29 Apr '15

29 Apr '15

My name is Choi . I want to save the contents of the chat , name , time as all log Is this possible? I want you to tell me if possible way. Thank you .

1 0

operator command
by Daiki Akiyoshi 21 Apr '15

21 Apr '15

I am a student worker at a college and learning how to set up ngircd. I have a trouble to log on as IRC operator. I configured an [Oper] section on config file. After I use /OPER command to be an IRC operator, log file says: "Got valid OPER for "Name" from "Nickname!~Name@com", user is an IRC operator now. However, when I use commands such as kick, it says "your privileges are too low". Does anyone have any idea how to fix this? I really appreciate your help. Warmly, Daiki Akiyoshi Earlham College'18

2 2

Compilation results ngIRCd 22.1 with tcc, Open64 5.0, SolarisStudio 12.3
by Götz Hoffart 13 Apr '15

13 Apr '15

ngIRCd 22.1 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 22.1 15-04-13 goetz Y Y N Y 1 ============================================================================== ngIRCd 22.1 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 […] opencc WARNING: unknown flag: -fstack-protector opencc WARNING: unknown flag: -fstack-protector opencc WARNING: unknown flag: -fstack-protector opencc WARNING: unknown flag: -fstack-protector opencc WARNING: unknown flag: -fstack-protector opencc WARNING: unknown flag: -fstack-protector opencc WARNING: unknown flag: -fstack-protector opencc WARNING: unknown flag: -fstack-protector opencc WARNING: unknown flag: -fstack-protector opencc WARNING: unknown flag: -fstack-protector "io.c", line 409: Warning: Variable __d0 in fucntion io_library_init_select might be used uninitialized "io.c", line 409: Warning: Variable __d1 in fucntion io_library_init_select might be used uninitialized "io.c", line 410: Warning: Variable __d0 in fucntion io_library_init_select might be used uninitialized "io.c", line 410: Warning: Variable __d1 in fucntion io_library_init_select might be used uninitialized "io.c", line 671: Warning: Variable __d0 in fucntion io_library_shutdown might be used uninitialized "io.c", line 671: Warning: Variable __d1 in fucntion io_library_shutdown might be used uninitialized "io.c", line 672: Warning: Variable __d0 in fucntion io_library_shutdown might be used uninitialized "io.c", line 672: Warning: Variable __d1 in fucntion io_library_shutdown might be used uninitialized opencc WARNING: unknown flag: -fstack-protector opencc WARNING: unknown flag: -fstack-protector opencc WARNING: unknown flag: -fstack-protector […] 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 22.1 15-04-13 goetz Y Y Y Y 1 ============================================================================== ngIRCd 22.1 has been configured with the following options: Host: x86_64-unknown-linux-gnu Compiler: /opt/solarisstudio12.3/bin/suncc 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 […] platformtest.sh: Running "make" ... "io.c", line 791: warning: statement not reached "io.c", line 887: warning: statement not reached "io.c", line 910: warning: statement not reached 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 * --------------------------- ------------ ---------- -------- -------- - - - - - x86_64/unknown/linux-gnu unknown 22.1 15-04-13 goetz Y Y Y Y 1 Grüße Götz -- ③rz :: Regionales Retro-Rechenzentrum, Freiburg :: http://www.3rz.org Für Freunde außer-gewöhnlicher Datenverarbeitung

1 0

ngIRCd Git Repository & Bug Tracker moving to GitHub
by Alexander Barton 07 Apr '15

07 Apr '15

Hi ngIRCd'ers! After becoming more and more dissatisfied with Bugzilla, and without Debian supporting it any more in their current releases, I decided to no longer use my own Bugzilla installation but to move the main ngIRCd Git Repository to GitHub and to use their issue tracker. I created a new "GitHub organization", which you can find here: <https://github.com/ngircd/> There you'll find our two sub-projects, the daemon itself and our website: • <https://github.com/ngircd/ngircd> • <https://github.com/ngircd/ngircd-web> All old bug reports have been migrated to GitHub, and HTTP redirects are in place, so that you should reach suitable pages even when using old URLs pointing to the now uninstalled Bugzilla installation. The migration of the existing bug reports has a few drawbacks: • You must re-subscribe to all bugs that you are interested in, • all GitHub issues are created by "alexbarton" (me), the real author information can only be seen in the description text, • and all issues creation dates are "now", the real dates can be seen in the description as well. • All attachments are … gone. If someone cares I can try to make them available somewhere (yes, I do have backups!). All the currently open bugs didn't have any attachments. While migration the bug/issue tracker to GitHub, I'm going to use the GitHub repository as the new "master repository" in the future, too. Up to now, I always used my own repository on <git://ngircd.barton.de/ngircd.git> and mirrored it periodically to GitHub. From now on, I will push all commits directly to GitHub – and mirror it back to my own repository. So basically you don't have to change anything in your setup (I hope!). The new Git repository URLs are: • <https://github.com/ngircd/ngircd.git> • <https://github.com/ngircd/ngircd-web.git> So what should you do? – Nothing. Keep smiling! ;-) Everything should work as before, and … • if you were using the bug tracker, have a look at the GitHub issues and (re-)subscribe to all issues that you are interested in; • if you are using Git, update your remotes to point to the new addresses as stated above. Please let me know when you encounter any broken links or other problems! I'm going to update the documentation included in the source tree (README, doc/GIT.txt, etc.) in the next few days … Thanks! Alex

1 0

← Neuer
1
2
3
4
5
6
7
8
9
...
43
Älter →

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