tanis
October 5th, 2004, 10:21
I am trying to work my way through an application that is protected with ASProtect and a custom serial + activation code combination.
I found out how to get through ASProtect (it's used in some DLLs instead of the EXE) and have a look at the full code using OllyDbg.
I tried bypassing the serial number check and the activation code check and I successfully got into the real application and at a first glance it seems to work.
I tried working with the app and I noticed that there's a component that's actually behaving differently than it was when I was using it as an evaluation version.
Now whta I wonder is if this could be something that has to do with the protection itself or if there's anything else I should check to clear my mind. Maybe this is a known issue that affects applications protected with ASProtect or some other generic protection that I didn't recognize.
Thanks!
-tanis
I found out how to get through ASProtect (it's used in some DLLs instead of the EXE) and have a look at the full code using OllyDbg.
I tried bypassing the serial number check and the activation code check and I successfully got into the real application and at a first glance it seems to work.
I tried working with the app and I noticed that there's a component that's actually behaving differently than it was when I was using it as an evaluation version.
Now whta I wonder is if this could be something that has to do with the protection itself or if there's anything else I should check to clear my mind. Maybe this is a known issue that affects applications protected with ASProtect or some other generic protection that I didn't recognize.
Thanks!
-tanis