ngIRCd Users April 2015

ngircd@lists.barton.de

6 Teilnehmer
7 Diskussionen

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

ngIRCd 22.1
by Alexander Barton 06 Apr '15

06 Apr '15

Hello World! ngIRCd 22 has been released on October 11 2014, and since then, a few "glitches" and bugs have been found. Therefore here it is: the next ngIRCd release named 22.1. The most severe bug was "WHO #channel" showing all invisible users and hiding all visible, the logic was reversed! This bug has been introduced back in August 2013 and affects ngIRCd releases 21, 21.1, and 22. Thanks a lot to "Cahata" for reporting this in #ngircd! And the most prominent change in ngIRCd 22.1 is that the default value of the "CipherList" configuration variable has been changed to not enable SSLv3 by default. Idea, initial patch, and testing by Christoph Biedl; Thanks a lot! (And please make sure to adjust this variable accordingly if you still have to support old and insecure(!) clients! You can check the current value using "ngircd --configtest" before upgrading. See "INSTALL" for details.) As usual, you can find the whole ChangeLog online on the ngIRCd homepage <http://ngircd.barton.de/doc/ChangeLog> and below: - Update doc/Platforms.txt and doc/FAQ.txt. - Fix spelling of RPL_WHOISBOT message text. - Don't send nick name as default PART reason: No other IRC daemon seems to do this (today?). Closes #185. Reported by Cahata in #ngircd, thanks! - Fix "WHO #<chan>" showing invisible users and hiding all visible, the logic was reversed! This bug has been introduced by commit c74115f2, "Simplify mode checking on channels and users within a channel", ngIRCd releases 21, 21.1, and 22 are affected :-( Problem reported by Cahata in #ngircd, Thanks! - Fix typo in src/testsuite/README - Auth PING: Fix our information text for manual sending of "PONG". Up to now, ngIRCd doesn't send a valid IRC command at all, oops! - Auth PING: Fix internal time stamp conversion and don't send a prefix in our PING command. The prefix confuses WeeChat, at least, which doesn't send an appropriate PONG in the case ... Debugging and patch by "wowaname" on #ngircd, thanks! - Fix syntax of ERR_LISTFULL_MSG(478) numeric. Pointed out by "wowaname" in #ngircd, thanks! - Enhance debug messages while sending CHANINFO commands. - Reset "last try" timer when enabling a passive server. This results in a new connection attempt as soon as possible. - Change log message for "Can't resolve address" and for IP address forgeries. - doc/HowToRelease.txt: Add note about the bug tracker. - Update "CipherList" to not enable SSLv3 by default. Idea, initial patch, and testing by Christoph Biedl <ngircd.anoy(a)manchmal.in-ulm.de>. - Change ngIRCd test suite not to use DNS lookups: Different operating systems do behave quite differently when doing DNS lookups, for example "127.0.0.1" sometimes resolves to "localhost" and sometimes to "localhost.localdomain" (for example OpenBSD). And other OS resolve "localhost" to the real host name (for example Cygwin). So not using DNS at all makes the test site much more portable. You can find more information on our homepage at <http://ngircd.barton.de/> and its mirror <http://ngircd.mirror.3rz.org/>. The primary download location is: • <http://ngircd.barton.de/pub/ngircd/> THANKS to all users, bug reporters, contributors, packagers, and supporters! Have fun! Alex

1 0

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 April 2015