About oversampled

oversampled · ‎Oct 27, 2021

Using the Ethernet MAC Address is not stable on a Windows system. A more reliable solution is to create a custom host ID and query the disk serial number of the Windows volume. In our experience, Ethernet MAC Address is stable on Apple Mac systems. With Flexnet Embedded XT, you have to manage your own host ID to overcome these issues. Publisher has a more sophisticated system for querying and managing host IDs.

oversampled · ‎Apr 05, 2021

There are some notes on this in the FNE_CXTUserGuide (see 'Specifying the Trusted Storage Location'). If you are using a device based licensing model then probably you need to locate Trusted Storage in a shared location so that different user accounts use the same TS instance. This works fine on Windows systems but can be tricky to implement on macOS due to folder permissions. Alternatively you can disable secure anchoring to avoid the error.

oversampled · ‎Aug 28, 2020

We are a customer of both FNP and FNE solutions, having legacy versions of our product on FNP and newer versions on FNE. Having been encouraged by Flexera to migrate to the newer FNE platform, 'this is where all the innovation is going' we were told, we would dearly like to see due attention given to FNE.

oversampled · ‎Aug 25, 2020

jberthold, Thanks for your reply, although this is probably not the response that FNE XT customers are looking for. Can you confirm then, is it the official position of Revenera that FNE customers should proceed to code their own Apple Silicon port using the porting kit? A 'roadmap item' sounds worryingly as though there isn't yet anyone working on it. End user expectation has changed with respect to new products and operating systems, people want the newest options immediately. As software vendors we need to be prepared ahead of time in order to remain competitive and capture the market share of early adopters - or risk losing customers to competing products. Adopting the porting kit seems like a lot of work and will be a tough development decision when there are competing licensing solutions already offering support for Universal Binaries on macOS Big Sur. Please! please! please! push internally to get some engineering effort on macOS 11.0 Universal Binary support including the new ARM architecture.

oversampled · ‎Aug 21, 2020

Yes agreed. The XT kit absolutely must have a solution ready for Apple Silicon. Please let us know what is planned and when we can expect to see a client kit to work with.

oversampled · ‎Mar 24, 2020

We have several thousand FNE XT protected clients and on Windows systems, using the first reported Ethernet Adapter has not proven to be a reliable method of identifying a machine. Depending on the hardware, the first reported Adapter may disappear when the machine is not connected to WiFi or when the user switches off WiFi. Furthermore there are some Ethernet connectivity solutions that will regularly report a different Adapter Address. The problem here is not simply that the reported Ethernet Adapter changes, but that it may disappear, leaving an invalid id in Trusted Storage. To a lesser extent we saw a similar issue with MAC systems (using the XT kit FlcGetHostIds() call) although we were able to overcome this by writing our own method to query Ethernet Adapter more consistently and then specify this adapter using FlcSetDefaultHostId() with the FLC_HOSTID_TYPE_ETHERNET type. The solution for MAC systems is now reliable. Having previously used FNP, it seems that FNE XT kit should offer a similar machine identification API with the ability to repair a broken binding. Another approach might be to allow more than one Ethernet Adapter address to be associated with the license feature binding. I'm aware of other systems that use this approach with success. I'm interested to hear what others experience is here and what solutions you have found. It may be possible to implement a custom machine identification solution and then use a custom string Host ID type rather than Ethernet Address Host ID, however I am concerned that using a Custom String could introduce a weakness in the protection that could be exploited more easily but perhaps this concern is unfounded. Thoughts Flexera or other FNE XT customers? Yes we have experimented with hostid-type filters in the identity.

oversampled · ‎Feb 18, 2020

We implemented an lm_wait_on_transaction() function which can be called before the main licensing class is destroyed. This allows the transaction thread to finish working before the parent object is destroyed. Seems to work well since the FNE SDK doesn't wait for long on the communications calls.

oversampled · ‎Dec 17, 2019

An update to the FNE libraries is urgently required to address the Apple notarization requirements. Currently the 2019.11 libraries are built using OSX SDK 10.8. It is a requirement for notarization that all libraries are built using SDK10.9 or later. It would be reassuring to hear some news about this.

Online Status	Offline
Date Last Visited	‎Mar 21, 2023 07:42 AM

Re: MAC address not stable as host ID

Re: Multiple Trusted storage

Re: Universal (ARM) FNE libraries

Re: Universal (ARM) FNE libraries

Re: Universal (ARM) FNE libraries

The XT kit doesn't provide a reliable solution for machine identification on Windows systems.

Re: How to interrupt a FlexNet Embedded XT SDK and exit gracefully

MacOS 10.15 Notarization of FNE Clients will require library update.

Re: MAC address not stable as host ID

Re: Multiple Trusted storage

Re: Universal (ARM) FNE libraries

Re: Universal (ARM) FNE libraries

Re: Universal (ARM) FNE libraries

The XT kit doesn't provide a reliable solution for machine identification on Windows systems.

Re: How to interrupt a FlexNet Embedded XT SDK and exit gracefully

MacOS 10.15 Notarization of FNE Clients will require library update.