Flexlm ECC alternate patching methods

[rcer]

nikkapedd,

Thanks & I think I have finally grasped it!. Have a look at the PM I sent to you.

Still have one question. which program do I need to use to unpack Slbsls?

rgds

rcer

[FoxB]

@rcer: you can use the dll inject for the online patch any info inside slbsls

[rcer]

Hi FoxB,

Thanks and can you please explain this in a little detail

rgds

rcer

Originally Posted by FoxB

@rcer: you can use the dll inject for the online patch any info inside slbsls

You are not right. In the previous version of slbsls.exe (SLBLicensing 2013) may be... In the new version of slbsls.exe (SLBLicensing 2014) no.
In the previous version public keys not encrypted (for all three daemons: slbsls, slbfd and lmgrd.slb). In the new version public keys for slbsls daemon is encrypted and public keys for all demons from time to time pass integrity check.

[alekine322]

Hi @rcer

slbsls vendor daemon difficult. I think the most difficult
I'm also trying to vendor daemon packed/encrypted/obfuscated

Thanks for your feedback @nikkapedd and @FoxB

[rcer]

alekine322,

yes slbsls is a tough nut to crack, and we rookies need al the help we can get from the seasoned crackers in this forum

[nathan]

Any chance to get the daemon ?

[alekine322]

Hi

@nathan: Yes, please check you PM

me to i want daemon to

[alekine322]

Hi

@ultimax Force: Yes, please check you PM

[FoxB]

Boot64: you are boot32? upload 2014 daemon, will see it.

[alekine322]

Hi

for slbsls 2013 Licensing.
how hard is to find the encrypted seed. With seeds found, generate my lmcrypt.exe, generate my license. patch files protected by ECC. License fine works
thank you very much

Boot64 (Boot32) you mention the following: for all three daemons: slbsls, slbfd and lmgrd.slb
I've seen licenses with slbsls and slbfd, but never with lmgrd.slb, Application that uses it?
these questions are for my studio

Note: Boot64, Please upload deamon vendor for SLBLicensing 2014 for my studio
Thanks in advance

[nikkapedd]

You need only to change the public key not the private ..
Every time the program check the public key, then authenticate your sign according with the vendor's pubkeys..
But pay attention if the program use also vendor_info or vendor_String certificate to authenticate the license, patching only the pub key is not enough to make a working license...

alekine322, patching only the vendor is not enough to make a working license.. You need to patch also the ECC in the exe/dll files

[bridgeic]

Originally Posted by nikkapedd

You need only to change the public key not the private ..
Every time the program check the public key, then authenticate your sign according with the vendor's pubkeys..

alekine322, patching only the vendor is not enough to make a working license.. You need to patch also the ECC in the exe/dll files

Beside the patch, we still need get lmcrypt that has private/public key paris that match with the patch. Seems compile SDK with setting s below will create private/public keys that consistent with the patch, so I ask
what's the relationship.

#define LM_SEED1 0x11111111
#define LM_SEED2 0x22222222
#define LM_SEED3 0x33333333

[alekine322]

Originally Posted by nikkapedd

alekine322, patching only the vendor is not enough to make a working license.. You need to patch also the ECC in the exe/dll files

YES, is correct