well, i'm taking a 5 min break from studying to think about my plans for the next release of codeCrypter.
The main weakness of the last release, which allowed a signature to be put on it, was that it used a static stub at entry point and another static stub for the decryption routine.
The second weakness was that the decryption stub was always placed in the same location in the last section of the file.
Finally, it used fixed parameters in the Linear Congential Random Number Generator (LCG) algorithm I used to perform the "encryption".
Now on the other side of things, I have not had any time to get further on my other project CodeMutator, but it had come a fair long way in development, and is capable of mutating stubs...
So the next release of codeCrypter is going to incorporate codeMutator for the purpose of making the stub different every time the packer is used.
The location of the decryption stub will be random in the last section, and random data will be filled in the space made for the stub, rather than leaving zeros (which allows AV to find the stub).
Finally, the user will be able to provide their own parameters for the LCG.
Now...back to revision...
See Ya!
03/04/06 @ 21:17