I have a friend who uses a simple series of encryptions for things, and then sends the proper method value to an user.
For example, the first thing they do is zip a file. (Think _DEFLATE.) Then he has a series of simple encryption methods to choose from:
Method 1: NOT every byte
Method 2: Write the file in 10 byte chunks — backwards.
Method 3: Use a substitution cypher. A = Z. B = W. Ect...
Method 4: Use a shift-cypher. A = C. B = D. C = E. (Shift value X spaces.)
And so on...
Then you just send the user the proper method number to enter as a passcode (usually obfuscated as well, with a simple math formula. Number 1234567 has the digits add up to 28, which corresponds to a valid method, just as an example.)
None of the processes are overly complex on their own, but they generally render the files secure from meddling/alteration. Unless they’re reversed properly, about the best anyone can ever get from them is a “archive corrupted” message.
By themselves, they probably wouldn’t be hard to break, but by using them on compressed information, he’s never had an issue with them so far. (Of course, we’re not talking securing the US Nuclear Missile launch here; just simple game asset data, and such...)
A lot of times, people tend to overthink how complex encryption has to be, when something *very* simple is sufficient enough for their needs. If I were to just compress the game data for *anything* I’ve ever shared here on the forums, and then wrote it to a file BACKWARDS, is there anybody who’d expend the effort to sit down and sort that out?
99.9987% of pseudo-encryption security comes simply from, “Meh! It’s encrypted. It’s not worth the effort to deal with!”