From owner-freebsd-security Sun Nov 1 16:11:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02728 for freebsd-security-outgoing; Sun, 1 Nov 1998 16:11:13 -0800 (PST) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02709 for ; Sun, 1 Nov 1998 16:11:08 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id TAA14541; Sun, 1 Nov 1998 19:11:02 -0500 (EST) Date: Sun, 1 Nov 1998 19:11:00 -0500 (EST) From: "Matthew N. Dodd" To: "Jordan K. Hubbard" cc: freebsd-security@FreeBSD.ORG Subject: Re: SSH vsprintf patch. (You've been warned Mr. Glass) In-Reply-To: <21498.909965295@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 1 Nov 1998, Jordan K. Hubbard wrote: > I read that too, yeah. Basically, I've seen evidence of provable > buffer overflows (but not proven exploitability of same) and I've seen > a hacked site who admins can't think of many other ways to be hacked > and are pointing either correctly or incorrectly at ssh as the cause > in their first round of theories. Either way, it's just all too > guessy for me right now - I'd sure like to see an actual exploit here > before declaring this most security scare concluded. :( Indeed. I attempted to keep my original message fairly neutral for that reason. At this point there isn't any reason not to go about fixing these potential problems though. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message