U-he Satin v1.3.1.7414-R2R
DATE : 2020.01.01 | NUMBER : R2R-8593 | SiZE : 16.36 MB
PLATFORM : WiN32/64 - VST/VST3/AAX(MODiFiED)
We took a journey back to the Golden Age of magnetic tape recording. We wanted to recreate all kinds of tape machines in software, from the ground up. After many months spent on research, measurement and on developing an architecture that would be flexible enough for the job, we knew we had nailed it... But we couldn't stop there: We added the old noise-reduction systems that were often (mis)used for timbral compression effects. Then more heads and a global feedback path, which made an uber-tape-delay and realistic 'one-shot' tape flanging possible. Users familiar with analogue recording gear should instantly feel at home with Satin, and digital afficionados will also learn to love the magic of tape – Satin invites you to explore and find out for yourself.
home page
https://u-he.com/products/satin/download from free file storage
HAPPY NEW YEAR!!!
Release by VR timebombs. VR tried to force-validate serial by old routine by
patching but it doesn't really help. We checked their Hive2 release and we
found zero timebombs are patched. Now you know that users who posts "100
percent working" for their releases are zero percent trustful.
At least we checked many places they haven't noticed.
Let's hope we made 100 percent again this time :)
----------------------------------------------------------------------------
Here is how U-he main protection works:
1. Generate value (0 - 2047) from the licensee name.
We call this value "UserValue".
2. Get the hash of serial number by UrsHash.
UrsHash is combination of WHIRLPOOL512 and SHA512)
3. Get hardcodedHash[UserValue] and compare with calculated hash.
If it matches, license = OK.
This means, serial number is not generated for users dynamically. The hash
of all serial numbers are hardcoded to the app since the first release. User
name is just used to determine which correct serial number to assign. This
is good if dev has many customers, otherwise serial check will be dull and
slow (check all hardcoded serials one by one, this is done by RobPapen).
However, there is the weak point in this "wise" protection. Once legit serial
numbers are leaked, that serial number can be used to other name. You can
make another licensee for that serial by colliding "UserValue". This is not
easy to avoid. Blacklisting the leaked serial number can affect to the legit
users too, because that user may have same UserValue with leaked licensee.
In short:
- Uhe app contains 2048 correct hashed serial numbers.
- Calculate valid serial from hashed serial is nearly impossible.
- User A and User B may have same legit serial number.
-> Generate another valid name for leaked serial can be possible.
Enjoy checking many security aspects for the uhe type protection.
These UserValue+Hash protection is used by Arturia, Audiority, SonicAcademy,
LVC-Audio, Youlean etc. Valid user+serial pair can be made from legit serial.