ngIRCd Users

ngircd@lists.barton.de

1 Teilnehmer
425 Diskussionen

Re: [ngIRCd-ML] IRC Services (rfc1459) broken on latest git?
by Alexander Barton 12 Mai '11

12 Mai '11

Hello! Am 29.04.2011 um 16:25 schrieb shinji(a)elite-systems.org: > Since you had to relax for rfc1459 and the logs are indicating "rfc1459 compatibility mode" does this mean you are working to support more services protocols? Current development version of ngIRCd has support for the current development branch (1.9) of Anope. However ngIRCd is a „second class citizen“ in Anope world: the protocol module most probably will be moved out of the regular source tree into an „extra“ branch or something like that, because of too little „relevance“. But as of today, the protocol module still lives in modules/protocol/ngircd.cpp (Anope 1.9, current GIT). If you are interested in Anope supporting ngircd, please test current ngIRCd and current Anope versions, and report back to Anope, for example in #anope-devel on irc.teranova.net :-) Regards Alex PS.: please try to „replay to all“ and keep the list in CC:!

2 1

IRC Services (rfc1459) broken on latest git?
by Robert Pendell 29 Apr '11

29 Apr '11

IRC Services support seems to be broken on the latest git. I guess it doesn't help that I'm using a discontinued IRC services application but since it does provide what is needed I've gotten used to using it anyways. On the most recent git (compiled into deb packages) rfc1459 support seems to break. I get the following in my syslog with ircservices attempts to connect. Apr 29 02:48:03 icarus ngircd[1801]: Accepted connection 12 from 127.0.0.1:42754 on socket 9. Apr 29 02:48:03 icarus ngircd[1801]: IDENT lookup for connection 12: no result. Apr 29 02:48:03 icarus ngircd[1801]: Switching connection 12 (" services.example.com") to RFC 1459 compatibility mode. Apr 29 02:48:03 icarus ngircd[1801]: Attention: this server uses a non-standard nick length, but the peer doesn't support the IRC+ extended server handshake! Apr 29 02:48:03 icarus ngircd[1801]: Server "services.example.com" registered (connection 12, 1 hop - direct link). Apr 29 02:48:03 icarus ngircd[1801]: Received command without prefix (connection 12, command "NICK")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "OperServ", client not known (connection 12, command "USER")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "OperServ", client not known (connection 12, command "MODE")!? Apr 29 02:48:03 icarus ngircd[1801]: Received command without prefix (connection 12, command "NICK")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "Global", client not known (connection 12, command "USER")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "Global", client not known (connection 12, command "MODE")!? Apr 29 02:48:03 icarus ngircd[1801]: Received command without prefix (connection 12, command "NICK")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "NickServ", client not known (connection 12, command "USER")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "NickServ", client not known (connection 12, command "MODE")!? Apr 29 02:48:03 icarus ngircd[1801]: Received command without prefix (connection 12, command "NICK")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "ChanServ", client not known (connection 12, command "USER")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "ChanServ", client not known (connection 12, command "MODE")!? Apr 29 02:48:03 icarus ngircd[1801]: Received command without prefix (connection 12, command "NICK")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "MemoServ", client not known (connection 12, command "USER")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "MemoServ", client not known (connection 12, command "MODE")!? Apr 29 02:48:03 icarus ngircd[1801]: Received command without prefix (connection 12, command "NICK")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "StatServ", client not known (connection 12, command "USER")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "StatServ", client not known (connection 12, command "MODE")!? Apr 29 02:48:03 icarus ngircd[1801]: Received command without prefix (connection 12, command "NICK")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "HelpServ", client not known (connection 12, command "USER")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "HelpServ", client not known (connection 12, command "MODE")!? Apr 29 02:48:03 icarus ngircd[1801]: Invalid prefix "OperServ", client not known (connection 12, command "WALLOPS")!? Just a thought but the buffering may be a bit off on this. It seems the commands from ircservices are not being properly interpreted somewhere. The last built I had that did work correctly. That one had a version string of ngircd-17.1~55-g5417a72 being it was from the git rep when I did it. The one I did just now was done today and I got all those errors above. The debug build doesn't provide any additional information otherwise I would provide that as well. If there is anything you can advise then I'm open for it. Robert Pendell shinji(a)elite-systems.org CAcert Assurer "A perfect world is one of chaos."

3 4

Buffer overflow on user connection
by Terry Baume 28 Apr '11

28 Apr '11

