Known and Resolved Issues
The following table lists known issues in all released versions of the ProtectServer HSM firmware, ProtectServer External 2 appliance software image, and ProtectToolkit client software. Workarounds are provided where available. Issues listed in green have been resolved and the component and version including the fix is provided.
| Issue | Synopsis |
|---|---|
| PSR-7424 |
Problem: When you are using the SafeNet KSP on a Windows system and disconnect the ProtectServer External 2 or ProtectServer External 2 Plus network cable, the client application receives a timeout, terminates, and crashes the system. Workaround: None. Resolved: Fixed in patch KB0026594. |
| PSR-6768 | Problem: If more than 10 accept or drop rules have been added the iptables firewall of a ProtectServer 2 Network HSM appliance, rules 11 and higher cannot be specified with the network iptables PSESH command. Workaround: None. |
| PSR-6767 | Problem: The HSM crashes if you try to create a BIP32 object in JCPROV using C_CreateObject and the CKA_BIP32_CHILD_INDEX or CKA_BIP32_CHILD_DEPTH attributes have null parameters. Workaround: None. Resolved: Fixed in firmware 5.06.04. |
| PSR-6517 | Problem: C_Sign() returns an invalid signature when used with length prediction and if the data size is greater than 127 KB. Workaround: Do not use length prediction with C_Sign() if the data size is greater than 127 KB. |
| PSR-6494 | Problem: The HSM halts if you specify a DES3 key as the wrapping key for an export key operation, by using the ctkmu x command with the -w option, and do not include the -3 option. Workaround: Include the -3 option to avoid halting the HSM or encountering an error. |
| PSR-5380 | Problem: The ProtectServer PCIe 2 HSM is not compatible with the 32-bit version of Windows 7. Workaround: None. |
| PSR-5057 |
Problem: After upgrading the HSM firmware, the gmadmin UI remains outdated and continues to display the previous firmware version. Workaround: Restart gmadmin. |
| PSR-5010 |
Problem: When running psesh:>sysconf appliance factory, the network configuration (hostname and IP address) are not reset. Workaround: Run the following commands to complete the factory reset procedure: >psesh:>network interface delete to delete the IP address. >psesh:>network hostname <hostname> to set a new host name for the appliance. |
| PSR-3970 |
Problem: Resetting the HSM between 20:00 and 24:00 GMT sets the real-time clock (RTC) back by 20 hours. Resolved: Fixed in firmware 5.06.02. |
| PSR-3414 |
Problem: When a new PCI driver is installed on Windows using the PTKpcihsmK6.msi package, the driver file (LunaK4.sys) is not updated automatically. Workaround: Use the following procedure to allow the Device Manager to recognize the new driver: 1.Disable the Luna PCI device in the Device Manager. 2.Copy LunaK4.sys manually from the installation directory to System32/drivers. 3.Enable the Luna PCI device in the Device Manager. |
| PSR-3368 |
Problem: While installing the PCI access provider, driver insert code is displayed on the console.
Workaround: This can be safely ignored. |
| PSR-3219 |
Problem: Pressing Cancel on the legacy Verifone 1000SE PIN pad halts the HSM. Workaround: Do not press Cancel when entering keys. Upgrade to a newer PIN pad. |
| PSR-2751 |
Problem: Applications using the USB API are not able to write files larger than 1 MB to the USB memory drive. Resolved: Fixed in firmware 5.06.02. |
| PSR-2700 |
Problem: The USB API does not support hybrid USB devices that use the USB 2.0, 3.0, and 3.1 standards. Resolved: Fixed in firmware 5.06.02. |
| PSR-2046 |
Problem: When using PTK-J, stopping an application using Ctrl-C causes the HSM to crash. Log reports a "Segmentation Fault". Workaround: None. |
