1. A serial generated by our keygen can be invalidated at next startup. This is
  2. not our fault but bug. Try generating another one.
  3. The authorization function of TAL-J-8 is broken. It uses different process
  4. between some functions.
  5. When you input serial :
  6. 1. Conver to ascii serial to binary by Base32.
  7. 2. Decrypt by Blowfish and get ascii decimal value.
  8. 3. Convert asii decimal value to number (Atoi).
  9. 4. Validate that number.
  10. When startup :
  11. 1. Convert ascii serial to number (Atoi). The number will be broken because
  12. serial isn't processed by Base32 decoding and Blowfish decryption.
  13. 2. Validate that broken number.
  14. As a result, some legit serial can be invalidated in next startup. In
  15. addition, both serial validation has vulnerablity that invalid serial can
  16. be recognized as legit serial. Actually, previous one shared in P2P contains
  17. wrong serial number. This happens because Atoi (ascii to int) function can
  18. convert broken data to valid int value. After the Blowfish decryption, some
  19. more validation should be done before Atoi to avoid broken data.
  20. In short, current auth validation doesn't always pass valid serial, and it
  21. sometime passes invalid serial.
  22. The licenses generated by many of our keygens (incl. TAL one) have watermark.
  23. They are valid but we can still identify. Did you know that our TAL-U-NO-LX
  24. license always starts with "599C767C"? We are wathing you!
  25. It looks like one famous release group is loving to use R2R keygen :)


Comments powered by Disqus