Code protect idea for Propeller2
JDat
Posts: 103
Hello!
Just quick idea: Add 512 bit eeprom for cryptokey on dice. User can ONLY program internal eeprom with cryptokey, but can not read it. Only ROM bootloader can read internal eeprom cryptokey and decrypt HubRAM contents when load actual code form external I2C chip.
Just quick idea: Add 512 bit eeprom for cryptokey on dice. User can ONLY program internal eeprom with cryptokey, but can not read it. Only ROM bootloader can read internal eeprom cryptokey and decrypt HubRAM contents when load actual code form external I2C chip.
Comments
EEPROM/FLASH is not available in the process that will be used.
Welcome to the forum.
As Bill stated you described basically how the encryption on the next Propeller chip is supposed to look like.
Not EEPROM but build in fuses, able to be burned one time. As far as I remember the Idea was to use SHA(256) algorithm to decode and encode the content of external flash memory to protect from copying and manipulation.
Once a key is burned the propeller 2 will just accept encrypted boot-code from serial and flash.
There was also the talk of having fuses left for your own code/use.
I also remember that (some?) of these fuses are not readable after booting the system.
But all of this is still in flux, the design of the P2 is not finalized yet.
Enjoy!
Mike