Re: why shareware
Originally posted here by Casablanca
There actually no reason for making it shareware other than for advertising me ;). Ypu r absolutely right about having more protection if I wanted to make it demo/shareware properly... but I am not poficient enough in programming for that. I would have to learn some techniques first. Now, if someone wants to teach me, please do.
well first try making it not shareware because shareware is just another rls for me ;P
Make a demo which doesnt actualy have all the features in it which makes it pretty much impossible (or ****ing annoying) to crack.
Or, you could pack the hell out of it using some lame packer like asprotect (which claims to be unpackable, but definently is). That's what most shareware authors do.....relying on a packer/protector is normally like asking someone to crack your program for a challenge.
Well, it sounds to me like the demo is better than the shareware...
One question... what does "rls" mean? (Real Lamer shite?... maybe?)
if you only use the key one time, yes it would be a one time pad. But using it over and over is also an option, and nearly as secure. As long as the key never falls into the hands of someone else, yeah...it will be secure, simply because there is no "cheater" way to undo an XOR unless the pattern repeats. Also one other note to remember, if you transmit more than one message using this meathod, it gets slightly less secure with each message. "Technically" you can break it using two ciphertexts and a LOT of spare time, simply because you can XOR the word over and over on the key at different offsets and get "pieces" of the plaintext, which can then be used to obtain parts of the key, and try them against the other ciphertext. But anyway...enough about that....:)
Hi again... Ihave been revising my code and realized I could modify it to make it clear and waste less memory. Now the main key is always of type double, although the user inputs it as an int. These reduces the extra variable I defined as x. The method Iterate() is now clearer to see because it needs no scaling as I had before.
Thank u all for your comments.
This has been one of the best threads I've read in a long time. Very informative!
Fix one little problem
Right... this is the final version of the class TRHCryptor using the algorithm described. It fixes one little problem that occurs in the previous versions. Now, x is not allowed to be negative.
Thanx again to everyone.
I think I remember the math problem you are using from somewhere, is it called a raki series?
It's good to know... I never heard of it