hi, how i can block to xfer serum the conexions for not update the serial? in MAC

I know there are people who have achieved, but not how to do this

 

There is no point in blocking web browser / internet connection for Xfer Records Serum because it has a time bomb implemented. It is triggered when you save a preset and will ask for the legit serial upon opening the plugin. Even on offline machines R2R keygen is not working for later versions of Serum. At least on Windows. But why would there be different protection scheme for OSX?

https://audiosex.pro/threads/serum-installation-issues-serial-not-working.23557/#post-173971

So without a proper scene release, there seems to be no way to get past the time bomb it seems.

edit: typo

 

You have to patch some codes in the binary file to prevent constant Serial checks!
U-he & Rob Papen aren't the only ones who implement *time-bombs* in their thingies.
Keygens are mostly useless [crap] since new updates often require new codes.
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

 

what was the last stable non-nagware version of Serum Kook?

 

Essentially that is what I was trying to say. Thank you for clarifying.

 

I have version 1.073 (Mac) installed.

You're welcome mate. I'm aware of it that patching requires some specific skills.
I still haven't had a look on the latest SERUM. It would be much easier having 2 versions
to compare, a cracked and a non-cracked. Otherwise having to use *Hopper Disassembler*
or IDA-Pro could be a tedious work and i don't have so much time to "dive" into codes.

––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

 

What I have done is to download the 1.07b version, use Little Snitch to block incoming and outgoing connections to Logic X and Ableton Live, install and crack, then install the new update. I have had no troubles whatsoever. In fact I've never had any troubles with plugins time-bombing while blocking incoming and outgoing connections with both DAWs with Little Snitch. Search any popular torrent site for a crack of it and it's very easy to setup.

Best of luck!

 

Mate, the time bomb is in the code of the plugin. You really don't have to go online to trigger it. In fact it has nothing to do with your machine being online. As soon as you doing something more with your instruments, the time-bomb(s) is triggered, rendering the instrument useless. I am sorry to message you the bad news.

 

Precise explanation!
For interested freaks or not: Developers embed simple comparing (cmp) commands in the code which
can be positioned elsewhere. It's like policemen directing the traffic, as soon as a "deviation" gets
detected they stop the traffic and do what they're taught to do!

In this case existing or blacklisted Serial Numbers get compared, hence the software stops to work
or gets deactived from inside. Obsessed developers (like Rob Papen) sometimes put dozens & hundreds
of such traps into their software.

–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

 

Last edited: Mar 16, 2016

Kookaboo, one question though. Isn't it possible (albeit unlikely) that the keygen comes up with a working serial by accident? Don't know how likely that is but maybe a few were lucky enough to get a working key from the keygen. That would explain why it looks like the generated keys are working, which in fact they do if you are really lucky.

 

I think I've found the way to crack the latest version in mac but I need a programmer to do

 

But it totally works guys, you just have to block your host DAW and the 1.07b version is totally working fine and I updated with the 1.094 and it's still working great. Try it.

 

hey, using hands off here. not sure if I am blocking this in the right way.
Ableton DAW is blocked, thats for sure. But do I need to block something else, too ?

plugin is asking me for serial over and over again. and the same serial works over and over again. v 1.094 on a el capitan mac

 

I wouldn't exclude that - but reality is often quite different.
When cracks flood the Internet many developers react quickly by putting up new barreers in the code.
+ Without patching the code from inside the Plug-In could of course accept keygenned Serials,
but as soon as you re-launch it, it will revert back to Trial Mode.

–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

 

It's easy: patch it and keep the net wire unplugged while you use it.

 

... until the TIME bomb renders the plugin unusable.
When (not if!) this happens, every time you save or load a preset and you reload the plugin, Serum asks for a serial.

If you don't have the problem already, then the time bomb has not yet fired.

 

Last edited: Mar 16, 2016

Oh yeah, you are right. The first time I opened it up it was great and worked totally fine. Now it's bombed. Oh well, I imagine some one will patch it soon enough.

 

Mr. Kookaboo , how you will know all of that ? because you said yourselves that you are just hex comparing cracks from other people .

did you have learned something new in real ?

dont have much time are just an excuse for you can not .

 

That's my business young boy! And keep your sarcasm for yourself.
I'm not here to provide everybody.
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

 

Let's see if I fully understand this whole serial thing.

Some code inside the plugin takes the serial number / key and puts it into an algorithm that computes a check sum or value. If that value is what the plugin expect it to be, the serial number / key is valid, otherwise it is not. Challenge-response-methods are basically the same, only the algorithm takes some OS or hardware values into account like processor ID, amount of RAM and whatnot in order to bind the software to a customer's PC or MAC device.

In order to know how to program a key generator, you have to know how this key checking algorithm works exactly. To stop people looking into the code, developers encrypt the code with something like RSA or AES. So far so good?

That means one as to either (A) break the encryption to reverse engineer the key checking algorithm and to program a working key generator or (B) remove the key checks from the code of the plugin.

(A) is the best method because you can have valid keys even for future versions / updates of the plugin without toughing the code of the plugin. But with a proper and strong encryption in place it is nearly impossible to do.

(B) needs altering (patching) the actual code of the plugin. That can also be very difficult but in most cases is still a lot easier than breaking the encryption of the key checking algorithm. And it needs to be done with every new version of the plugin.

Am I right this far?

So what's up with the keygen for this plugin? Is it kind of half working because the encryption was not broken and in consequence was not reverse engineered but by comparing legit keys with the ones that were generated, one can come close to the algorithm that checks the keys? Does this make any sense? I don't understand why earlier version of the plugin seem to accept a generated key but later versions don't. As a customer I would receive only one key for all versions of the software. So to me it seems obvious that a key can not be half valid. Either it is valid or it is not. What did I miss?