This program is a progressive type encryptor/decryptor with a twist. What this means is that it will take a variable length key, and encrypt a file using it in two (2) ways. One way is to step through the file one character at a time and XOR the character with a character from your private key which is, also, being stepped through one character at a time. The private key will continuously be used until the entire file is processed. This is the XOR encryptor part. The character is also encrypted by performing various mathematical computations to it involving, amongst other things, the use of the checksum of your private key. The checksum is created in the standard way and if you wish to learn more about how to create a checksum, it can be found on the Internet. By the way, the maximum key size is 256 bytes(2048 bits). The encryption is strong enough to keep most hackers out(maybe not professionals though).

Because of some complexities inherent to the program and in keeping with my desire to make my code 'open source' with no restrictions, I have totally rewritten the program to remove all obfuscations. The flow of the program is easy to follow, now, and CPU usage has returned to normal.

I removed the Progress Bar for the same reason that I removed the Pause button - the program completes the task so quickly that it serves no purpose. You would need to encrypt an extremely large text file in order to see it work in a meaningful way.

I, also, added a MessageBox to inform the user when the current task is completed.

Bug fix. If the GO button was clicked without a key enterred, the program crashed. I fixed this by adding a MessageBox explaining the error. After it is closed the program re-enters the Message Loop thereby giving the user the user the opportunity to correct the error and continue the task.

The PAUSE button has been removed. The program is so fast the PAUSE button was pretty much useless

At this point, for reasons that I do not wish to discuss, I reworked and cleaned up the code to make it less readable. Some may wonder why I obfuscated the code but still released the sources. The reason I did this is because I wanted the code to have a unique stamp to it that would be easily identified as my own.

Major rewrite and first release of the software. This is a beta release as I only just finished converting it from NASM to MASM. At the same time, I removed all elements of the pattern encrypter portion of the software and ported the algorythm from PadLock into this program. Padlock is a DOS based 16bit program but the algorythm was very easy to port. The goal of this program is to create a win32 application that Encrypts/Decrypts text files. It is important that an examination of the encrypted file does not reveal any discernable patterns or ASCII bleed-through. Version tracking starts from this point, on.

The orginal concept for this program came to me when I stumbled across a fellow working on a NASM implimentation. He was having trouble getting it to work and was asking for help. We never did get the NASM version to work the way he wanted it to work. He wanted to deploy it using a pattern overlay encryptor. The output from the encryptor had too many recognizable patterns. I suggested he switch methods; instead, he gave up in disgust giving me the sources to do what I will with them. I began to explore the idea of converting this code to MASM and use a type of XOR encryptor with a twist.