Detrius
March 29th, 2006, 22:12
Hello,
I am a student and have some basic knowledge of programming and my Dad is working as a programmer.
We both have no experience with "cracking", but right now we are trying to "crack" (I don`t kow the exact definition of "cracking"
a program protected by "Crypkey 5.6".
Our first attempt was the one we thought the easiest: we wrote a program from which we called the target program. Our program waited for a short time (starting time), then set the computer clock every 1/100 second back to the starting time. When the target program was closed, we let our program wait for a short while, then saved this time. At the next start, we fetched this time, set the clock back with it, saved the time when the target program quit, and so on.
I know this is not really crcking, but with this method one could use the program for a very long time instead of only 30 days.
The problem was, this method worked most but not every time the target program was started and while we tried to fix this problem we made a mistake: at one time we set the time back but not the year ( we started to work on this problem shortly before the year 2006, so this time we set the time back on for example 25.12.06 instead of 25.12.05) and after that the 30-day-period was over…
After that I did some research in the Internet and found that Crypkey writes information about the 30-day-period in/after the end of different files (is that correct?). So one possibility would be to find these files and delete the information, so Crypkey thinks it is it`s first run each time it`s started, correct? Any hints how to find this files?
Another way would be to manipulate the checking process itself, which happens in some of Crypkey`s DLL`s (correct?). Any hints in which DLL`s or how to find them? Adresses?
I hope this request doesn`t bore you too much, if not please answer…
Detrius
(Crypkey-Version-5.6 -> found it in a forum-> how can I check it another way?)
I am a student and have some basic knowledge of programming and my Dad is working as a programmer.
We both have no experience with "cracking", but right now we are trying to "crack" (I don`t kow the exact definition of "cracking"

Our first attempt was the one we thought the easiest: we wrote a program from which we called the target program. Our program waited for a short time (starting time), then set the computer clock every 1/100 second back to the starting time. When the target program was closed, we let our program wait for a short while, then saved this time. At the next start, we fetched this time, set the clock back with it, saved the time when the target program quit, and so on.
I know this is not really crcking, but with this method one could use the program for a very long time instead of only 30 days.
The problem was, this method worked most but not every time the target program was started and while we tried to fix this problem we made a mistake: at one time we set the time back but not the year ( we started to work on this problem shortly before the year 2006, so this time we set the time back on for example 25.12.06 instead of 25.12.05) and after that the 30-day-period was over…
After that I did some research in the Internet and found that Crypkey writes information about the 30-day-period in/after the end of different files (is that correct?). So one possibility would be to find these files and delete the information, so Crypkey thinks it is it`s first run each time it`s started, correct? Any hints how to find this files?
Another way would be to manipulate the checking process itself, which happens in some of Crypkey`s DLL`s (correct?). Any hints in which DLL`s or how to find them? Adresses?
I hope this request doesn`t bore you too much, if not please answer…
Detrius
(Crypkey-Version-5.6 -> found it in a forum-> how can I check it another way?)