From owner-freebsd-chat Thu Dec 20 6:27:57 2001 Delivered-To: freebsd-chat@freebsd.org Received: from aquinas.techsquare.com (aquinas.techsquare.com [199.190.186.200]) by hub.freebsd.org (Postfix) with ESMTP id 6451637B419 for ; Thu, 20 Dec 2001 06:27:54 -0800 (PST) Received: (from jamie@localhost) by aquinas.techsquare.com (8.11.6/8.11.3) id fBKERle26857; Thu, 20 Dec 2001 09:27:47 -0500 (EST) (envelope-from jamie) Date: Thu, 20 Dec 2001 09:27:47 -0500 From: Jamie Oulman To: "Brandon D. Valentine" Cc: chat@freebsd.org Subject: Re: Just lost one to Linux. Compaq server support. Message-ID: <20011220092747.A26807@techsquare.com> References: <20011220011035.A18793@techsquare.com> <20011220031755.O21508-100000@turtle.looksharp.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011220031755.O21508-100000@turtle.looksharp.net>; from bandix@looksharp.net on Thu, Dec 20, 2001 at 03:20:59AM -0500 Organization: TechSquare Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > your best to protect a system from /known/ vulnerabilities. There's no > telling who's out there reading source code and finding exploits without > reporting them. It's hopefully not a common scenario, but the > possibility exists. There's no way to say for certain that a given box > is uncrackable. I know this is not what you meant by your statement, > but the distinction is an important one to make IMO. yes. that is correct. there is the chance that the attacker-to-be has something that hasnt gone public yet. but in those kinds of situations. who is safe? -jfo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message