From owner-freebsd-bugs Wed Mar 10 15:30:18 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 3D7D514E3E for ; Wed, 10 Mar 1999 15:30:17 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.2/8.9.2) id PAA99092; Wed, 10 Mar 1999 15:30:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Wed, 10 Mar 1999 15:30:03 -0800 (PST) Message-Id: <199903102330.PAA99092@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Joel Ray Holveck Subject: Re: bin/7669: libalias does not IRC DCC packets under certain conditions Reply-To: Joel Ray Holveck Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/7669; it has been noted by GNATS. From: Joel Ray Holveck To: Eivind Eklund Cc: Brian Somers , FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: bin/7669: libalias does not IRC DCC packets under certain conditions Date: 10 Mar 1999 17:21:27 -0600 >> Any chance of you two reviewing this change to close 7669 ? If it >> doesn't work in all situations I'll add an option - but then again, >> it may not work at all :-) > This change does not work in all situations. The correct way to > handle it would be to have libalias trap the protocol mIRC use to > query the IRC server. > If anybody know where I could get information on what the protocol > does, I can try to see if there is some easy way to put a handler for > it into libalias - I suspect it could be slightly problematic, due to > needing to track the extra information on a per-stream basis. It > would probably be a good addition to the libalias infrastructure, > though. I have a test environment availible that can be used to read the TCP transaction. (This is the same environment where I originally found the problem) You want it? Cheers, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message