vesanico
September 13th, 2005, 06:27
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
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