Hello, I am having some trouble with some users connecting to my ngIRCd server - this only seems to affect some users. Here's an extract from my log: > Apr 28 10:46:39 jupiter ngircd[1600]: Accepted connection 13 from > 58.160.178.xxx:54009 on socket 10. > Apr 28 10:46:39 jupiter ngircd[14258]: Can't resolve > "CPE-58-160-178-xxx.hbqy1.fli.bigpond.net.au": Name or service not known > Apr 28 10:46:39 jupiter ngircd[14258]: Possible forgery: > 58.160.178.xxxresolved to CPE-58-160-178-xxx.hbqy1.fli.bigpond.net.au > (which has no ip address) > Apr 28 10:46:39 jupiter ngircd[1600]: New TLSv1 connection using > cipher AES128-SHA on socket 13. > Apr 28 10:46:39 jupiter ngircd[1600]: User "Skiitz!~.(a)58.160.178.xxx" > registered (connection 13). > Apr 28 10:46:39 jupiter ngircd[1600]: Write buffer overflow > (connection 13, size 4036 byte)! > Apr 28 10:46:39 jupiter ngircd[1600]: Shutting down connection 13 > (Write buffer overflow!) with 58.160.178.xxx:54009 ... > Apr 28 10:46:39 jupiter ngircd[1600]: SSL connection 13 shutting down ... > Apr 28 10:46:39 jupiter ngircd[1600]: User "Skiitz!~.(a)58.160.178.xxx" > unregistered (connection 13): Write buffer overflow! > Apr 28 10:46:39 jupiter ngircd[1600]: Connection 13 with > 58.160.178.xxx:54009 closed (in: 0.0k, out: 11.9k). My interpretation of the log is that the client is exceeding ngIRCd's buffer size - can this parameter be tuned, or is this a misbehaving (outside of RFC) client? Terry.

2 3

re; PredefChannelsOnly = yes
by Rich Griese 16 Mär '11

16 Mär '11

Hey there, Thanks for the; PredefChannelsOnly = yes advice. I tried putting it in the global and then the channel section, and it is not doing the job I put it in my /usr/local/etc/ngircd.conf and then stopped and started the ngirdc is there a trick I am missing? Cheers! RichGriese(a)gmail.com

4 8

replay recent messages on joining persistent chatroom
by Brendan Miller 16 Mär '11

16 Mär '11

For some jabber based chatrooms, there seems to be a way to make the server play back recent messages on joining, so that you can see what the conversation was about before you joined. Is there a setting to make ngircd do this?

2 1

can't connect from other than localhost
by Brendan Miller 02 Mär '11

02 Mär '11

I just installed ngirc for the first time. Currently, I can connect to ngirc from localhost; however, from other machines I cannot connect. It tried troubleshooting with netcat and wireshark a bit. When I connect with netcat to port 6667 from another machine, my connection ins't refused, but I don't seem to be getting any kind of response back from the server either. Not even an ACK. Any suggestions? I'm wondering if there's some switch I have to flip to get it to talk to something other than localhost. Thanks

2 1

Forcing SSL only listeners
by Darren Spruell 28 Feb '11

28 Feb '11

I have a use case for an ircd that provides SSL/TLS only service. ngIRCd looks like it will support both SSL and non-SSL encrypted services through the use of 'Ports' and 'SSLPorts' configuration options. I can use iptables to block connections to the vanilla IRC service port but it seems an option to force SSL/TLS only (or disable non-SSL service) would be more elegant. Has this scenario been discussed before? Shall I add a bugtraq entry for a feature request to support this capability? Thx, -- Darren Spruell phatbuckett(a)gmail.com

1 1

Default Client/Channel Modes
by Jerome Rose 25 Feb '11

25 Feb '11

Is there an way to set the default mode for new clients and/or channels? Thanks, Jerome

4 4

gnutls_handshake: Could not negotiate a supported cipher suite.
by Georges POLITIS 06 Jan '11

06 Jan '11

