Hello all,

I've been tinkering away at a flexlm licensing scheme that doesn't require a daemon to be running in the background. It still does license file checking, but this is contained somewhere within the target. Indeed, even though there's a server-client licensing scheme avaliable, I can't figure out from the instructions how to set it up.

Anyway, I identified which files contained the lmgr.lib - these were all .dll. Apparently, the target features a launcher app that picks an engine (normal or MPI). It is this engine (a .dll) that contains the flex lib, and which then resorts to other dlls lying around. Oh, flex is v9.2.

Now, since IDA spits a huge amount of stuff out, it's an issue finding the checkout routines. Does anyone breaking up such schemes into smaller, tractable pieces?

Cheers,

vesanico

Available for IDA is various FlexLM sig files, (the version doesn't have to match), google and see if you can find them, or you may already have one or more, when applied, they will label the checkout routines usually _l_checkout or _lc_checkout, they however, (at least as far as I know) do not label the ECC routine, which is the main key if you want to take a patching approach. It really doesn't help much, as there are very few apps, (yes there are a few), that can be patched to run without some form of a license - see other posts in this forum for more info.

SiGiNT

Hello all,

here's an update of my activities:


- found lmgr.lib inside ****Engine.dll, ****ServerEngine.dll, ***X.dll
- disassembly with IDA, using 3 sig files for flexlm 9.2
- located the flex routines, but still looking for the checkout
- found, in the unix folder of the installation cd, a daemon executable, as well as a license server utility (both flex).

To do:
- find what's happening in the serverless (or embedded server) version
- check whether the unix utilities bring some insight into the workings.

Cheers,

vesanico