I have a flexlm 11.8 vendor daemon:
http://www.megaupload.com/?d=A8UGIZKH

and I'm trying to extract the seeds from it. I have read the git manual for extraction, but I don't know if it applies to 11.8 yet. Is there any method for extracting seeds from this daemon or do we have to wait for 11.8 sdk?

Also, assuming somehow we got the seeds from it, what tool is used to generate license signatures? I see a lot of posts on how to extract seeds with ollydbg, but nothing talking about how to use the seeds once you have them.

If we can't extract seeds from 11.8, is there any other way of reversing it? Like a flexlm11.dll patch or something.

I am pretty new to the way flexlm works, so excuse the beginner questions.

I've extracted the seeds from your daemon using techniques that are discussed in the FLEXlm literature no problem, by that I mean "you need to search for those methods".

Licenses are generally created using either makekey or lmcrypt (these need to be built from the FlexNet SDK), the current v11.4 that is out there will do fine. The caveat here is that to generate valid licenses with just the seeds you need the vendor to be using old style short SIGN licenses, otherwise you need to recover additional seeds (the LM_SEEDS) and this is non-trivial.

With the vendor daemon being v11.8 I don't hold out much hope that your target will be using old style keys, this will mean you are going to have to patch the licensing layer to get a license accepted.

I could elaborate for hours on the subject of FLEXlm but I hope this gets you a bit further forward.

Regards, CrackZ.

By flexlm literature, do you mean git's manual or actual flexera documentation?

Is there any way of telling from the daemon if it uses the short SIGN keys? Patching the licensing layer sounds like something that is beyond my capability, so I'll probably just retire the question. Extraction of seeds is probably as far as this rookie can go.

By FLEXlm literature I mean 'current tutorials'.

The reason to extract the seeds from the daemon is that it is configured to accept whatever style of license it finds in the license file, often the actual licensed target will simply decline to accept the old license format without ever trying to perform a checkout.

A sample license or dig through the full target would reveal what style of license is required. If you feel like uploading something I'll tell you ;-).

Regards,

CrackZ.

CrackZ, ygpm.