File was renamed from doc/Hardware-identifiers.md |
| | |
| | | # Hardware Identifiers |
| | | |
| | | ## Use cases |
| | | Linking the execution of a software to a. With the recent coming of virtualized environments the installation of software directly on the machine has been less and less. |
| | | Linking the execution of a software to a physical hardware (a pc). With the recent coming of virtualized environments |
| | | the installation of software directly on the machine has been less and less. |
| | | |
| | | OpenLicenseManager guess the environment where the user is trying to launch the software, and reports it to the software publisher when he is generating a license in a way that he can decide how to limit the usage on per license basis. |
| | | |
| | |
| | | This is straightforward case. If the software is executing on a physical hardware it is possible to identify the hardware by various parameters (cpu type/memory/disk label/mac address) |
| | | |
| | | ### Execution in a virtual machine |
| | | Generating a pc identifier on a virtual machine doesn't make much sense, since the vm can be copied as a whole elsewhere |
| | | Generating a hardware identifier on a virtual machine doesn't make much sense, since the vm can be copied as a whole elsewhere |
| | | and there are few ways to detect this without using an external license server. |
| | | |
| | | * Usually when the machine is copied the MAC address is changed. But sometimes it changes on its own. Software publishers may want to use this as a last resort to prevent the vm for being cloned. It has to be verified case by case. |
| | |
| | | |
| | | |
| | | If the licensed software specify the parameter |
| | | If the licensed software uses `STRATEGY_DEFAULT` and the strategy generates an unstable identifier it is possible to ask the user to set t |
| | | If the licensed software uses `STRATEGY_DEFAULT` and the strategy generates an unstable identifier it is possible to ask the user to |
| | | set the environemnt variable. |