| ??? 02/24/06 21:11 Read: times |
#110732 - the weekness Responding to: ???'s previous message |
The weekness of the "crypting" device inserted between code memory and the execution "core" lies in the possibility to intercept the code after decoding...
Even if this is prevented by integrating the "decoder" into the execution core, a relatively simple attack can be based on submitting various "encrypted" code different than what is in the code memory and deduce the "decryption result" based on the chip's behaviour. That was the point of the attack on the Dallas' crypto-51, discussed here recently (I think the thread started by something like "how to destroy a pin ... needed for the code readout", which for itself is a way - although controversial and not generally recommended - how to protect). ---- The issue of security comes up so often a FAQ should be based on it. As there is a lot to be discussed, it would be a very good topic for the... wiki... (forever :-) Jan Waclawek |
| Topic | Author | Date |
| HOW TO PROTECT SOFTWARE? | 01/01/70 00:00 | |
| When asking questions like yours ALWAYS | 01/01/70 00:00 | |
| Agree with Erik | 01/01/70 00:00 | |
| Agree with Erik & Jack. | 01/01/70 00:00 | |
| a simple test | 01/01/70 00:00 | |
| By using a programmer which supports... | 01/01/70 00:00 | |
| reading correct ? | 01/01/70 00:00 | |
| Maybe all he wants is ... | 01/01/70 00:00 | |
| How do you propose to do this as a condi | 01/01/70 00:00 | |
| Two answers ... | 01/01/70 00:00 | |
| the weekness | 01/01/70 00:00 | |
| HOW TO PROTECT SOFTWARE? | 01/01/70 00:00 | |
| re crypting | 01/01/70 00:00 | |
| re: eric | 01/01/70 00:00 | |
| where ther is a will, there is a way | 01/01/70 00:00 | |
| the "simple" "encryption" | 01/01/70 00:00 | |
| another example : smartcards | 01/01/70 00:00 | |
| Sorry, but you are O.T. | 01/01/70 00:00 | |
| what ????????????????? | 01/01/70 00:00 | |
| Stop misusing this forum! | 01/01/70 00:00 | |
Where are you Jog Milind? | 01/01/70 00:00 |