- Revenera Community
- :
- FlexNet Publisher
- :
- FlexNet Publisher Forum
- :
- Re: lmcrypt security
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
lmcrypt security
How do others deal with this, I'm sure we're not the first to run into this dilemma.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
A lmcrypt executable, vendor daemon executable and lmgrd executable are the 3 most sensitive part of any publisher (/customer) who generates licensing.
So it becomes a publishers responsibility to insure their safety. And yes if lmcrypt is in the air, its a security issue and i am afraid that it can't be tracked down. (for example, create an uncounted license and use it forever)
Regards,
Abhay
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
I totally agree the reply with regard to lmgrd is confusing.
The security within FLEXera depends upon your secret keys and those are obviously compiled into lmcrypt, your vendor daemon and your application.
Any "off the shelf" executables such as lmgrd and lmutil have no relationship to your secret keys at all.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
A lmcrypt executable, merchant daemon executable and lmgrd executable are the 3 most touchy piece of any distributer (/client) who produces permitting.
So it turns into a distributers duty to protect their wellbeing. Also, yes if lmcrypt is noticeable all around, its a security issue and I am anxious about the possibility that that it can't be found. (for instance, make an uncounted permit and use it until the end of time), air blue
@PhilipMJones wrote:I totally agree the reply with regard to lmgrd is confusing.
The security within FLEXera depends upon your secret keys and those are obviously compiled into lmcrypt, your vendor daemon and your application.
Any "off the shelf" executables such as lmgrd and lmutil have no relationship to your secret keys at all.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi
Maybe you can rebuild the SDK by changing the seeds in lm_code.h.
rebuild lmcrypt and the application too.
oldest version of lmcrypt will not be compatible with new software.
Regards.
Gilles Noyer.
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)