1. HAPPY NEW YEAR!!!
  3. * You need the installation of R2R-WAIFU.
  4. * CodeMeter runtime installation is not required.
  5. * Our release runs faster and uses less memory than legit version.
  6. * Auto-Tune Pro and Auto-Key is included.
  8. NOTE : Preset cannot be recalled from VR release. Because VR release is not
  9. cracked correctly.
  11. ----------------------------------------------------------------------------
  13. Previous release by VR is not cracked correctly and preset is not working
  14. correctly. The second release by them says it is fixed but not, preset is not
  15. compatible with legit version due to the bad crack. Auto-Tune uses crypto
  16. for the preset by using CmCrypt/CmCrypt2 (provided by WIBU CodeMeter Core
  17. API). VR just bypassed that crypto function. You know what that means :)
  19. Also, VR release still calls WIBU Core API. It is logged by WIBU local
  20. service. You can confirm by checking CodeMeter Control Panel or WebAdmin.
  22. What R2R did:
  24. * AxProtector is completely unpacked. Using less memory. loading faster like
  25. our iLok releases. VR version is still packed with AxProtector.
  26. * Re-Linked to our DLL based WIBU API Emulators. Almost same scheme like the
  27. developing version (the one BEFORE protecting Ax/IxProtector).
  28. * You can use our release and legit WIBU protected software at same time.
  30. ----------------------------------------------------------------------------
  32. Q: I want to know about WIBU. What's the technical difference from others?
  33. A: eLicenser - McFACT is a main protection. McFACT is crypto that runs
  34. encrypted without decryption. Some minor apps don't use McFACT
  35. and easy to bypass the license check. Well, those most wanted
  36. targets use McFACT.
  37. PACE/iLok - WrapWarden (packer, PE protector) and Eden/Fusion (custom
  38. API). Anti-Tampering is optional, provided by MetaFortress
  39. (Verimatrix.Inc).
  40. WIBU - AxProtector (packer, PE protector) and IxProtector (code
  41. encryptor, integrated to AxProtector). CoreAPI (custom API,
  42. you can choose to link with AxProtector or link with DLL).
  44. Q: Why do you think only Auto-Tune was cracked (partially) recently?
  45. A: Because Auto-Tune is not really using AxProtector and IxProtector is
  46. used in weak way. Binary is also runnable without license. Running app
  47. with legit license -> dump code section to get IxProtect-ed part -> bypass
  48. license check, and you can get that "partially" crack :)
  49. Of course, to get full working version (regarding the presets), you need
  50. to solve the cryptographic part as we already mentioned above. And it will
  51. perform better when you unpack from AxProtector and strip it.
  53. Q: Are other WIBU protected products protected in the same way?
  54. A: Yes and No. Almost all other proudcts are using AxProtector more to
  55. encrypt the code and you will be needed to unpack them. IxProtector
  56. supports re-encrypting the section, and you will need to dump the section
  57. right after the decryption. The dumping process is needed to be done
  58. carefully, or license will be gone (because IxProtector has TRAP function
  59. as WIBU describes in their web page). This is what called "license lock"
  60. option in Ax/IxProtector.
  62. Q: Can you "do" other WIBU protected products?
  63. A: Yes we can. Legit license is required. We confirm we can unpack stronger
  64. Ax/IxProtector protected targets, and link with our emulator when needed.
  66. Q: Is WIBU CodeMeter good for audio application?
  67. A: We discussed this topic in the group. The answer is - NO.
  68. eLicenser or iLok should be better. The good point of WIBU is not good
  69. for the most audioapps which support plugins.
  70. WIBU has many "license lock" options as anti-debugging anti-dumping way.
  71. Anyway, the protection-chaos of audioapps can easily trigger them
  72. unexpectedly and legit users may loose license. Some plugins hook INT3
  73. like rootkit, some others attach debugger themselves, some uses Enigma/
  74. Themida/VMProtect. It's very hard for developer to determine which WIBU
  75. protection option to acquire to their products when they consider the
  76. compatibility with other plugins. Wrong option choice may result license
  77. locked in WIBU. Back in the day, the developer called Tone2 put many
  78. debugger detection and lead them into Windows shutdown. But many legit
  79. users experienced that bomb (it's finally exposed and fixed in 2015).
  81. https://www.kvraudio.com/forum/viewtopic.php?&t=442754
  82. (Most people think iLok is a reason of mis-detection, but not really)
  84. To avoid the trouble in WIBU, developer need to turn off most options and
  85. disable license locking. (In this meaning, Antares choosed right option to
  86. Auto-Tune v9.1.0). After we showed the unpack of AxProtector, emulation
  87. of Crypto API, fix of IxProtector, what's the reason to choose WIBU
  88. without advanced option and license lock option? "We choose WIBU" means
  89. "We don't care the customer" in audio world after this explanation.
  91. * To be fair, WIBU can be a good choice for standalone business-to-business
  92. application. We said it's just not good for audio apps which load tons of
  93. 3rd party plugins to one main process.
  94. * One exception can be Reason by ReasonStudios. Unless you use VST plugins,
  95. Reason app and the Rack Extensions are fully managed by one developer and
  96. user can manage his all license by one dongle.
  98. Q: Why did you decide to release WIBU thing this time?
  99. A: We feel we need to share the technical notes before more developers (who
  100. doesn't really know about protection) go to CodeMeter just because it is
  101. not cracked. We always welcome the technical refutation from the audio app
  102. developers if we explained wrong about CodeMeter.

HAPPY NEW YEAR!!!