Hi, I am tried to setup an SSL protected irc server using ngIRCd and I epicly failed. Here's my ngircd.conf: [Global] SSLPorts = 17667 SSLKeyFile = /etc/ngircd/ngircd-key.pem SSLCertFile = /etc/ngircd/ngircd-cert.pem SSLDHFile = /etc/ngircd/ngircd-params.pem Name = irc.debian.org Info = Yet another IRC Server running on Debian GNU/Linux AdminInfo1 = Debian User AdminInfo2 = Debian City AdminEMail = root@localhost MotdFile = /etc/ngircd/ngircd.motd PidFile = /var/run/ngircd/ngircd.pid PingTimeout = 120 PongTimeout = 20 ConnectRetry = 60 OperCanUseMode = yes MaxConnections = 500 MaxConnectionsIP = 10 MaxJoins = 10 The problem is that SSL initialisation fails. Here's the relevant /var/log/syslog output: Jan 5 21:31:12 chronos ngircd[12609]: ngircd 15-SYSLOG+ZLIB+SSL+IRCPLUS+IPv6-i486/pc/linux-gnu started. Jan 5 21:31:12 chronos ngircd[12609]: Reading configuration from "/etc/ngircd/ngircd.conf" ... Jan 5 21:31:12 chronos ngircd[12609]: gnutls_certificate_set_x509_key_file (cert /etc/ngircd/ngircd-cert.pem, key /etc/ngircd/ngircd-key.pem): Base64 decoding error. Jan 5 21:31:12 chronos ngircd[12609]: Warning: Error during SSL initialization, continuing ... Jan 5 21:31:12 chronos ngircd[12609]: ServerUID must not be 0, using "nobody" instead. Jan 5 21:31:12 chronos ngircd[12609]: Can't change group ID to 65534: Operation not permitted Jan 5 21:31:12 chronos ngircd[12609]: Can't change user ID to 65534: Operation not permitted Jan 5 21:31:12 chronos ngircd[12610]: Running as user irc(39), group irc(39), with PID 12610. Jan 5 21:31:12 chronos ngircd[12610]: Not running with changed root directory. Jan 5 21:31:12 chronos ngircd[12610]: Notice: Can't change working directory to "/var/run/ircd": No such file or directory Jan 5 21:31:12 chronos ngircd[12610]: IO subsystem: poll (initial maxfd 100). Jan 5 21:31:12 chronos ngircd[12610]: Now listening on [0::]:17667 (socket 5). Jan 5 21:31:12 chronos ngircd[12610]: Now listening on [0.0.0.0]:17667 (socket 6). I doubt it is a permissions problem. Here's the /etc/ngircd directory listing: gp@chronos:/etc/ssl$ sudo ls -l /etc/ngircd/ total 20 -rwxrwxrwx 1 irc irc 0 2011-01-05 21:21 ngircd-cert.pem -rw-r--r-- 1 irc irc 4839 2011-01-05 21:29 ngircd.conf -rwxrwxrwx 1 irc irc 1238 2011-01-05 21:25 ngircd-dhparams.pem -rwxrwxrwx 1 irc irc 1675 2011-01-05 21:21 ngircd-key.pem -rw-r--r-- 1 irc irc 255 2010-05-11 19:16 ngircd.motd gp@chronos:/etc/ssl$ I've read the SSL guide (found here http://ngircd.barton.de/doc/SSL.txt) and it lists 2 methods for creating the SSL certificate/private key. I've used both without success. Does anyone have any ideas? Thank you in advance. Georges

3 2

ngIRCd 17.1
by Alexander Barton 19 Dez '10

19 Dez '10

Hi All! Not that long ago, ngIRCd 17 has been released. Sadly a few bugs have slipped in, which have been fixed in this new release: 17.1. – in addition a few minor new features have been implemented which are also part of this release. The changes since release 17 are: * --configtest: remember if MOTD is configured by file or phrase * Enhance log messages when establishing server links a little bit * Reset ID of outgoing server link on DNS error correctly * Don't log critical (or worse) messages to stderr * Manual page ngircd(8): add SIGNALS section * Manual pages: update and simplyfy AUTHORS section * Remove "error file" when compiled with debug code enabled * README: Updated list of implemented commands * add doc/README-Interix.txt and doc/Bopm.txt to distribution tarball * add doc/PAM.txt to distribution tarball * New numeric 329: get channel creation time on "MODE #chan" commands * Save channel creation time; new function Channel_CreationTime() The most important fix is "Reset ID of outgoing server link on DNS error correctly“: this could result in ngircd never trying to re-connect to a particular server when a DNS error occurred and to a permanently split network :-/ The new release can be downloaded here: * <ftp://ftp.berlios.de/pub/ngircd/ngircd-17.1.tar.gz> * <ftp://ngircd.barton.de/pub/ngircd/ngircd-17.1.tar.gz> GnuPG signatures for release 17.1, a Mac OS X package, patches from release 17 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. Have fun! Regards Alex

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