Because lots of questions come to us about cracking Reason, this
time we would like to explain the CodeMeter and Reason's protection
implementation. Just to mention the audio softwares, there are 3
types of WIBU for copy controling.
1.Just check the dongle. Nothing else. It's a normal easy target
unless there are extra checks or anti piracy methods. MAGIX
Sequoia application stands this type.
2.With AxProtector
http://www.wibusystemsusa.com/products/axprotector.html
AxProtector is a packer. Things like PACE protection - (very
different one for crackers though). Developer does not need to
use SDK to use it. Hard packer but unpackable *theoretically*.
Latest SSL Duende, MAGIX Sequoia DDP adopt AxProtector.
3.With WIBU-CM SDK
With SDK, you can use cryption in the code. Full enhancement
of the Wibu protection - if developers ues it right. When it is
used right, app cannot be cracked (bypassed). App never work
correctly without the right decryption. The only way to remove
is emulation : H2O did it 8 years ago.
Reason uses WIBU-CM SDK. The cryption is used when you load the
user project files : The main restriction of the demo version. All
other export limitations are not protected with any cryptions or
extra tricks. Basically, without any security halls, load function
never works without the proper emulation. Emulate CodeMeter cryption
or dongle - that's the problem ;)
A cracker from us also indicates the way to bypass the encrypted
load function, but you cannot load the project made by the legal
version and need to code additional dll to inject, and more work
to convert "something" to "something". This also needs hard work and
can be disabled by developer - it's unreal way.
In conclusion : Give up your hope.
When the time comes, when poeple forget them, Gods do it. What
you can do is stopping begging or requesting those lost artifacts.