this version makes it's a very difficult task to make a clean dump that you can use on any computer. however, it is extremely easy (but time consuming) to unpack the apps and have them run on your own machine (and possibly even the same OS on another machine). I may write a tutorial on the entire process and post it here, but the basic idea behind it is to dump and attach the aspr envelope to the dumped.exe file. This involves realigning dumped sections and playing with import functions. The biggest obstacle to overcome would be rebuilding an import table and IAT, since aspr now doesn't simply use redirection from withing the IAT.
And, if Alexey ever peers this forum (who knows) here's a little msg to him:
Quote:
|
While this implementation is a better protection (in that it requires more time and effort to crack it), it is not better for the end user. Your new system will protect better, but waste more cpu cycles and ultimately slow down the application in boot time and in execution. This is in stark contrast to your previous protector which was very fast. One of the biggest problems I have with protectors like Armadillo and others is the speed and stability issues. And now, it seems, you're moving to that direction as well. You're finding yourself in bad company. This is a real shame considering you had the best protector out there if programmers would simply use the tools available to them and encrypt pieces of code unless a valid key is present. Anyway to summarize, while I understand the need to offer this type of protection it is still very breakable and you will not be keeping products out of the hands of those who seek to acquire them illegally. Rather you will end up giving the legitimate user a headache from a frustratingly slow starting and slow running, unstable app. Same story as always, good old Joe Shmo gets screwed for no real good reason all in the name of stopping piracy and that, my friend, will never happen.
|