I need a simple encryption for some text strings. I want to create coupon codes and make them look cool so subsequently created code should look very different. (And besides looking cool, it shouldn't be easy to guess a code.) But I want to be able to decrypt them again. So the algorithm must be reversible.
I alread tried some stuff with moving bits around so they look kind of random already. But two subsequent codes (just one bit different) of course look very similar.
Any suggestions? I would like to do that without using external gems.
Philip
I can recommend you uuencode and uudecode utils you can use them wuth standart ruby function pack:
(sample from Hal Fulton's Ruby Way)
You could use OpenSSL::Cypher
But the intermediate form doesn't lend itself well to printing
Given your thought that it would be nice if the intermediate form was the same length, you might just use a simple map of one char to another.
PLEASE UNDERSTAND THAT THIS IS NOT SECURE
You can easily brute force the key, but it seems to be congruent with your requirements.
If you don't need real encryption, you can use a simple cipher. (This can be used when you don't need security, or to encrypt short random/one-off strings.)
Optional method for encryption and decryption
You can check all different ways of encryption/decryption using ruby in this gist: https://gist.github.com/iufuenza/183a45c601a5c157a5372c5f1cfb9e3e
If you don't want to use a gem, I would totally recommend Openssl as the most secure which is also very easy to implement as it has very good Ruby support.
Do you really want to trust the user to give you back the right value? If you trust what the client gives you back and the user figures out your encryption scheme you'll be using data they provide. That sounds like a very bad idea.
It's not clear to me why you don't want to give them a key into a database that maps a random numbers, perhaps with some error correction properties, to the coupon discounts. That way you have control of the final result. They provide you a key, you look up the associated coupon and apply the coupon. In this way you're only using your own data and if you want to remove a coupon it's all on the server side.
If you keep all the key-codes you can also check that new codes are different from previously released ones.