who knows how to generates the VENDOR_INFO string from the license key?
 

Is there anybody who knows how to generates the VENDOR_INFO string from the license key?

I meet a app that be protected by Flexlm , It use a license that have VENDOR_INFO and DIST_INFo stringI meet a app that be protected by Flexlm , It use a license that have VENDOR_INFO and DIST_INFo string Like this:
FEATURE FEATURE1 VENDORname 20051207 15-jan-2006 uncounted 53D5DD0FF467 \
VENDOR_STRING=3-DEMO-25-0-1-VM05120701 \
HOSTID=DISK_SERIAL_NUM=12345678 vendor_info="e650c7bb00e81d53" \
dist_info="d17b14a8b615e68cfe928f58fdefa251d38106bb6e33b54518cb1519b2eb424a"
FEATURE FEATURE2 VENDORname 20051207 15-jan-2006 uncounted 5C89B778DC77 \
VENDOR_STRING=3-DEMO-20-0-0-VM05120701 \
HOSTID=DISK_SERIAL_NUM=12345678 \
vendor_info="246b6b3146a892ee" \
dist_info="17eea625fcc8867b2df2aeb097af4996e689800caaa1c7fc5e5e0c5e2ceb42f4"
FEATURE FEATURE3 VENDORname 20051207 15-jan-2006 uncounted 369FA7270A06 \
VENDOR_STRING=3-DEMO-1-0-0-VM05120701 \
HOSTID=DISK_SERIAL_NUM=12345678 \
vendor_info="aba1dc03a7b16794" dist_info="12f9e3ff95437a244e592d8be6caf09cd4894eb6d39e956c13ae50ce2642dac1"

I can strip VENDOR_STRING from license line and generate a new license without problems.
But The VENDOR_INFO and DIST_INFo string maybe are accrording to(Feature,exp_date ,key,HOSTID),
if you just strip from license line and generate a new license ,
IT cann't work , and show "Future license file format or misspelling in license file"
.

nblender said "It use different algorithms for calculating the VENDOR_INFO field. The VENDOR_INFO field has to be update to match the license key.Using your favorite debuggger and disassembler, reverse the routine which matches the license key to the VENDOR_INFO string and make a keygen."

Is there anybody who knows how to locate the algorithms for calculating the VENDOR_INFO in the routine ?
who knows how to a keygen to generates the VENDOR_INFO string from the license key?

I have google and read Nolan's:
"Information Hiding Methods used by FlexLM Targets"
"Key Extraction and Encryption Algorithm Reversing"
"Making Tools Work Together"
"Reversing the report encryption algorithm for the flexlm license manager'
"describes an attack on the keys for FlexLM itself"

BUt I haven't found any information for it .

Can you tell me is there any other article about it?
Thanks !

It may be hand made algorithm. You need recovery it before generating.
And you can not find any solutions in essay, imho.

wbr

Hi hanzi,

regarding the vendor_info I was wrong. It is a standard attribute which is triggered by the lm_set_attr(...) function with the proper code. Therefore, you should find the corresponding code (from SDK) and monitor any call to lm_set_attr(...).

nathan

thanks nathan,

I think maybe it is a standard attribute which is triggered by the lm_set_attr(...) function with the proper code.But in the lm_attr.h ��I cann't find a corresponding code for vendor_info . have you ever meet it?

Only references I could find were :

#define LM_CDID_VENDOR_INFO 6 /* id #6 */
#define LM_CDID_DIST_INFO 7 /* id #7 */


and

#define LM_LICENSE_VENDOR_INFO "vendor_info"
#define LM_LICENSE_DIST_INFO "dist_info"


Git

I have same problem.