need help on compiling FlexLM v9.2

[dirkmill]

The 9.x SDKs don't work with v8 vendor-keys.
You may try the following keys for vendor "alastone"

v9.x
VENDOR_KEY1 0xf1bd324f
VENDOR_KEY2 0xc0d8c168
VENDOR_KEY3 0x813080d2
VENDOR_KEY4 0xc5eb45fc
VENDOR_KEY5 0x7a703fb3

v10.x
VENDOR_KEY1 0x83f52c05
VENDOR_KEY2 0x633cf7ca
VENDOR_KEY3 0xf56c2940
VENDOR_KEY4 0x4709fe31
VENDOR_KEY5 0x7a703fb3

Your captured v9.2 data should work. You're probably missing something...

Dirk

P.S. You might want to get Nolan Blender's lmrecode source

Originally Posted by dirkmill

The 9.x SDKs don't work with v8 vendor-keys.
You may try the following keys for vendor "alastone"
v9.x
VENDOR_KEY1 0xf1bd324f
VENDOR_KEY2 0xc0d8c168
VENDOR_KEY3 0x813080d2
VENDOR_KEY4 0xc5eb45fc
VENDOR_KEY5 0x7a703fb3

Your captured v9.2 data should work. You're probably missing something...

Dirk

P.S. You might want to get Nolan Blender's lmrecode source

Big thanks to Dirk and Dmit
Yes, I can reach here now:

#define VENDOR_KEY1 0xf1bd324f
#define VENDOR_KEY2 0xc0d8c168
#define VENDOR_KEY3 0x813080d2
#define VENDOR_KEY4 0xc5eb45fc
#define VENDOR_KEY5 0x7a703fb3

#define CRO_KEY1 0x321d784d
#define CRO_KEY2 0xf2c452ca

#define VENDOR_NAME "alastone"

and now I can successfully compiled the v9.2 SDK. the question is, the vendor keys I generated by using this protocol are not identical to the ones I captured in the memory. mmmh, I got obfuscated keys?
the keys coming with lm_code.h (demo) are wrong? stupid question again

[CrackZ]

Hiya,

The keys in your target are not obfuscated, other than key 5 in the same old method.

The reason your keys differ is that the vendor keys as issued by Macrovision have options such as checksums, expiry dates etc, etc taken into the generation process, in fact in terms of generating a license the vendor keys aren't even used anymore.

Regards

CrackZ.

Originally Posted by CrackZ

Hiya,

The keys in your target are not obfuscated, other than key 5 in the same old method.

The reason your keys differ is that the vendor keys as issued by Macrovision have options such as checksums, expiry dates etc, etc taken into the generation process, in fact in terms of generating a license the vendor keys aren't even used anymore.

Regards

CrackZ.

Yes, now I understant this. The vendor keys generated by myself and the other set with the help of Dmit are not identical: key1-4 are different, while key5 and CRO keys are same. There are all valid. Compiled two lmcrypt.exe resulted in same license sign strings. Unfortunately, the license is invalid.
I am trying to figure out the problem. Any hints are much appreciated.

[CrackZ]

Hiya,

Your question can be simply answered by telling us the return value of _lc_checkout() ;-).

Its going to be either bad seeds or a public key verification error.

Regards

CrackZ.

[dirkmill]

Originally Posted by alastone

the keys coming with lm_code.h (demo) are wrong? stupid question again

hi alastone!

the demo-keys are not wrong, just expired
see below for the output of lmrecode

Input vendor name (Actually daemon name):
demo
Version of input data (3, 4, 5, 6, 7, 8, 9 or 10=2):
9
Input decvals[0] = 37efbbfe
Input decvals[1] = ffffffe1
Input decvals[2] = ffffffff
Input decvals[3] = 71eed201
Expiry date: 1-jan-2005
Encryption seed1: 0b165dc9
Encryption seed2: 0b165dc9
VENDOR_KEY1 0xc945f9e3
VENDOR_KEY2 0x45083d28
VENDOR_KEY3 0xd42a1e0d
VENDOR_KEY4 0x16a59630
VENDOR_KEY5 0x0b165dc9

Dirk