in reply to Re^3: Convenient Crypto
in thread Convenient Crypto

Let me explain a little background. In an embedded device exists perl as a means for reliable memory management and possibility to fix bugs remotely. As a "security" (against reverse engineering) the policy is only to run from internal mem. There are three blocks (1536 bytes) available that I try to use for encrypting a database (tied hash) on external mem as a more real means of security. SHA is available because "auth the updates". Blowfish alone is more than 3 blocks.

Sorry about the missing blanks, but I forgot to "ungolf" this.

Replies are listed 'Best First'.
Re^5: Convenient Crypto
by ikegami (Patriarch) on Feb 15, 2011 at 18:12 UTC

    Doesn't change the fact that SHA doesn't provide encryption. Any use of it is pure obfuscation, not encryption. I'm sure there are encryption algorithms designed for use in memory-tight systems.

      Read the Source! It is real crypto, because a key is used and every bit of the result depends on every bit of the key and every bit of the plain text.
        I didn't say that no encryption is occurring.