ngIRCd Users April 2011

ngircd@lists.barton.de

3 Teilnehmer
2 Diskussionen

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

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 2011