Let's assume no one is intentionally trying to spy on other
people's data. If that is the case a simple encoding/decoding such
as base64 will suffice.
No sir, as that is exactly what we're trying to do, prevent access
to "other people's data" through URL manipulation. While Base64
would keep a fair number of people out, it is no where near strong
enough for say, patient info, credit card info, etc.
Then I would blowfish encrypt the whole thing. I don't have blowfish
encryption as an Active4D command, but I do have it as a plugin
command. The plugin commands are:
A4D Blowfish encrypt(inText: Text; inPassphrase: String; inIV:
String) -> Text
A4D Blowfish decrypt(inText: Text; inPassphrase: String; inIV:
String) -> Text
inIV is an "initialization vector", which is just some text that is
used to provide a seed for the encryption algorithm, and is usually
some random text which is then prepended or appended to the encrypted
text to be used as the IV when decrypting.
You'll have to make some method wrappers for these to call them from
Active4D.
Regards,
Aparajita
Victory-Heart Productions
www.aparajitaworld.com
"If you dare to fail, you are bound to succeed."
- Sri Chinmoy | www.srichinmoylibrary.com
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
