Thanks for your response.
Please find my response in-line below.
So it looks like it is working (at least to some extent). Is there a way to test it is working on a Mac? Is there some basic Mac test application I can run to communicate with it?
------------------------------------------------------------------------------------------------------------------------------------------
1. You can use the Safenet Sentinel Medic tool to check for successful communication with Sentinel keys.
Here is the link to download the same.
Additionally, a few samples are provided with Sentinel Ultrapro toolkit those need to be protected and programmed for the specific key. These are available on below location on the machine where the Sentinel Ultrapro SDK is installed.
C:\Program Files (x86)\SafeNet Sentinel\UltraPro\<Version>\Toolkit\Samples
-----------------------------------------------------------------------------------------------------------------------------------------
My use case is possibly not the norm. I want to run IAR EW on my Mac, using WINE (Windows Emulation). The program works fine but I need the License Manager to be able to find the Sentinel Device.
The method described in WINE support is to symlink the device from OS X (or Linux) to the WINE directory, however not device exists in /dev on my Mac (not sure if this is normal or not).
In essence, I'm looking for a way to map the Sentinel device in macOS to the WINE environment so my Windows apps running in WINE can communicate with it.
Should I expect an entry in /dev when the Sentinel device is inserted and the drivers loaded?
2. Please be informed that the Sentinel System drivers are not officially tested over WINE (Windows Emulator). So it is not recommended to use the same with WINE environment.
----------------------------------------------------------------------------------------------------------------------------------------
How do programs normally communicate with the Sentinel device? Via a proprietary library or DLL? Or via some other standard/open interface (e.g. TCP/IP)?
3. On runtime, the application checks for the key’s presence (programmed with a protection strategy) in order to run successfully. For example, by verifying some user data on the key.
The Sentinel driver (an interface to the key) communicates with the key attached to a parallel/USB port as shown in attached picture.
The key returns a response to the driver, which communicates back to your application. If a correct response is obtained, the user is permitted to run the application.
-------------------------------------------------------------------------------------------------------------------------------------
Hope it helps !
Thank You,
Gaurav Bhanot