From owner-freebsd-security Thu Jan 20 12:40: 4 2000 Delivered-To: freebsd-security@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id 73F13152D3; Thu, 20 Jan 2000 12:39:56 -0800 (PST) (envelope-from mike@sentex.net) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id PAA32223; Thu, 20 Jan 2000 15:39:54 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <3.0.5.32.20000120153724.0206a850@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Thu, 20 Jan 2000 15:37:24 -0500 To: Tom From: Mike Tancsa Subject: Re: bugtraq posts: stream.c - new FreeBSD exploit? Cc: freebsd-security@freebsd.org, freebsd-stable@freebsd.org, security-officer@freebsd.org In-Reply-To: References: <3.0.5.32.20000120152818.01d7fa40@staff.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 12:34 PM 1/20/00 -0800, Tom wrote: > Uhh.. there isn't enough information here to determine anything. That was only a snippet. The poster claims to have contacted the freebsd team and that they were working on it... I just wanted to know if this were the case. Another snippet of the post below. I didnt want to blurt the whole bugtraq posting, as I suspect most people are already subscribed to it. >One thing of note: he also stated this happened on non-freebsd systems, >which is contrary to what the other person said, who was "under the >impression it was freebsd specific." > >I have the source, which I'm not going to post for 2-3 days (give time for >fbsd to work on the fix). If it isn't out before the 21st, I'll post it up. > > ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message