| ??? 02/25/08 21:34 Read: times |
#151451 - not necessarily Responding to: ???'s previous message |
I do agree with you, though. You have to assume that anyone that wants your code will get it. You need to provide value elsewhere which will separate you from the thief of your code.
My legal disassebly experience tell me that good code is will "separate you from the thief" provided the thief do not carbon copy the hardware. if the hardware is ' carbon copied' you DO have a legal recourse and the paranoid can oblitterate the type numbers on the chips which makes a hardware copy almost impossible to make. Anyhow, I just realize that the OPs 'protection' is darn easy to circumvent (2 minutes max) and, if he will send me an e-mail, I'll tell him how easy it is privately. Erik |
| Topic | Author | Date |
| Secure IAP (In Application Programming) | 01/01/70 00:00 | |
| It is not THAT important | 01/01/70 00:00 | |
| Encryption | 01/01/70 00:00 | |
| not necessarily | 01/01/70 00:00 | |
| 2 minutes? | 01/01/70 00:00 | |
| Encryption worth it? | 01/01/70 00:00 | |
| the philosophical thread continued | 01/01/70 00:00 | |
if you want to make it really painful ... | 01/01/70 00:00 | |
| ansered by e-mail | 01/01/70 00:00 | |
| the balancing act | 01/01/70 00:00 | |
| there is little difference... | 01/01/70 00:00 | |
| bootloader | 01/01/70 00:00 | |
| On a SiLabs F02x or similar | 01/01/70 00:00 | |
| it's the same on other derivatives, too... | 01/01/70 00:00 |