[A83] Re: microcode

To: assembly-83@lists.ticalc.org
Subject: [A83] Re: microcode
From: james l <james@kirk.math.twsu.edu>
Date: Tue, 18 Sep 2001 16:04:39 -0500
In-Reply-To: <200109182051.f8IKp0124929@sunsparc.hysoft-automation.com>
References: <200109182051.f8IKp0124929@sunsparc.hysoft-automation.com>
Reply-To: assembly-83@lists.ticalc.org


Root/Great Overall Dictator replies:
> > >If I was to get a new computer, I would not want an updgradeable microcode
> > >CPU, because it is possible (unlikely but possible) that some hacker would
> > >give me an unsoliceted update. So far, I have got 3 viruses over cable in
> > >less than a month (my first month), and they are all internet worms, not
> > >trojans!
> > 
> > 
> > Updating microcode is probably a complex process, that cannot be easily 
> > done by software running on said processor.  The worst I've heard of is one 
> > that flashes your BIOS with garbage, then reboots.  The only way I can 
> > think of that a processor could contro lthe operation to recode itself 
> > wouldbe if there were two processors, and most people aren't that rich . . .
> 

See here  http://www.urbanmyth.org/microcode/ (no it isn't a joke) (my fault,
but it doesn't 'flash' the processor, so it has to be reloaded on each boot)

> 
> Not saying it does work like this, only that this could be an way to do such
> a thing.
> 
> 
> > OT: Firewalls are a good thing if you have cable.  I use one with dial-up 
> > so that apps don't keep wasting hours.
> OT Reply ;-)   :
> A bit of caution and a non-fancy email reader (one that doesn't open files and
> such for you, and displays the extension even if it is *.lnk or *.pif) can do some protection as well. 
>  
OT Reply to an OT Reply to an OT section: 
Especially with the new Microsoft worm/virus that spreads via email, popup
windows, unsecured servers (code red like).  Called Nimda

see semantac, slashdot, etc

James L

References:

[A83] Re: microcode

From: Peter-Martijn Kuipers <hyper@hysoft-automation.com>