From: Greg Hoglund (hoglundhbgary.com)
Date: Wed Jul 06 2005 - 13:29:46 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

>> infecting hardware (or, more to the point flashable firmware type
>> stuff) such that malicious code could survive warm reboots, cold
...
>
>
>The firmware burnout idea is one that I had at Cenzic, applied to doing a
>million+ writes to a motherboard's flash BIOS to require physical
>replacement of the motherboard. I think it made it into Greg's book. The

<-- snip

Ahem... It made it into my book after I obtained the idea for firmware
burnout directly from a robot enthusiast who has built a competition
battle-bot. In one of his first prototypes he made the mistake of using
serial EEPROM for a RAM capability. Because RAM is used readily, it caused
the burnout of the EEPROM after about an hour of use, after which the
enthusiast then calculated the approximate number of write operations to
kill the EEPROM at about 1 million. He posted as much on a website devoted
to battle-bots. The rest of devious thinking was a direct result of that seed.

-Greg

_______________________________________________
Dailydave mailing list
Dailydavelists.immunitysec.com
https://lists.immunitysec.com/mailman/listinfo/dailydave

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]