date format for flexlm

[borisxyz]

Hello,

I have signature for the feature protected by flexlm. e.g.
6DEE14AB63183EF0BBBC. I noticed that 19th, 17th, 15th and 13th hex numbers (DE4B) are used to code the expiration date for the feature. Is it correct?

Does anyone know rules used to get those hex numbers. Say, If I want March 18, 2011 coded in the signature what 19,17,15,13 hex should be in the signature? Thanks

[BfoX]

19th, 17th, 15th and 13th hex numbers (DE4B) are used to code the expiration date for the feature. Is it correct. for 20th digits v5.x code

[borisxyz]

Bfox, thanks... Yes, my program uses v5.x code.

I noticed in the program that the real signature is compared with the calcualted signature bit by bit in _l_ckout_string_key() but before that happens the date part is stripped from the signature. So, to make the feature work i need to have all 20 Hex numbers in signature, looking at _l_ckout_string_key() I can get 16 hex numbers, how to get 4 remaining hex numbers coding the expiration date? Can you give some pointers? Thanks

[BfoX]

@borisxyz: tell us your vendor daemon name

[borisxyz]

Bfox: the deamon name is sldwks_d which is S..O...L.I..D...W.O...R.K.S

I have reversed this software, extracting the encryption seeds and generating the signatures for the features. At this point, I am just curious to understand how the signatures are generated in flexlm and compared with the feature signatures. That was the basis for my question regarding the expiration date.

Anyone please respond. Thanks