From owner-freebsd-security Thu Dec 21 12: 4:54 2000 From owner-freebsd-security@FreeBSD.ORG Thu Dec 21 12:04:52 2000 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from ns.shawneelink.net (ns.shawneelink.net [216.240.66.11]) by hub.freebsd.org (Postfix) with ESMTP id 3A61337B400 for ; Thu, 21 Dec 2000 12:04:52 -0800 (PST) Received: from jan (gate14.shawneelink.net [216.240.79.14]) by ns.shawneelink.net (8.10.1/8.10.1) with ESMTP id eBLK4oO27685 for ; Thu, 21 Dec 2000 14:04:50 -0600 (CST) Message-Id: <4.2.2.20001221140608.00b8a2d0@mail.jbacher.com> X-Sender: jb@mail.jbacher.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 21 Dec 2000 14:14:39 -0600 To: security@FreeBSD.ORG From: J Bacher Subject: Re: dsniff 2.3 info: In-Reply-To: References: <4.2.2.20001221111451.00b6ef00@mail.jbacher.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 08:37 PM 12/21/00 +0100, you wrote: >J Bacher writes: > > > Which translates to "it's FreeBSD's fault". Send patches or shut up. > > So, are you in agreement that this is a FreeBSD issue? > >Not necessarily. I'm saying that what you write translates to laying >the blame at the FreeBSD project's feet. > > > If so, do you expect that anyone that reports a problem with an OS or > > application should also be the individual to provide patches? > >You're not "reporting a problem", you're saying that the problem being >discussed is caused by incompetence or sloppyiness on the part of the >members of the FreeBSD project. Hello? I have not reported a problem, filed a complaint, or engaged in any pissing and moaning. I'm looking for clarification as to your position regarding the disagreement you have with another individual. I saw that a problem was reported. I saw some recommended solutions. The solution that you are disagreement with doesn't resolve the entire issue but it certainly addresses one part of the problem. Is there any logical reason to not take that suggestion into consideration? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message