ProtectToolkit Software Installation

This section contains instructions for installing the various ProtectToolkit software components and configuring them for your client machine. Refer to the system requirements below, and then the section for your client operating system:

System Requirements

ProtectToolkit 5.9.1 has the following prerequisites for installation:

>Java runtime (required for graphical user interface utilities only). The product has been tested using Java runtime version 6.x, 7.x, 8.x, 9.x, 10.x, and 11.x.

NOTE

>The older (minor) versions of Java 7 or Java 8 could cause issues with the SAFENET java library (jprov_sfnt.jar). Thales Group recommends updating Java 7/8 to the latest version.

>Warnings appear when compiling some of the provided Java samples with Java runtime 9, 10, or 11 installed. These warnings can be safely ignored.

>.NET versions 3.5 and 4.5 (Windows only). All required .NET versions are available for download from Microsoft.

>Microsoft Visual C++ 2005, 2008, 2010 (Windows only). All required MSVC versions are available for download from Microsoft.

NOTE The Java runtime, .NET and Microsoft Visual C++ must be installed first.

Supported Platforms

The supported platforms are listed in the following table.

C=ProtectToolkit-C, PKCS #11 v2.10/2.20

M=ProtectToolkit-M, MS CSP 2.0 with CNG

J=ProtectToolkit-J, Java runtime 6.x/7.x/8.x/9.x/10.x/11.x.

NOTE Do not upgrade to ProtectToolkit 5.9.1 if you are using the legacy PSG HSM.

Operating System		OS type	64-bit PTK	64-bit PTK supported hardware	32-bit PTK	32-bit PTK supported hardware
Windows	10	64-bit	C/M/J	PCIe2, PSE2, PSE2+	C/J	PSE2, PSE2+
	Server 2019	64-bit	C/M/J	PCIe2, PSE2, PSE2+	C/J	PSE2, PSE2+
	Server 2016	64-bit	C/M/J	PCIe2, PSE2, PSE2+	C/J	PSE2, PSE2+
	Server 2012 R2	64-bit	C/M/J	PCIe2, PSE2, PSE2+	C/J	PSE2, PSE2+
	Server 2008 (R1 and R2)	64-bit	C/M/J	PCIe2, PSE2, PSE2+	C/J	PSE2, PSE2+
	7	32-bit	-	-	C/J (KSP support)	PCIe2, PSE2, PSE2+
	7	64-bit	C/M/J	PCIe2, PSE2, PSE2+	C/J	PSE2, PSE2+
Linux	RHEL 8.7*	64-bit	C/J	PCIe2, PSE2, PSE2+	-	-
	RHEL 7	64-bit	C/J	PCIe2, PSE2, PSE2+	C/J	PSE2, PSE2+
	RHEL 6	32-bit	-	-	C/J	PCIe2, PSE2, PSE2+
	RHEL 6	64-bit	C/J	PCIe2, PSE2, PSE2+	C/J	PSE2, PSE2+
	SUSE12	64-bit	C/J	PCIe2, PSE2, PSE2+	C/J	PSE2, PSE2+
AIX	7.2	64-bit	C/J	PSE2, PSE2+	C/J	PSE2, PSE2+
	7.1	64-bit	C/J	PSE2, PSE2+	C/J	PSE2, PSE2+
	6.1	64-bit	C/J	PSE2, PSE2+	C/J	PSE2, PSE2+
Solaris	11 (SPARC, x86) 10 (SPARC, x86)	64-bit	C/J	PSE2, PSE2+	C/J	PSE2, PSE2+
HP-UX	11	64-bit	C/J	PSE2, PSE2+	C/J	PSE2, PSE2+

* Requires the RHEL 8.7 Support Patch.

Operating Modes

ProtectToolkit-C can be used in one of three operating modes. These are:

>PCI mode in conjunction with a locally-installed ProtectServer PCIe 2.

>Network mode over a TCP/IP network, in conjunction with a compatible product such as the ProtectServer External 2.

A machine with a ProtectServer PCIe 2 installed may also be used as a server in network mode.

>Software-only mode on a local machine without access to a hardware security module.

Within the client/server runtime environment, the server performs cryptographic processing at the request of the client. The server itself will only operate in one of the hardware runtime modes.

The software-only version is available for a variety of platforms, including Windows NT and Solaris, and is typically used as a development and testing environment for applications that will eventually use the hardware variant of ProtectToolkit-C.