In the evening, I suddenly wanted to do something about Eval. So I turned out a tool I wrote two years ago from the hard disk, and ran and detected it. Everything was normal, however, when we ran to the crack in the last step, we suddenly failed to respond. I started to think that there was a problem with the implementation method of my code, So Baidu went to Google and said on the Internet that the SI of A Nb written by a Nb could be XXXX, and then I went back to work, report the virus-_-#, the age of Internet spam... So I found a similar comparison of Nb's yyyy and ZZZZ to run and check. Without my tools, I couldn't get through the tests. I was so impatient that I had a bit of teeth and a bit of teeth, run it with a virus to check whether it works.
Run, check is normal, crack is also normal. I lamented that there was a gap between my code and the cow, but I was unwilling to come up with a packet capture tool, I checked my code for half an hour and found that my code is correct. The process is similar to XX, and the algorithm is even better, only when the range of the first attempt is reached 64, it stops. Check the code, int min = 0, int max = 64. It turns out that the process is okay, but the scope is too small, leading to crack failure...
Modifying the code, compiling, and everything is okay, so did Daniel. Haha, my code is of high quality and high universality.
PS: Let's look back at the program two years ago. It's like a garbage dump. A piece of code has been repeatedly written more than a dozen times, with a name in the East and a name in the West, if it weren't for me that I still had the habit of writing comments, the code would be a book now-_-#. Rewriting is impossible, so a big project, I don't have the time and energy I spent at school anymore. Some small bugs can be used together, and the speed can be used together.
