| Anchor | ||||
|---|---|---|---|---|
|
...
Regular Sentinel HASP keys
This is most common way of CHARON-VAX licensing.
The CHARON-VAX license is embedded in a Sentinel HASP dongle. This license is available only on the host where the dongle is physically installed.
The CHARON-VAX installation procedure takes care of the Sentinel HASP run-time (driver) installation. Once the CHARON-VAX product has been installed, it is possible to plug-in the regular license key and proceed with CHARON-VAX usage without additional configuration steps.
| Info |
|---|
The number of CHARON-VAX instances allowed to run on a particular host may be restricted by the license content (see above). |
...
| Parameter | Type | Value | ||
|---|---|---|---|---|
| license_key_id[N], N=0 or 1 | Numeric | A number (decimal Sentinel key ID) that specifies regular (N=0) and backup (N=1) license keys to be used by CHARON-VAX. Example:
It is also possible to specify both regular and backup key in one line. Example:
Depending on the presence of the regular and/or backup license key IDs in the configuration file, CHARON-VAX behaves differently:
|
License installation
Installation of Regular and Network license keys
Installation of CHARON-VAX regular and network licenses consists of:
Installation of the Sentinel run-time environment on the CHARON-VAX host (regular and network keys) or on the host that will distribute CHARON-VAX licenses over a local network segment (network key only). The Sentinel software ( the “aksusbd” RPM package) is installed automatically by CHARON-VAX for Linux.
Physical connection of the HASP license dongle to the CHARON-VAX host or to the host distributing the CHARON-VAX license over the local network segment.
When manual installation of Sentinel run-time is required (in the case of the network license server that does not have CHARON-VAX installed), open the CHARON-VAX kit folder and proceed the following way:
|
| Info |
|---|
In case of network-wide license (red dongle) do the following:
Please consult with your Linux User's Guide on details. If stricter firewall rules are required, it is possible to open the ports 30000-65535 and 1947 only for the "/usr/sbin/hasplmd" daemon. |
| Div | ||
|---|---|---|
| ||
|
| Info |
|---|
Some additional packages may be needed in certain cases, for example "glibc.i686" |
...
To access the ACC, start any web browser and go to http://localhost:1947
| Info |
|---|
Sentinel Admin Control Center is not able to display CHARON-VAX licenses - to view key contents, use the "hasp_srm_view" utility. |
To access Sentinel Admin Control Center start any web browser,
...
enter http://localhost:1947
...
and press Enter.
...
Web interface of the Sentinel Admin Control Center will appear.
The screenshot below gives an example of its interface:
Disable remote keys access
A helpful feature of Sentinel Admin Control Center is the ability to disable access to remote keys. If the network key is installed locally, access to the key from remote hosts can be disabled. The following examples demonstrate how this can be done.
To disable access to remote keys switch to the "Access to Remote License managers" tab and uncheck the "Allow Access to Remote Licenses" checkbox. Then press "Submit" button to apply this setting:
Accessing Sentinel Admin Control Center from remote hosts
By default, Sentinel Admin Control Center forbids accessing its web interface from remote machines. To allow access, configure ACC for remote management.
The first step is to edit the "hasplm.ini" file:
|
Allow remote access by changing the "ACCremote" parameter from "0" to "1".Then restart Sentinel Admin Control Center run-time:
# /etc/init.d/aksusbd restart |
If the CHARON-VAX host firewall is blocking remote access to the Sentinel Admin Control Center, please configure the firewall to open the port 1947 (TCP protocol). Refer to Linux documentation for details on how to configure the firewall.It is also possible to use SSH port forwarding with the following command (put the real CHARON-VAX host name instead of "CHARON_MACHINE"):
# ssh -L8080:CHARON_MACHINE:1947 root@CHARON_MACHINE |
This will expose Sentinel Admin Control Center on port 8080 to any computer, and Sentinel Admin Control Center will believe commands are coming from the local host.
License management utilities
CHARON-VAX for Linux provides a specific utility for license management - "hasp_srm_view". This utility is used to display CHARON-VAX license content, and to collect key status information and host fingerprint (C2V) files.
| Info |
|---|
Applying updates (".v2c" files) is typically done using Sentinel Admin Control Center (see above), but alternatively it is also possible to use a specific "hasp_update" utility for that. |
Please refer to the Utilities section of this Guide for more details.
Transferring and removing CHARON-VAX software licenses
Software Licenses Transfer
Software Licenses (SL) can be transferred from one host to another using the "hasp_srm_view" utility and "Sentinel Admin Control Center" (ACC).
The following example demonstrates the transfer procedure.Let's suppose a Software License must be transferred from a host "SourceHost" to a host "RecipientHost":
Collect the specific information about the "RecipientHost" to issue a transfer license. To do that run "hasp_srm_view" utility on the "RecipientHost" with the following parameters:
$ hasp_srm_view -idfThe file "recipient.id" will be created in the current directory.
Copy the "recipient.id" file to the "SourceHost".
Info "recipient.id" file is an ASCII file, so use "ascii" option in case of FTP transfer. - On "SourceHost", open "Sentinel Admin Control Center" (ACC) (browse to http://localhost:1947). Note the number of the software license you are going to transfer.
Run the "hasp_srm_view" utility in the following way to create a transfer license for the host "RecipientHost":
$ hasp_srm_view -tfr <license number> recipient.idThe "license number" is the value collected at step 3.Example of collecting a transfer license:
$ hasp_srm_view-tfr 12345678recipient.idThe file "<license number>.v2c" will then be created in the current directory. In the example above the name of the transfer license will be "12345678.v2c"
Copy the resulting "<license number>.v2c" file to the "RecipientHost".
Info "<license number>.v2c" file is an ASCII file, so use "ascii" option in case of FTP transfer. On "RecipientHost", open "Sentinel Admin Control Center" (ACC) (browse to http://localhost:1947). Apply the "<license number>.v2c" file as described above
Software License Removal
It is also possible to remove Software License completely from a host, the license will then be dumped to a specific license file "*.v2c", so it can be re-applied if needed.
To remove the Software License completely from a host, do the following
::
- Open "Sentinel Admin Control Center" (ACC) (browse to http://localhost:1947). Note the number of the software license you are going to remove.
Run the "hasp_srm_view" utility in the following way to remove the license:
$ hasp_srm_view -tfr <license number>The "license number" is the value collected at the step 1.Example:
$ hasp_srm_view -tfr 12345678The "<license number>.v2c" file will then be created in the current directory. In the example above the name of the transfer license will be "12345678.v2c"
- It is always possible to re-apply the created ".v2c" file to restore the deleted software license.
Cloned Software License Removal
In certain situations Software License may become "Cloned" (disabled). In this case the following procedure must be applied to remove the cloned license:
- Go to http://localhost:1947 to access the "Sentinel HASP Admin Control Center" (ACC).
- In the "Sentinel HASP Admin Control Center" (ACC), locate the target "Sentinel SL AdminMode" license.
- Press the "Certificates" button at the right side of the SL description:
- Note the name of the correspondent certificate and path to the certificates base in the "Certificates" section.
- Remove the target certificate file from the specified directory (in most cases it is "/var/hasplm/installed/68704/").
- Reboot CHARON host.
- Start "Sentinel HASP Admin Control Center" (ACC) again to ensure that the SL has been removed.
| Div | ||
|---|---|---|
| ||
|
License Deinstallation
To completely remove a CHARON-VAX license from a host, it is enough to remove the Sentinel run-time daemon (and the package "charon-license-<...>.rpm" containing the run-time customization) using the following command:
# rpm --nodeps -e aksusbd charon-license-<...> |
Then just physically disconnect the license key (in the case of protection by dongles).
Special "backup" license keys
Backup keys are provided by STROMASYS along with standard license dongles. It is strongly recommended to order a backup key to recover immediately from damage or loss of the main license key.Backup keys use a counter (integer) value hardcoded inside the key. This integer value is a number of hours CHARON-VAX is allowed to run. Each time CHARON-VAX checks the license (every hour), the value is decreased (by 1 hour).Please note that backup keys have restricted functionality:
- CHARON run time is typically limited to 720 hours (30 days). This should be more than enough time to get a replacement from STROMASYS.
- Backup license may be valid only until a certain date. Please check with STROMASYS management.