From owner-freebsd-hackers Sat Nov 8 21:07:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA14278 for hackers-outgoing; Sat, 8 Nov 1997 21:07:47 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from srv.net (snake.srv.net [199.104.81.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA14269 for ; Sat, 8 Nov 1997 21:07:43 -0800 (PST) (envelope-from cmott@srv.net) Received: from darkstar.home (tc-if2-29.ida.net [208.141.171.86]) by srv.net (8.8.7/8.8.5) with SMTP id WAA06579; Sat, 8 Nov 1997 22:07:33 -0700 (MST) Date: Sat, 8 Nov 1997 22:06:59 -0700 (MST) From: Charles Mott X-Sender: cmott@darkstar.home To: Howard Lew cc: Tony Kimball , hackers@FreeBSD.ORG Subject: Re: Newest Pentium bug (fatal) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 8 Nov 1997, Howard Lew wrote: > > For Windows users this bug should not be much of a problem unless viruses > start popping up taking advantage of the bug. For FreeBSD it is not very > comforting to know that any misbehaving user can lock up your shell > machine, but in a controlled environment this should not be a problem. > Possibly also systems where users are allowed to put executable CGI-invoked code on their web pages (although usually such users also have shell accounts). This could be bad for Intel. I think that there is a limited subset of Pentium owners which now have a *very* strong incentive to obtain replacement chips or go to alternate vendors (AMD or IDT). -- Charles Mott P.S. Have any FreeBSD users tried out the new IDT chip?