Subject: pkg/19612: chat/xchat doesn't handle DCC requests correctly
To: None <firstname.lastname@example.org>
From: None <email@example.com>
Date: 12/30/2002 20:36:51
>Synopsis: chat/xchat doesn't handle DCC requests correctly
>Arrival-Date: Mon Dec 30 11:37:00 PST 2002
>Release: NetBSD 1.6K
System: NetBSD lucifer.ipv6.stack.nl 1.6K NetBSD 1.6K (GENERIC) #1: Sat Dec 14 19:29:54 CET 2002 firstname.lastname@example.org:/sys/arch/i386/compile/GENERIC i386
xchat doesn't correctly handle DCC requests; part of the message
seems to get lost somewhere. As an example, I did a DCC CHAT to
myself, on another host, while tcpdump'ing the traffic from- and to
the ircserver. For the record, xchat is configured to use ports
7000 to 7005 for DCC purposes, but I don't think this is in any
way of importance.
Xchat's own "raw log" thinks it transmitted the following
<< PRIVMSG pienjo :^ADCC CHAT chat 1052978052 7000^A^M
<< PING LAG3566191913^M
The "other side" got the following request:
*** DCC CHAT (chat) request received from Pienj_o [188.8.131.52:62521]
The nick is correct. The IP number is correct. The port number
most definately isn't.
A tcpdump from exactly that section reads:
19:44:55.717950 lucifer.inet.65481 > sun4irc.sci.kun.nl.ircd: P 330639234:330639283(49) ack 1737124311 win 17520 <nop,nop,timestamp 371 95659854> (DF)
...s...NPRIVMSG pienjo :.DCC CHAT chat
19:44:57.828799 lucifer.inet.65481 > sun4irc.sci.kun.nl.ircd: P 49:69(20) ack 1 win 17520 <nop,nop,timestamp 375 95659854> (DF)
It seems quite obvious that the second part of the chat message is
The odd thing is that this problem only seems to exist for NetBSD.
The same version of xchat running on FreeBSD doesn't have this
problem, and the FreeBSD ports package doesn't use any relevant
patches. Xchat is working perfectly otherwise.
Try to offer a DCC chat (or send a file using DCC) to somebody else,
and watch their screen ;)
Unknown. Looking at it.