02-25-2025, 01:36 AM
(02-24-2025, 09:00 PM)Pete Wrote: Hey Sam, @a740g
A quarter of a century ago I wrote my own encryption for office data. It worked great but by today's standards would be considered obsolete. My question is how involved would this be using this new QB64 encryption function to get even something simple like a password encrypted?
So say want to encrypt my password to this forum:
password$ = "peteistremendousbutsteveisjustamazing"
How would I encrypt that with this new feature so, unlike the example in the wiki, someone can't just decode it with _BASE64DECODE$? I would think there should be a key involved.
Pete
Well, you should not use _BASE64ENCODE$ or even _DEFLATE$ for encrypting sensitive data because these are not encryption methods. Anyone can trivially reverse them using _BASE64DECODE$ and _INFLATE$.
_MD5$, _ADLER32, and _CRC32 are not encryption but hashing/checksum functions and the results are not reversible.
As you rightly pointed out, you would need something that takes a key and then encrypts the data using the key. To reverse the process and get back the original data, you would have to use the same key. I think something like AES should do the job quite well.
I'll try to put together something over the weekend.