cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
SimonF
Flexera beginner

lmcrypt alters SERVER line when built with Dongle Support

Jump to solution

I'm running into a few problems when using a lmcrypt.exe that is created when the toolkit has been built with dongle support.

There is a license file named test.lic

#Comment#

SERVER this_host FLEXID=10-ABCD01234

VENDOR EXAMPLE EXAMPLE /EXAMPLE

# counted licenses

INCREMENT f1 EXAMPLE 1.0 permanent 1 SIGN=

When building the toolkit with

nmake -f makefile clean all

and then running the created lmcrypt.exe against test.lic the server line reads

SERVER this_host FLEXID=10-ABCD01234

In contrast, when building the toolkit with

nmake -f makefile DONGLE=1 clean all

and then running the created lmcrypt.exe against test.lic the server line reads

SERVER SIGNING-SYSTEM-HOSTNAME FLEXID=10-ABCD01234

The contents of SIGN= created by both executables are the same

This does seem like undesired behavior since this means the server line will have to be corrected before it is shipped or read by the customer's license server.

Is there a way to call lmcrypt so it only alters the FEATURE/INCREMENT lines while leaving the SERVER line untouched?

Alternatively, what are the implications of signing a license file using a FLEXID HostID with a lmecrypt.exe that was built without dongle support?

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Flexera aparashar1
Flexera

Re: lmcrypt alters SERVER line when built with Dongle Support

Jump to solution

@SimonF , when ever the SERVER line is node-locked with any identity (mac address, IP address or in this case the FLEXID), the hostname will be resolved and the system's (where license file is being crypted ) hostname will be kept in place of localhost/this_host in the SERVER line.

Now, for dongles, we will only have this observation when dongle is physically connected to the system, where license crypt is being performed.

Kindly detach the physical dongle from the system and run the license file crypt again. The SERVER line will not be overwritten with hostname.

If a toolkit was build without dongle support, there shouldn't be any affect on crypting of license file. However, when we will start the license server - it will fail.

(Anything expressed here is my own view and not necessarily that of my employer, Flexera. If my reply answers a question you have raised, please click "ACCEPT AS SOLUTION".)

View solution in original post

0 Kudos
2 Replies
Highlighted
Flexera aparashar1
Flexera

Re: lmcrypt alters SERVER line when built with Dongle Support

Jump to solution

@SimonF , when ever the SERVER line is node-locked with any identity (mac address, IP address or in this case the FLEXID), the hostname will be resolved and the system's (where license file is being crypted ) hostname will be kept in place of localhost/this_host in the SERVER line.

Now, for dongles, we will only have this observation when dongle is physically connected to the system, where license crypt is being performed.

Kindly detach the physical dongle from the system and run the license file crypt again. The SERVER line will not be overwritten with hostname.

If a toolkit was build without dongle support, there shouldn't be any affect on crypting of license file. However, when we will start the license server - it will fail.

(Anything expressed here is my own view and not necessarily that of my employer, Flexera. If my reply answers a question you have raised, please click "ACCEPT AS SOLUTION".)

View solution in original post

0 Kudos
Highlighted
SimonF
Flexera beginner

Re: lmcrypt alters SERVER line when built with Dongle Support

Jump to solution

When the dongle is removed the SERVER line will not be changed indeed.

A classical case of changing too many variables at once in a testing environment.

I had previously experimented if the same effect happens when other HostIds for the server line are used but since they were not match for the signing system the SERVER line was unaffected. Once a HostId that matches the system running lmcrypt is used the same behavior  occurs. It's unlikely to happen in regular use but could crop up in test files.

0 Kudos