---- START NEW MESSAGE --- Received: from cherry.ease.lsoft.com [209.119.0.109] by dpmail10.doteasy.com with ESMTP (SMTPD32-8.05) id A6F329FB00FA; Wed, 28 Jan 2004 16:42:27 -0800 Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <19.00CC1AA5@cherry.ease.lsoft.com>; Wed, 28 Jan 2004 19:42:17 -0500 Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release 1.8e) with spool id 0902 for PICLIST@MITVMA.MIT.EDU; Wed, 28 Jan 2004 19:42:11 -0500 Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 0057; Wed, 28 Jan 2004 19:41:27 -0500 Received: from *unknown [210.8.51.66] by mitvma.mit.edu (IBM VM SMTP Level 430) via TCP with ESMTP ; Wed, 28 Jan 2004 19:41:26 EST X-Warning: mitvma.mit.edu: Host *unknown claimed to be whitlam.corp.gli.com.au Received: by whitlam.corp.gli.com.au with Internet Mail Service (5.5.2653.19) id <4T7L19NT>; Thu, 29 Jan 2004 11:44:12 +1100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Message-ID: <2193429B07D9914D97216EBBAA6AB8BD1A04DB@whitlam.corp.gli.com.au> Date: Thu, 29 Jan 2004 11:44:12 +1100 Reply-To: pic microcontroller discussion list Sender: pic microcontroller discussion list From: Liam O'Hagan Subject: Re: [PIC:] Disassemblers To: PICLIST@MITVMA.MIT.EDU Precedence: list X-RCPT-TO: Status: U X-UIDL: 371856177 yeah pretty much... The last issue like this I found end up costing the manufacturer approx $30 million, replacing hundreds of thousands of defective devices before someone exploited the fault. At the moment, this seems to be pretty localised, but we cannot be sure if this person has been doing this for years, but in small enough amounts that it would be written off as a counting error, but has recently got greedy and has taken enough to attract some attention. I have watched the security video of this person defrauding this device dozens of times, and plenty of other people have done the same, and we cannot see anything unusual. We've tried a variety of tests with static discharges up to 25kV, EMI, RF and magnetic interference and many more, but with no luck, very intruiging There has to be some method of triggering this extra code externally to the device, as it has functioned correctly for every other user... > -----Original Message----- > From: Jan-Erik Soderholm XA (TN/PAC) > [SMTP:jan-erik.xa.soderholm@ERICSSON.COM] > Sent: Thursday, January 29, 2004 11:20 AM > To: PICLIST@MITVMA.MIT.EDU > Subject: Re: [PIC:] Disassemblers > > Liam O'Hagan wrote : > > > Sorry to be so roundabout in my description, by necessity > > there are a lot of security concerns with an issue like this. > > > Hm, even *mentioning* it seems to be on the "security edge"... :-) > > Jan-Erik. > > -- > http://www.piclist.com hint: The list server can filter out subtopics > (like ads or off topics) for you. See http://www.piclist.com/#topics -- http://www.piclist.com hint: The list server can filter out subtopics (like ads or off topics) for you. See http://www.piclist.com/#topics .