I was playing around with lmcrypt -verfmt in the flexlm 10.8 and 11 SDK trying to understand how to use it to generate licenses for software protected with older versions of flexlm.

I also messed around with adding: #define LM_VER_BEHAVIOR LM_BEHAVIOR_Vxxx to lmcode.h when building lmcrypt, but the line did not seem to have an effect.

Typing lmcrypt -help reveals the only certain versions are available to use with -verfmt (2-5, 5.1, 6, 7 and 7.1).

Does this mean a flex sdk version 7.2 through 10.8 will generate the same signature (assuming the same LM_STRENGTH and seeds)?

It is not clear to me how the different versions can produce the same license since very old SDK versions use two seeds, kinda old versions use four seeds and the newest versions (10.8 and 11) use three seeds.

Can I use my kits to produce flex v9.2 licenses? If I need to do anything in addition, what is it?

The only clue I can give you here is that ver. 10.x licenses are backwards compatible with older versions of the target using 9.x - I do know that some companies are switching to longer auth. codes -



This info doesn't really pertain to your question, but I thought I'd include it just for the general info.

SiGiNT

Where can I get "TOOL REQUEST REMOVED?

Which part of the FAQ's instructions, which state:

"Do not ask where to find the "tools"

did YOU interpret as NOT including YOU??

This is further made clear by the statement in the title of the Tools of the Trade Forum, which states:

Do not ask where to get the Tools of our Trade. Do not even think about asking for them.

These Rules DO APPLY TO YOU!

Regards,

sorry..............

Hmmmmmmmmm......... hadop,

You will now have to redeem yourself to get some respectabilty.

woodmann