Re: Securing code in embedded devices
From: Chris Hills (chris_at_phaedsys.org)
Date: 02/14/05
- Next message: Wim Ton: "Re: Securing code in embedded devices"
- Previous message: Bruce Barnett: "Securing code in embedded devices"
- In reply to: Bruce Barnett: "Securing code in embedded devices"
- Next in thread: Wim Ton: "Re: Securing code in embedded devices"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 14 Feb 2005 17:18:27 +0000
In article <cuqlu4$p0o$0$208.20.133.66@netheaven.com>, Bruce Barnett
<spamhater113+U050214113747@grymoire.com> writes
>
>Some people have asked me for help in securing their application code
>in embedded devices from the threat of reverse engineering. I was
>looking for some papers/sites that discuss approaches, good and bad,
>to address this issue.
>
>This system is attached to a network, so it can get encrypted data
>over a wire.
>
>They are interested in options other than using a secure
>microprocessor with password protected memory. I'm not sure what the
>issues are.
>
>I'm still gathering requirements, but perhaps someone can point me to
>commercial solutions, web pages, hack sites, lessons learned,
>do's and don'ts, etc.
>
>Thanks
>
>I realize that any system can be defeated, especially if you have
>physical access. Some are harder to defeat than others.
>SRAM vs. FLASH memory for instance.
Use a single chip MCU system with lock bits. Many MCU have them.
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
\/\/\/\/\ Chris Hills Staffs England /\/\/\/\/\
/\/\/ chris@phaedsys.org www.phaedsys.org \/\/
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
- Next message: Wim Ton: "Re: Securing code in embedded devices"
- Previous message: Bruce Barnett: "Securing code in embedded devices"
- In reply to: Bruce Barnett: "Securing code in embedded devices"
- Next in thread: Wim Ton: "Re: Securing code in embedded devices"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
