My encryption technique [COMPLETED]

[WallShadow]

Seriously? I can't perform cryptanalysis on it when you keep re-obfuscating it like that. This time my decompiler actually just gave up at one point and started dumping byte code at me. Please give use the proper source code so that I can create a brute forcer for it to check for collisions, this is getting to be impossible.

As a side note, why are you obfuscating it?

[moldyToast1]

Because I'm actually selling this on another forum
I'll send you the source in a PM because I like you

[WallShadow]

Because I'm actually selling this on another forum
I'll send you the source in a PM because I like you

ahhh. genius.

[moldyToast1]

find any collisions? ;D

[WallShadow]

find any collisions? ;D

working on it, a few more minutes and I'll be able to set it to brute force all day long.

edit:

attacking current just as I'm typing this.

[moldyToast1]

Awesome. Tell me if you get anything ;D

-- Sun Jan 06, 2013 2:53 pm --

Just so you know, because there is no length limit, there will be 0 collisions.

[WallShadow]

Just so you know, because there is no length limit, there will be 0 collisions.

We'll see about that as soon as my script starts working again >.<

-- Sun Jan 06, 2013 5:52 pm --

So, an day of attacking and it didn't find any collisions in the set of all 1,2,3 letter long words, and all 4 letter long words starting with a space. I probably implemented the brute forcer terribly and that is why it is going so slow, so I will work on it over the week. Congrats on a successful message obfuscation scheme.

[moldyToast1]

thanks wallShadow
Looking at the source code you can figure out that there cant be any collisions because you can decrypt the text.
Its not a hash Lol