Flexlm ECC alternate patching methods

[FoxB]

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

[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]

Hi FoxB,

Thanks and can you please explain this in a little detail

rgds

rcer

[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

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.

[FoxB]

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

[bridgeic]

Originally Posted by nathan

......
Find attached the Generic pubkey replacer made by Tanker (win + linux). I tested the Win version on a couple of targets (v11.10 and v11.9.1) and it identifies the pubkey correctly (I double checked in the vendorcode struct in memory), however, I didn't manage to produce a working license, yet (work in progress as I may be missing something crucial in the generation).
......
nathan

If use this patch, what we should do at FlexLM SDK side? Which files should be modified? lmprikey.h? or some other files together? How to modify?

[bridgeic]

Originally Posted by bridgeic

If use this patch, what we should do at FlexLM SDK side? Which files should be modified? lmprikey.h? or some other files together? How to modify?

For license with 239bit SIGN2, I see two groups of private keys as below after compiler SDK. Then whether this ecc patch still work? Or should add the 2nd corresponding pubkey into the patcher also?

static unsigned char lm_prikey[2][3][40] = {{{0x0, 0xb2, 0x45, 0x2c, 0xbc, 0x7e, 0x72, 0xc1, 0x3a, 0x39, 0x5e, 0x67, 0x25, 0xce, 0xd9},
{0x2, 0x1c, 0x8f, 0xa2, 0xe4, 0xb6, 0x4f, 0x7a, 0x2c, 0xd2, 0x6, 0x81, 0xb5, 0xd8, 0xf9, 0xf1, 0x81, 0x6, 0x4a, 0x8e, 0x17},
{0x3, 0xa0, 0x58, 0x89, 0xd2, 0x30, 0x22, 0xd8, 0xca, 0x5e, 0xac, 0x59, 0x33, 0xb3, 0x69, 0xdc, 0x30, 0x9b, 0xb6, 0x8d, 0x24, 0x56, 0x60, 0x23, 0xf0, 0x8c, 0x11, 0xb8, 0xc2, 0xba}}
,
{{0x0, 0x5b, 0xd9, 0xeb, 0xa1, 0xb8, 0x16, 0x1f, 0x95, 0xf5, 0x21, 0x5b, 0xf2, 0x2a, 0x68},
{0x1, 0x6f, 0x67, 0xae, 0x86, 0xe0, 0x58, 0x7e, 0x57, 0xd4, 0x85, 0x6f, 0xc8, 0xa9, 0xa1, 0x6e, 0x2b, 0x9, 0xd8, 0xed, 0xb2},
{0xb, 0x7b, 0x3d, 0x74, 0x37, 0x2, 0xc3, 0xf2, 0xbe, 0xa4, 0x2b, 0x7e, 0x45, 0x4d, 0xb, 0x71, 0x58, 0x4e, 0xc7, 0x6d, 0x95, 0xf, 0x34, 0x9c, 0x4, 0xa3, 0x67, 0x57, 0xa6, 0xd1}}
};

[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

[bridgeic]

Originally Posted by bridgeic

If use this patch, what we should do at FlexLM SDK side? Which files should be modified? lmprikey.h? or some other files together? How to modify?

License pass check with <1> use the patch <2> compile SDK with setting s below.

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

Seems the private keys is related with the values LM_SEED1~3, but don't know the relationship, anyone can give some clue?

[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