From: Christian Wettergren <cwe@it.kth.se>
To: tcmay@got.net (Timothy C. May)
Message Hash: c94b31c66fdb0906613628c55714af216e4b2e2361b17c07d3fc81a79c815a24
Message ID: <199606190641.IAA10766@piraya.electrum.kth.se>
Reply To: <adeb915b01021004b1a6@[205.199.118.202]>
UTC Datetime: 1996-06-19 11:35:40 UTC
Raw Date: Wed, 19 Jun 1996 19:35:40 +0800
From: Christian Wettergren <cwe@it.kth.se>
Date: Wed, 19 Jun 1996 19:35:40 +0800
To: tcmay@got.net (Timothy C. May)
Subject: Re: Fuseable Links - no guarantees??
In-Reply-To: <adeb915b01021004b1a6@[205.199.118.202]>
Message-ID: <199606190641.IAA10766@piraya.electrum.kth.se>
MIME-Version: 1.0
Content-Type: text/plain
| >I recently saw an add for a UK based group that says they can take a PIC
| >OTP micro and read the prom (for a fee, of course) - How the heck is this
| >done??
According to the FAQ for satellite piracy, whatever that is called, it is
quite simple for some models of PICs.
Many of the OTP PICs have a wipe mode for reusal. Apply a certain voltage,
the programming voltage, and the memory is wiped and a fuse is restored so
the memory is programmable again.
Approx a year ago some people on this scene discovered that one could restore
the fuse without erasing the memory content. They applied the programming
voltage minus 0.5V (or something similar). The idea is that there is a voltage
drop across the fuse, and this modified voltage level just barely "manages
it" across the fuse. The voltage level is however not enough to spark the
memory erasure mechanism off.
So I guess one can look at the circuitry and apply non-standard voltage and
current values, or even non-standard timing values -- and do bad things
to these circuits. So this begs the question: Is there anyone who has looked
at "computer security" issues at this level? Is this just bad implementations
of these circuits or are there a fundamentally hard problem in this?
(I'd guess you'll find the FAQ if you search for the words "satellite piracy
PIC OTP" on Alta Vista.)
-Christian
Return to June 1996
Return to “tcmay@got.net (Timothy C. May)”