![]() Generating a keygen for the registry file would achieve very little unless you already own a UAD card - and then you are risking screwing up a perfectly good system for relatively little gain. The hardware gets a new lease of life, no development costs for a new card - and is protected against future improvements in native CPU power. This would allow for more plugin instances per DSP, more power (depending on native CPU) and still retain the inherent difficulty in cracking the platform. If I were UAD, I would be reworking their coding so that (say) 80% of the plugin would run on the native processor (currently I would guess that only the GUI and I/O run natively) and the remaining 20% runs on the mpact processor. So to run the plugs you need the card = \"hackproof\". The op codes are single-instruction multiple-data operations that can perform vector functions on arrays of operands without time-consuming program loops.\" \"The Mpact processor has its own machine language that packs two op codes into every word by using a long instruction word (LIW) format. I think that the reason nobody has cracked the UAD platform is that the code to run the plugins will be compiled for the mpact processor and wouldn't run on an Intel or PPC processor - you'd have to decompile the code and recompile it for a native processor with a different architecture. Well, there simply is no way to make a keygen.Ĭracking this system would be hard indeed. Well, since you have no way of knowing the algorithm used, since it's in hardware, since you have no way to \"shortcircuit\" or emulate the protective algorithm, since it's purely in hardware, and since each of the keys on the card that is used to verify plugins is a unique, random, one time pad. If the calculated checksum is the same as your reg key, It's allowed to run (and this check is made in the card hardware as well, only the reg key is sent to the card). Then, on the card, in hardware, I have the algorithm to calculate a \"checksum\" from the plugin ID and one of the unique numbers stored on your card (a separate number used for each plugin). Now, for each new plugin, i give it some unique ID (or hard to tell property, like the checksum of the plugin dsp code). Then, I keep all these numbers stored in my database, linked to card serial number. On the rom of each card, i place one thousand or so really long, unique, numbers, just like the ones in the reg file. Well, had me thinking for a while, how I would have done the copy protection if I had the same possibilities as UA. Read in another thread: \"I have no doubt that a group capable of emulating Synchrosoft device or PACE/Ilok can make a generator of the UA reg file.\" ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |