Code copy protection
Posted 18 June 2011 - 11:49 AM
- shockckcHok likes this
Posted 18 June 2011 - 05:52 PM
Posted 09 July 2011 - 04:38 PM
Posted 09 July 2011 - 07:34 PM
You can lock down TinyBooter so that it will only flash and run firmware signed by your private key. [Actually, you can have two keys--if you want one for the .NET MF runtime and one for your application.]
Based on what you wrote above, are you saying that you can put a hook in the firmware, make it so that only your firmware loads to the device, and then write code that looks at the firmware hook and then loads (or operates) or not depending on finding the hook?
Inside your code, you can do any type of authentication you'd like as well.
There are some ways to keep folks from pulling your firmware off the chip as well. Although anyone with a really expensive microscrope and lots of time on their hands...
Posted 30 June 2017 - 01:45 PM
Hi jinlye, First: Christoc...yes, you can use Dotfuscator. You'll need the non-Express version of Visual Studio for that, I believe. Second: You can actually build the Netduino firmware as "RTM" which will lock out the debugger--and you can add digital kits to the firmware which lock down your unit. You could even lock the flash on the MCU after flashing it. More details are available in the "\MicroFrameworkPK_v4_1\Documentation\" folder and in the microcontroller datasheet. Lots of options. .NET MF is great for open source electronics boards, but it also has these types of options for commercial products which want to be locked down. Chris
can you explain me with sample this:
"You can actually build the Netduino firmware as "RTM" which will lock out the debugger--and you can add digital kits to the firmware which lock down your unit."
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users