Spectrasonics - Omnisphere v2.8.1c Standalone, VSTi, VST3, AAX x64 (v2) - обновление для Omnisphere 2

В файле R2R.txt

We remade keygen from scratch.

* Support new Spectrasonics auth format.
* No more crash when you paste the license to app.
* No more timebomb issue in Omnisphere.

TECHNICAL INFORMATION - The ANTI-R2R KeyGen Ways added in the updates!

1. Crashing app when pasting the license

Here is pseudo code of PASTE function in the latest version.
----------------------------------------------------------------------------
Win32::OpenClipboard(hWnd);
hGlobal = Win32::GetClipboardData(CF_TEXT);
clipboardData = Win32::GlobalLock(hGlobal);

Spectrasonics::removeSpaces(clipboardData);
Spectrasonics::addSpaces(clipboardData);
(DO MORE THINGS HERE)

Win32::GlobalUnlock(hGlobal);
Win32::CloseClipboard();
----------------------------------------------------------------------------

When you paste legit license, nothing will happen :

INPUT : xxxxxxxxxxxx xxxxxxxxxxxx xxxxxxxxxxxx ....
SPACE REMOVED : xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ....
SPACE ADDED : xxxxxxxxxxxx xxxxxxxxxxxx xxxxxxxxxxxx ....

When you paste the license from previous keygen (no spaces!) :

INPUT : xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ....
SPACE REMOVED : xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ....
SPACE ADDED : xxxxxxxxxxxx xxxxxxxxxxxx xxxxxxxxxxxx ....

After adding space, the license length becomes longer than first input. This
will cause buffer overrun and it destroys the stack most time! However,
on some computers, it won't crash immediately, or errors are ignored on some
hosts. Once activation file is generated and restarting the app, this code
does not affect to its stability. It wasn't a big issue for crack users.

TBH, we are not sure if Spectrasonics intends to do this, because this can
cause lots of side effects. When user accidentaly pastes non license data,
their "protection" leads crashing too. Anyway, our new license does not crash
like before.

TIPS : Crashes or not, do not modify the memory acquired by GetClipboardData.
The behavior is totally undefeined and not assured by Windows. You need to
allocate the memory and copy the data to that before processing!

2. Timebomb!

There are 2 types of triggers. Timebomb is only available in Omnisphere2.
After timebombing, it bypasses many essential functions.

- Checks the 16bit license flags.
When Bit1 (Omnisphere2 License) is 0, timebombs!
When Bit2 is 1, timebombs!

Previous keygen generates full bits license = all bits 1 = 0xFFFF.
Since its Bit2 is 1, it causes timebombs.

- RSA2048 PublicKey Modification Check
Because RSA2048 is mathematically unbeatable in 2021, we swap the key to
own one (that's why we have to patch for some keygens!). Spectrasonics
checks that RSA PublicKey if it's original or modified by R2R patch. When
it detects modification, timebombs!

3. Protection for what?

After we released last Omnisphere2 updates last year, we saw some posts
about timebombs. However, we also found that some legit users are reporting
exact same issue. We were skeptical about the timebomb existence.

These ambiguous extra protections should be effective for crackers for sure,
but it also lowers the chance for crack users going to legit. Because there
are no guarantee that legit version works without that issue. Urs (U-he)
reprted that his sales increases on "ACE Day".

Cracks in figures

Their timebomb is obvious (showing message or funny graphics etc). Users
can know it's due to the bad-crack. If their timebomb silently crashes DAW,
or triggers minor disadvantage, R2R don't think those sales increasing
happens.

This vagueness reminds us NI Massive (check NFO of v1.2.1 by ASSiGN). There
were hidden extra checks to crash the apps which weren't cracked before.
People who experienced this crash thought it was a bug. The solution (file
deletion in setting dir) was shared as common knowledge everywhere. No one
thoght it was due to the extra protection until NI forum moderator stated
the fact! In short - NI beated crackers (until they state the fact), but they
lost the reputation of the app-stability and didn't help people going legit
(because people thought the crash was a bug which NI cannot fix). NI stops
using it after once ASSiGN cracked it, and never implemented again till now.

"Protection for what" is a nice topic for companies.

* Special thanks to someone who cracked Omnisphere2 without keygen. After we
saw some users posting that issue doesn't happen, we finally decided checking
the whole protection again!

* Downloading, installing, updating all Spectrasonics plugins and contents
took much more time than checking protection