The original idea with implementing blowfish was a means for securing the code on an unsecured eeprom/flash in the next Propeller. There would be an internal array of fuses which contains the passcode which is not accessable at run time. A tiny blowfish engine implemented on the P2 would use the passcode (in a protected kernel mode) to load the encrypted code and place the decypted code into memory. This method isn't feasible with the current Propeller because theres no means to hide the passcode. However it still has applications with the current Propeller for encrypting datastreams where the intruder doesn't have physical access to the Propeller (like trying to sniff RF or wire communications).
Comments
not from me I'm afraid. I have yet to take the leap into assembly! And cryptography is a whole new ball park on top of that
rgds
Paul
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
"There are 10 types of people in the world. Those who understand binary and those who don't."
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Paul Baker